Problem: The client's website is disconnected from WPML, and the supporter's test link is still present in the WPML account. The client needs to reconnect their website and remove the old supporter's test link. Solution: 1. Go to WPML → Translation Management and click on the Tools tab. 2. Expand the Connected sites dropdown. 3. Click the unlink icon next to the site you would like to disconnect. For more detailed instructions, please visit Automatic Translation Subscription for Multiple Sites.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please contact us through the WPML support forum.
Problem: The client is experiencing a redirect issue where a category page is incorrectly redirecting to a product page. Both the category and the product have the same slug 'sac-en-paille-marocain', which is causing the redirection. Solution: 1. Clear the website's cache, including server-side cache, to ensure no old redirects are stored. 2. Verify that no redirects are set in the Redirection plugin. 3. Change the slug of either the translated product or category to ensure they are unique. This step should resolve the conflict and stop the incorrect redirection.
If these steps do not resolve your issue, or if the information provided here becomes outdated, we recommend checking the related known issues and verifying that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
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 for further assistance.
Problem: You are seeing an error message on your dashboard while managing WooCommerce payment gateway settings. The error details include issues with unrecognized characters in the encoded string. Solution: We recommend you try the following steps to resolve the issue: 1. Close the error message by clicking 'x'. 2. Refresh your dashboard to see if the error persists.
If the error continues, it might be due to reasons that are no longer relevant or applicable to your current setup. 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 still persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was experiencing style issues and a key table error that prevented pages from being viewable. Solution: We ran the database troubleshooting options, which resolved the issues, and the pages are now viewable again.
If this solution does not relate to your issue, or if it seems outdated, we recommend opening a new support ticket. We also advise 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.
For further assistance, please visit our support forum.
Problem: The client reported that despite correct translations in the WPML string translation section, some sentences on certain pages of the Spanish version of their website were displaying in English. This issue was not present in an older staging version of the site. Solution: We identified that the issue was due to a conflict between language files from WPML and another language file. We recommended the following steps: 1. Ensure to back up your data. 2. Remove the language files or folders located outside of the
wp-content/languages/wpml
directory to avoid conflicts. 3. Do not drag these external language files into the WPML folder as it can overwrite existing translations. 4. If the issue persists, restore the
wp-content/languages/plugins
folder and remove the language files one by one to find the problematic file. 5. Uncheck the option "Cerca le stringhe durante il rendering delle pagine" to avoid rendering issues.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: If you're setting up WPML and cannot see the names of the languages to choose (Default language - Translation languages), and activating WPML disrupts the Elementor builder and styles, you might be facing a similar issue. Solution: We recommend reactivating WPML along with the WPML setup wizard. The issue with not seeing language names and the disruption of Elementor could be due to a stuck key in the "icl_admin_messages" table in your database. Removing this key should resolve the problem. If the styling issues persist after this fix, it's advisable to address them in a separate support ticket.
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 issue persists, please open a new support ticket.
Problem: The client's site is set to Translate Everything Automatically mode, but a newly created product category did not get automatically translated. Solution: We explained that automatic translation is only possible with the Advanced Translation Editor for specific content types such as posts, pages, templates, and other contents covered by our addons. To translate a product category automatically, the client should edit the original product category and then send a product with this category to automatic translation. Alternatively, creating a draft product, assigning all product categories, and sending it to automatic translation will also translate any product category not yet translated. For more details on translating taxonomies, we recommend reading our documentation here: Translating Post Categories and Custom Taxonomies.
If this solution does not apply to your case, or if it 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. If issues persist, we highly recommend opening a new support ticket for personalized assistance.
Problem: The client is experiencing an issue where the language switcher appears twice in the menu of their website: once as the first item and again as the last item, but broken. They want the language switcher to appear only once as the last item. Solution: We recommend clearing your browser cache as a first step, as this might resolve the issue of seeing the language switcher incorrectly. To do this, you can follow the steps provided in this documentation: WPML Language Switcher Options. If after clearing the cache the issue persists, it might be due to a configuration or a visibility issue that is not replicable on our end. In such a case, we suggest checking your menu settings in the WPML "Languages" section to ensure the switcher is set up correctly to appear only at the desired location in the menu.
If this solution does not apply or is outdated, or if you continue to face issues, please open a new support ticket. We also 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. For further assistance, you can contact us directly at WPML support forum.
Problem: The client is experiencing an issue where the translated taxonomy terms are not showing on the front end when the Dynamic Visibility feature by Jet Engine is enabled, although they appear correctly when the feature is disabled.
Solution: We recommend the following steps to ensure that the Dynamic Visibility feature works correctly with translated taxonomy terms in WPML:
1. Navigate to WPML -> Settings -> Custom XML Configuration tab.
2. Add the following code:
3. Save the changes.
4. Go to the page and edit in the default language, make a minor change (like adding a dot or word), and save.
5. Update the translation.
6. In the translation editor, locate the new fields with the name "jdev_value" and translate these as the names of these taxonomies.
7. Complete the translation to 100% and check the frontend.
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 Elementor heading titles and paragraphs on your site but the translations are not displayed, only the original language. Solution: 1) Translate the template ID via WPML-> String Translation. After this step, the strings should work correctly in both languages. 2) To translate the related listings widget, add the following XML code in WPML-> Settings-> XML tab:
Please verify if the translations are now correctly displayed.
If this solution does not resolve your issue or seems outdated, we 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: The client is unable to translate the first horizontal timeline on their page using WPML because the Elementor Timeline Addons Plugin is not compatible with the WPML editor. Solution: We recommend adding the following custom XML configuration to WPML to make the Elementor widget translatable:
After adding this code, make a small change and re-translate the timeline. Additionally, we suggest sharing this solution with the plugin author and inviting them to join our GoGlobal program to enhance compatibility.
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 issue persists, please open a new support ticket.
Problem: The client needs to register an additional site, affitti.bosa.net, but their account is currently registered only for bose.net. Solution: If you're experiencing this issue, it's likely because you are using an End-user (one-site) license. This type of license is limited to one site only and does not allow for the registration of additional sites or license changes. For more information, please check out the following link: Transferring Account Renewals to Your Clients. To register more sites, you will need to purchase a new license. You can do this by visiting WPML Purchase Page. If the system does not allow you to purchase from the same account, you may need to create a new WPML account.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues at WPML 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.
Problem: The client was facing an issue where the 'read more' text in the posts was not translating correctly using WPML, despite other text translations working fine. This issue persisted even after deactivating the Post Type Order plugin and rebuilding the template. Solution: We identified that the untranslated 'read more' text was part of a Toolset template. To resolve this, we translated the specific text using the WPML Advanced Translation Editor (ATE) via the Translation Management section. After applying the translation directly in the Toolset template, the 'read more' button text displayed correctly in the desired language.
Please note that this solution might be outdated or not applicable to your specific case. If you're still experiencing issues, we 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 problem persists, please open a new support ticket.
Problem: The client was experiencing a critical error when switching to the German language on their website. Additionally, when in the English language, three products were displayed in German, which was not the case previously. Solution: We identified that the issue was due to the string "Alle %" not being translated properly. We corrected this translation issue, and the website should now function correctly without the critical error when switching languages. If you're experiencing similar issues, we recommend checking the translation of all strings in your WPML String Translation module.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
