Problem: The client experiences 404 errors across the site, mainly with portfolio posts, after copying and translating a page. The issue persists even after setting up redirects and involves unexpected changes in URLs when setting up translations in different languages.
Solution: 1. Ensure the PHP version is fully supported by WordPress, preferably versions 8.1 or 8.2. 2. In an incognito window, check if the issue still occurs. If it does, follow these steps: - Navigate to WPML->Support->Troubleshooting. - Clear the WPML Cache. - Go to WP Engine and clear the website cache. 3. Check if there are any active 301 redirects that might be affecting the URLs. 4. In WPML settings, under 'Translated documents options' -> 'Page URL', ensure the correct settings are applied based on whether the translation language uses encoded URLs. If necessary, adjust the language settings to 'Encoded' or set it to 'Translate' for more control over the URL slugs in the translation editor.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your specific case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket.
Problem: The client is experiencing an issue where the button text on a Loop template page displays in Spanish, despite the page not being translated. The button text 'Read More' does not reflect the default language when displayed on the front end. Solution: We recommend checking the translation settings for your post types and language switcher. First, navigate to WPML->Settings->Post Types Translations and ensure that the pages are set to Translatable - only show translated items. This setting helps in displaying content only in the translated language without falling back to the default language if a translation is not available. Next, go to WPML->Languages->Language Switchers and check the option for How to handle languages without translation. Make sure that "Skip languages" is enabled. This setting prevents the display of languages that do not have translations.
If these adjustments do not resolve the issue, or if the solution seems outdated or not applicable to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket with us for further assistance.
Problem: If you're experiencing warnings and a 404 page after using the autotranslate feature on your site, particularly when switching to languages like Danish, and your theme is compatible with WPML, the issue might be related to your site settings. Solution: We discovered that although the Settings → General page displayed values for both Site URL and Home URL, the Home URL was actually empty in the database (in the wp_options table). This mismatch was likely causing the problem. Simply re-saving the settings page might not repopulate the value due to the issue itself preventing it. Therefore, we recommend updating the Home URL directly in the database. After making this change, please check your site to confirm that everything is working as expected.
This solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
Problem: The client is facing two issues: 1) Unable to find and translate the footer content in the Quere theme using WPML. 2) Incorrect display of Contact Form 7 forms in different languages on the footer and contact page, despite correct settings in Elementor. Solution: For translating the footer: 1. Check the WPML → Translation Dashboard for any unscanned texts and use the search function to find specific footer phrases. 2. If not found, navigate to WPML → Theme and plugins localization, select the Quere theme, and scan for strings. Then, use WPML → String Translation to add translations.
For resolving Contact Form 7 issues: 1. Ensure the Contact Form 7 Multilingual plugin is active. If not, download and activate it. 2. Translate the forms via WPML → Translation Dashboard, select the forms, and send them for translation. 3. Clear any site caches to reflect changes.
If these steps do not resolve the issues or if the footer still cannot be found for translation and the forms display incorrectly in some languages, it may be necessary to directly contact our support. We recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket at WPML support forum.
Problem: The client is facing two issues: first, two items in the translation queue are marked as 'status: pending review' and display an endlessly spinning icon. Second, French links are not correctly translated, leading to pages with URLs that remain untranslated. Solution: 1) To resolve the endlessly spinning icon in the translation queue: - Navigate to WPML-> Translation Dashboard. - Turn off the 'translate everything automatically' option. - Refresh the page. - Check the Translation Jobs tab to ensure no jobs are stuck.
2) To fix the untranslated French URLs: - The URLs were not translated inside ATE; we have now translated them. Please verify if they now correctly redirect on the translated home page.
Additionally, check the WPML-> Translations page to confirm that no pages are stuck in the pending review status. If issues persist, it might be due to outdated solutions or specific configurations that differ from your setup. We recommend visiting related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem continues, please open a new support ticket.
Problem: The client reported multiple issues: pages not appearing in the translated language, content inside Spectra tabs not translating correctly, and images not displaying correctly in translations. Solution: 1. For pages not appearing in the translated language, we recommended removing ghost entries and re-translating the pages. This involves: - Navigating to WPML > Support > Troubleshooting. - Clicking on "Remove ghost entries". - Editing the page in the original language, making a minor change, and saving. - Updating the translation page.
2. For translating Spectra tabs, we provided an XML configuration to make the tab titles/labels translatable. The client should: - Add the provided XML configuration to the WPML configuration file. - Update the original page and translate the tab content in the Advanced Translation Editor.
If these solutions do not resolve your issues or if they seem outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance.
Problem: The client reported a crash on Greek product pages when using the Klarna for WooCommerce plugin, despite it working correctly in other languages. The error logs indicated a fatal error due to a null object reference in the Klarna plugin, suggesting a conflict with WPML's handling of translated products and WooCommerce Blocks.
Solution: We initially attempted to resolve the issue by applying a temporary code snippet to check for null product objects on the Greek product pages. However, this did not fully resolve the issue. The client managed to fix the display of the Greek product pages by correcting the template used, but the Klarna plugin still caused crashes when enabled. We recommended creating a staging site to further investigate the issue without affecting the live site.
If this solution does not apply to your case, or if it seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The links in products and category texts on the Danish page are not working correctly. They redirect to the English color page instead of the Danish version, although the Danish translation is available and works when accessed from the "customize" page. Solution: The issue stems from the links in the default language editor using 'http' instead of 'https'. We recommend updating these links to include 'https', which should allow WPML to process them correctly. After making this change, please update your translations to ensure that all links work correctly across different languages.
If this solution does not resolve your issue or seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket.
المشكلة: تواجه مشكلة في عرض بعض العبارات باللغة الأصلية في صفحة المنتج، على الرغم من ترجمتها في محرر الترجمة ATE. الحل: لحل هذه المشكلة، نوصي بإضافة الكود التالي إلى WPML-> Settings-> Custom XML Configuration:
لمزيد من المعلومات حول كيفية جعل الكتل المخصصة في Gutenberg قابلة للترجمة، يرجى زيارة هذه الصفحة. بعد ذلك، يرجى إعادة ترجمة قالب المنتجات لضمان ترجمة جميع العبارات.
قد تكون هذه الحلول غير ذات صلة إذا كانت معلوماتها قديمة أو لا تنطبق على حالتك. نوصي بشدة بفحص المشاكل المعروفة، التحقق من إصدار الحل الدائم، والتأكد من تثبيت أحدث إصدارات الثيمات والإضافات. إذا استمرت المشكلة، يرجى فتح تذكرة دعم جديدة هنا.
Problem: The client is facing two issues with their multilingual website using WPML: 1. The 'Send Request' button does not link to the correct language-specific page. 2. Extra top and bottom margins appear on English pages after translation, which are not present in the Greek version. Solution: For the 'Send Request' button translation and linking: 1. Navigate to WPML >> String Translation. 2. Click on the 'Admin texts translation' link under the 'Not seeing strings that you are looking for?' section. 3. Search for the button URL and enable its translation. 4. Return to WPML >> String Translation and add the translation for the button URL. For more details on string translation, visit WPML documentation on finding and translating strings. For the page design sync issue: 1. Go to WPML >> Settings > Custom Fields Translation. 2. Search for fields starting with 'qodef_'. 3. Set the layout fields to 'Copy' to ensure they sync in secondary languages. 4. Open the default language home page in Edit mode and press 'Update' to sync the page options fields into the secondary language. If similar issues occur on other pages, re-saving the default language page should resolve the issue.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit WPML Support Forum.
Problem: You are using WPML and WPForms together and encountering a JavaScript error on translated pages stating 'wpforms_settings is not defined'. This issue arises when the WPML String Translation plugin is active, preventing the wp_footer WordPress hook from firing, which WPForms relies on to write the wpforms_settings variable.
Solution: We attempted to reproduce the issue and escalated it for further investigation but found no immediate solution. We recommend: 1. Resaving the WPForms settings via WPForms > Settings. 2. Inspecting and resaving the wp_options table without making changes to see if it resolves the issue. 3. If these steps do not resolve the issue, and you have implemented a workaround by rebuilding the Elementor footer to hardcode language-specific content, you may continue with this solution if it is satisfactory. However, if the problem persists or you prefer a different solution, we suggest opening a new support ticket. We also recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
If further assistance is needed, please do not hesitate to contact us at the WPML support forum.
