Problem: The client is experiencing an issue where the 'language switcher' is automatically removed from the menu after adding it. Solution: We recommend the following steps to identify and resolve the issue: 1. Create a full backup of your website. 2. Disable all plugins except for WPML and its add-ons. 3. Check if the issue persists. 4. If the issue is resolved, reactivate your plugins one by one and check after each activation to identify the plugin causing the issue. 5. If the issue still occurs with only WPML plugins active, switch to a default WordPress theme like TwentySeventeen and test again. It is best to perform these steps in a staging environment if possible.
If these steps do not resolve your issue or if the solution does not seem relevant, please open a new support ticket with us.
Problem: The client was unable to find the section labeled as per the documentation after publishing a page, which is necessary for registering a new Elementor widget for translation. Solution: We recommend adding the following code to the WPML-> Settings-> Custom XML tab:
After adding the code, update the page in the default language first before updating the translation to see the strings in the string translation. If this solution doesn't look relevant, please open a new support ticket.
Problem: The client was trying to translate the phrase 'قمة{category} أخبار' and expected to see 'Top {category} news' in English. Instead, they saw 'same-{category} أخبار'. Additionally, there was a concern about the default language of strings. Solution: We requested temporary access (wp-admin and FTP) to the client's site to better understand the issue. We also mentioned the possibility of installing a plugin like "Duplicator" or "All in One WP Migration" to replicate the site locally, with the client's permission. We emphasized the importance of the client making a backup before providing access. After gaining access, we could not find the untranslated content on the English version of the page provided. We asked the client to confirm if the issue was resolved. Regarding the default language of strings, we opened a new support ticket to address that separately.
Problem: The client is trying to translate strings from Arabic to English, but the string translation is offering Arabic translation options instead of English. This issue is observed when translating footer templates with different IDs for each language. Solution: If you're experiencing an issue where the language of a string is not correctly detected in the string translation, you can manually change the default language of the string. Here's how to do it: 1. Select the string in question. 2. Click on "change the language of selected strings". 3. Choose the correct language for the string. For a detailed guide, please refer to our documentation on how to change the source language of strings.
