Problem: The client is experiencing an issue where the Dutch (NL) top bar header on their website is incorrectly displaying the French translation instead of the Dutch one. Solution: We recommend checking the language settings used when the header was originally created. It appears that the header may have been initially set up in Dutch and then translated to French, which is causing the current issue. To resolve this, you should: 1. Confirm the original language of the header by editing the Dutch Header Template in Divi and checking the translation status in WPML > Translation Management > Dashboard. 2. If the header was indeed created in Dutch, edit it directly in Divi and update the translation from Dutch to French. 3. Since Divi templates should always be created in the site's default language, we suggest removing the global header template and recreating it in French. Afterward, translate it from French to the other required languages.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 needed, do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues with WPML where fields show as 100% translated after saving, but the WordPress dashboard indicates incomplete translation with some fields having an orange light, this might be due to a known bug. This issue often occurs when translations are performed quickly, and it seems to affect various fields randomly, particularly when using Elementor and Bricks Builder. Solution: We recommend reopening the translation and saving the segment for a second time. This workaround has helped some clients while we continue to develop a permanent fix. Our developers were aware of this issue and already applied a solution.
If this solution does not resolve the issue or if it reoccurs, it might be due to the problem being outdated or not applicable 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 the problem persists, please do not hesitate to open a new support ticket for further assistance at WPML support forum.
Problem: You are trying to translate Elementor button links on your website, specifically to link to an archive page using a relative URL in the Elementor button link, like /evenement/. However, the 'Calendar' button redirects to the French version instead of the expected English archive page. Solution: We recommend checking our guide on translating URLs. When you encounter a page with untranslated buttons, search for the slug (for example, 'evenement') to see all URLs that contain it.
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 the problem persists, please open a new support ticket.
Problem: You are using Bricks builder 1.10.3 and WPML, and you encounter an issue where the Dutch translation of a page appears empty even though it has been translated. Solution: We recommend checking the workaround on this page. First, disable the "I prefer bigger segments" option. Then, update the page in the default language and subsequently update its translation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with saving special characters and flags in WPML while using Elementor. The special characters and flags are not displayed correctly after being saved. Solution: We recommend switching to the previous version of the Advanced Translation Editor to resolve this issue. Here are the steps to follow: 1. Go to the top right corner of the translation editor. 2. Click the gear icon. 3. Enable the option "Use the previous version of the Advanced Translation Editor." Please try these steps and check if the special characters and flags display correctly.
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 the problem persists, please do not hesitate to open a new support ticket at our support forum.
Problem: The client was having issues with an archive page created with Bricks builder, where they used a loop to display categories and dynamic data to call the featured image from an Advanced Custom Fields (ACF) field for custom taxonomy types. Solution: We recommended the client to manually edit the translated taxonomy that was causing the issue and simply click save. This action should resolve the problem with the display of the translated taxonomy.
If you're experiencing a similar issue, we recommend you try manually editing the translated taxonomy and saving it. However, this solution might be irrelevant if it's outdated or not applicable to your case. If the problem persists, 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 you still need assistance, please open a new support ticket at our support forum.
