Problem: The client is experiencing issues with extra identifiers appearing on the French page of their website and discrepancies in the English translation after switching from the Classic Translation Editor to the Advanced Translation Editor. The issues persist even after attempting to switch back.
Solution: If you're experiencing similar issues, we recommend the following steps: 1. Confirm Advanced Translation Editor is Active: Ensure that the Advanced Translation Editor is selected as your preferred editor in WPML → Settings under the Translation Editor section. 2. Update the Original English Page: Perform a minor update on your original English page to ensure WPML has the latest version of your content. This can be done by editing the page under Pages → All Pages or Products → All Products if it's a product page. 3. Resubmit the Translation Job for French: Using the Advanced Translation Editor, re-translate the content to correct any discrepancies and remove extra identifiers.
Please note that this solution might be 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 open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to locate the Divi Flash FAQ module in WPML's String Translation. Additionally, extra identifiers are appearing on the French page after switching to Classic Translation mode, and the English translation in WPML differs from the original content. Solution: For the Divi Flash FAQ module not being recognized by WPML, we recommend updating your custom XML configuration. Please ensure to have a backup and follow these steps: 1. Navigate to WPML > Settings > Custom XML Configuration. 2. Update with the following code:
3. After saving this configuration, edit the FAQ Item on the original page, save the page, and open the translation editor. You should now see the strings of the module inside the translation editor.
If this solution does not resolve your issue or seems irrelevant due to being 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: You are trying to translate products in WooCommerce using WPML and after upgrading to WPML version 4.7.6, you encountered issues with translating products. As an administrator with permission to translate, the 'Translators Tab' is empty, and you cannot add yourself as a translator because it says the role already exists. Additionally, you noticed an error with the Advanced Translation Editor indicating 'No sitekey found for this website'. Solution: We recommend activating the Advanced Translation Editor in the WPML settings and checking the Translators section to confirm that the account has the administrator role and both languages assigned. You should then try sending products to translation and opening them in the Advanced Translation Editor. If issues persist, test with another admin account and ensure the user profile has a name, email, and nickname filled in. If this solution does not resolve your issue or 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. We highly recommend opening a new support ticket if needed.
Problem: You are trying to use automatic translation with WPML on your site, and you encounter a prompt stating: 'Your default language, English, must be mapped to a supported language in order to use automatic translation.' Despite resetting WPML and clearing related entries in the wp_options table, the issue persists. Solution: First, ensure that your site is properly registered with WPML. If you encounter issues with site registration, follow the steps outlined in this documentation. Next, navigate to WPML → Settings → Translation Editor. Switch from Advanced Translation Editor to Classic Translation Editor, and then switch back to Advanced Translation Editor. This process may help in resolving the language mapping issue.
If the problem persists or the solution 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. If necessary, please open a new support ticket at WPML support forum for further assistance.
The client wants to add a floating flag icon in the backend of their website using the DIVI theme to switch languages, similar to the GTranslate feature. WPML does not have a built-in feature or hook to support this.
Solution:
We recommend implementing a CSS workaround to achieve a floating language switcher. You can add the following CSS code to keep the Dashboard language switcher floating:
Please note that this solution might be 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: You are trying to translate your website using WPML and have encountered issues with translations on specific URLs. The Chinese version correctly corresponds to the homepage, but the English and other languages are incorrect. Some content, including text and format elements, are not translated across various pages and sections. Solution: 1) For the homepage menu issue, go to Appearance -> Menus, switch the language to English, select the header menu, and check the menu item label. 2) If you created the content using Elementor, the widgets might need to be registered for translation. We recommend checking our guide on registering page builder widgets for translation.
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 you still need assistance, please open a new support ticket at WPML support forum.
