Problem: The client was experiencing an issue with a Dutch translation of a button link URL on a slider that appears four times on a page. The link was supposed to direct to a Dutch version of a product page, but it was not working correctly. The client had tried re-translating the page and making minor edits, but the issue persisted. The problem was specific to the Dutch translation, as other language translations were functioning properly.
Solution: We asked the client for a clear explanation of the issue and to provide examples or screenshots to better understand the problem. We also advised the client to avoid including unnecessary details such as menu items in their description to prevent confusion. After the client managed to resolve the issue on their own, they informed us that the topic could be closed.
If you're experiencing a similar issue, we recommend providing a clear and concise description of the problem, along with any relevant examples or screenshots. This will help us assist you more effectively. Please note that the solution provided here might be outdated or not applicable to your case. We highly recommend checking the 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 issue persists, please open a new support ticket with us.
Problem: The client was experiencing issues with WPML when adding keywords to product pages using RankMath. After adding keywords, the translated content would revert to English, and links would sometimes not work correctly. This was time-consuming and frustrating for the client, who had to repeatedly check and fix the translations and links.
Solution: We recommended a workaround by adding the following code to the
wp-config.php
file to prevent automatic updates of translations, which might be causing the issue:
Please note that the solution provided might be outdated or not applicable to your case. If you continue to experience issues, 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: The client was experiencing issues with WPML not accepting translations of keywords that have the same initial words (synthetic names). Specifically, when the first two words of the keywords were the same, WPML would not translate them unless they were interspersed with other keywords that had different initial words.
Solution: We asked the client if these keywords were not being translated using automatic translation and whether they could see them in the Advanced Translation Editor. We also inquired about where in the backend they were adding these keywords.
If you're experiencing similar issues with keyword translation in WPML, we recommend checking if the keywords appear in the Advanced Translation Editor and ensuring that automatic translation is functioning correctly. Additionally, consider the structure of your keyword list and try interspersing keywords with the same initial words with others that start differently to see if this resolves the issue.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we highly recommend checking the related 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.
Problem: The client is experiencing issues with broken links on their website after updating page slugs using the Advanced Translation Editor (ATE). They noticed that the WPML slug is edited and changed when manually updating a page in WPML, leading to broken links. The client is concerned about why this issue did not occur before and how to prevent it from happening.
Solution: We recommend checking the WPML > Settings > Translated documents options > Page URL to ensure that the 'Translate' option is selected. This means that when the page slug is changed in the default language, it should also be translated in ATE. If the slug is translated and the page translation is completed, it will be saved to the translation memory and will not require retranslation unless the slug is changed again.
For Divi module users, ensure that the 'Adjust IDs for multilingual functionality' option is enabled in WPML > Languages. This will allow WPML to automatically adjust the translation page slug in the frontend, preventing broken links.
If you follow these steps and still encounter issues, or if this solution does not seem relevant to your problem, please open a new support ticket with us, and we'll be happy to assist you further.
