Problem: When switching from German to English on the website, the menu remains in English and does not switch back to German, despite the page content changing to German.
Solution: 1. Verify if the issue is caused by AJAX by reloading the page (using command/alt+R). If the correct elements load after a manual refresh, AJAX might be the cause. 2. Ensure that the language filtering for AJAX operations is enabled in WPML. Navigate to WPML → Languages, scroll down to 'Language filtering for AJAX operations', and check if 'Store a language cookie to support language filtering' is activated. 3. If the problem continues, deactivate other plugins temporarily to identify if any are interfering with the language switching. 4. Check your theme settings to see if you can disable AJAX loading. 5. If these steps do not resolve the issue, contact the theme's author and suggest joining our Global Program to ensure full compatibility with WPML. 6. You can also check your theme's compatibility with WPML on our theme compatibility page.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client is experiencing an issue where the status of a page remains set to editing and the page cannot be accessed in English, even though the translation has been completed for over 8 hours. Solution: We recommend updating the WPML plugin to the latest version, currently 4.6.8, as well as any add-ons, to ensure all bug fixes and improvements are applied. Additionally, updating WordPress to the latest version is also advised. You can find the latest releases and update instructions under My Account -> Downloads. Before updating, please make sure to backup your database. After updating, if the issue still persists, try making a small modification to the original product, save it, and then navigate to the WPML translation editor to finish the translation again.
If this solution does not seem relevant to your situation, please do not hesitate to open a new support ticket in our support forum.
Problem: The client is experiencing intermittent issues where the texts to be translated are not displayed when trying to translate a page from the page list or the WPML page translation management, even after increasing the memory limit in the
1
wp_config.php
file. Solution: If you're experiencing this issue, we recommend trying to switch between the Visual and Text tabs in the translation editor. If the problem persists, we suggest activating the WPML advanced translation editor, which not only should resolve the display issue but also offers additional features for a better translation experience. For more information on how to use the WPML advanced translation editor, please visit our documentation.
If this solution doesn't look relevant to your situation, please open a new support ticket and we'll be happy to assist you further.
Problem: The client was unable to see a newly added translated product on the WooCommerce shop page in languages other than the original language, Swedish.
Solution: 1. We acknowledged the client's workaround of publishing the product in all languages from the admin product page. 2. We identified that the issue was likely due to a glitch during the translation process, where the URL for the translated pages was incorrect, showing a query string format instead of the correct permalink structure. 3. We confirmed that the normal procedure for translating products is detailed in our documentation: Translating Products Automatically. 4. We advised the client to follow the normal translation procedure and to contact us if the issue reoccurs.
Problem: The client wants to identify when translated content has been manually modified, so a warning can be shown to the user indicating that they have manually modified the translations. This is to ensure that users can check the translated version again after updating the original content. Solution: We regret to inform you that it is not currently possible to automatically identify manual modifications in translations to trigger a warning. However, you can review the content added by translators by navigating to WPML > Translation Management > Jobs. There, you can use the filter next to the "Translated by" column to see who translated what. For visual guidance, please refer to this screenshot: https://tinyurl.com/2gkyok5s.
To review translations, this feature is only available for machine translations. For more information on how to review automatic translations, please visit our documentation: How to review automatic translations on your site.
If this solution does not seem relevant to your situation, please do not hesitate to open a new support ticket with us for further assistance: Contact WPML Support.
Problem: The client is unable to find shipping labels in the string translation area of the WPML plugin. Solution: We recommend the following steps: 1. Enable auto-register strings for translation by following the instructions provided here: Enabling auto-register strings. 2. If the shipping labels still do not appear, try translating admin and settings strings as outlined in this documentation: Translating admin and settings strings. Please ensure to backup your database before making any changes.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us here.
Problem: The client has registered the site as a development site, but WPML Media is not registered. Solution: We recommend completing the installation of WPML using the WPML Wizard. It's possible that the WPML installation process has not been finished. For guidance, please refer to our Getting Started Guide.
Problem: The client is unable to access the order received page in secondary languages on their multilingual website, and instead encounters a 404 error page. Solution: If you're experiencing a similar issue where the order received page is not displaying correctly in secondary languages and shows a 404 error, we recommend you check for a known issue with WPML. Please visit the following documentation:
Before making any changes, ensure you back up your database. If this solution does not seem relevant to your situation, please open a new support ticket with us, and we will be happy to assist you further.
Problem:
The client customized a WooCommerce email template ("Customer invoice / Order details") by changing the body text and needed to translate the new version from English to Italian and French.
Solution:
We asked the client to clarify whether the customization was done directly in the WooCommerce email template or through a customization in the theme's functions.php file. We also provided a link to our documentation on how to translate WooCommerce emails, which includes steps to follow after scanning the theme. The client then realized they had not scanned the child theme and upon doing so, found the string they were looking to translate.
Problem: The client has a widget with recommended posts created using WP Bakery that does not display a translation option, resulting in the sidebar widget showing the English version on all translated pages. The client also wants to remove the '(EN)' language code from the English version of the widget. Solution: We provided a workaround for translating the widget title: 1. Open the
file. 2. Locate the following snippet around line 124:
1
<div class="gp-widget-title">
3. Replace it with the provided code that includes WPML filters and actions to register and translate the string. 4. Visit the page with the issue in the original language to register the string. 5. Go to WPML > String Translation and translate the string under the 'WordPress' textdomain. 6. Repeat these steps in the
1
gp_vc_showcase
file. For the issue with the YARP plugin, we opened a separate ticket.
Problem: The client is experiencing an issue where automatic translations with DeepL are defaulting to Portuguese from Portugal (PT-PT) instead of Brazilian Portuguese (PT-BR) when translating content. Solution: We have implemented a fix in our systems to address this issue. We recommend that the client updates to the latest version of WPML to resolve the problem with DeepL translations. After updating, the client should be able to translate to Portuguese - BR without the translations defaulting to Portuguese - PT.
Problem:
Some links in the Elementor widget were not updating in the page translation and remained in the default language.
Solution:
We registered the Elementor widget for the Image Hover effect element using the WPML Compatibility Test Tools plugin. Here are the steps we followed:
1. We added the following custom XML configuration code to WPML -> Settings -> Custom XML Configuration:
Problem: The client is trying to change the Genesis Layout for a second language page. The layout automatically updates to match the original language layout, and manual changes to the layout are not being saved.
Solution: We recommend navigating to WPML > Settings > Custom Fields Translation, then clicking on Show System Fields. Here, find and unlock the
1
_genesis_layout
field and set it to "Not Translate". This should allow for different layouts to be selected for each language without being overridden by the original language layout.
If this solution does not seem relevant to your issue, please feel free to open a new support ticket by visiting our support forum.
Problem: The client was experiencing an Internal Server Error which was resolved by increasing the memory limit. However, they encountered a new issue where the English event page of their Events Calendar was showing a blank page, unlike the default Japanese page. The client suspected this was due to the plugin using a 'slug' to display events rather than a traditional page, which might not be recognized when the '/en/' language code was added to the URL.
Solution: We explained that the 'events' page is an archive page generated by the plugin and not a regular page that can be edited. The reason the English translation of the 'events' page was blank is that there were no events translated into English. We recommended going to the admin area, navigating to Events > Translate an event post, and ensuring that the events are translated into English. This should allow the events to display correctly on the English language page.
If this solution doesn't seem relevant to your issue, please don't hesitate to open a new support ticket with us.
Problem: The client was experiencing an Internal Server Error when navigating the menu/page in a language that was not set as the default. The URL structure was incorrect, with the language code (/en/) incorrectly placed in the middle of the URL instead of at the end.
Solution: We reviewed the debug log and found no fatal errors related to the Internal Server Error. However, we noticed a PHP Notice error related to the 'The Events Calendar: Community Events' plugin. We deactivated this plugin and confirmed that the member pages then loaded correctly without the Internal Server Error. We provided a screen recording of the correct functionality for the client to review. We recommend the client to check their site after deactivating the plugin to see if the issue is resolved.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
