Problem: You are trying to translate pages using Avada Builder, but not all parts of the page are translated. Solution: First, ensure that the text you are trying to translate appears in the translation editor.
Here are the steps we recommend: 1. Make a slight modification to the original page and save it. This action can help refresh the page translation. 2. Navigate to the WPML translation editor to see if the changes are reflected and the missing content appears for translation. 3. Verify that you are using the latest version of your theme, as outdated themes can sometimes cause issues with translation plugins.
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 floating language switcher set up following the WPML documentation is not clickable. Solution: We recommend increasing the z-index value of the "wpml-floating-language-switcher" CSS selector to 9999 to ensure it appears above other page elements. You can add the following CSS to the custom CSS section of your theme:
This adjustment should make the language switcher clickable. If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket with us for further assistance.
Problem: You are trying to translate pages using Avada Builder, but not all parts of the page are translated. Solution: First, ensure that the text you are trying to translate appears in the translation editor.
Here are the steps we recommend: 1. Make a slight modification to the original page and save it. This action can help refresh the page translation. 2. Navigate to the WPML translation editor to see if the changes are reflected and the missing content appears for translation. 3. Verify that you are using the latest version of your theme, as outdated themes can sometimes cause issues with translation plugins.
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.
The link associated with the Divi button is not appearing for translation
Solution:
We recommend adding the WPML language configuration code in WPML>>Settings>>Custom XML Configuration. After adding the following code, please update the page in the original language after making a minor edit to refresh the translation settings. Then, update the translation to check if the issue persists.
For more details, you can refer to a similar issue discussed in our forum: WPML Forum Discussion.
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.
Problem: After installing WPML and activating automatic translations from French to English and Spanish, the client encountered issues with the language switcher module not displaying correct pages and English-translated text widgets showing 'widget body' followed by a serial number instead of the translated text.
Solution:
There was another temporary issue in client's site which they fixed and it resolved the said issue.
We recommended checking for conflicts with other translation plugins, as this was identified as the cause of the issue. Additionally, we advised following our Elementor tutorial, particularly the sections on templates and widgets, which could potentially resolve the described problems.
If this solution does not apply to your situation, or if it 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. Should these steps not resolve your issue, please do not hesitate to open a new support ticket with us for further assistance.
Problem: If you're experiencing issues where text widgets do not display translated content in English and instead show 'widget body' followed by a serial number, while other languages like Spanish work fine, this might be due to a conflict with another plugin. Solution: We recommend checking if you have another multilingual plugin activated, such as TranslatePress. If so, deactivate the other multilingual plugin. In this specific case, deactivating the 'TranslatePress - Multilingual' plugin resolved the issue. It's important not to activate two multilingual plugins at the same time as they can conflict with each other.
If this solution does not apply to your case, or if it seems outdated, 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 through our support forum at WPML support forum.
Problem: You encountered an issue with some tables in the database while attempting to add translations in WPML. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Click the small 'x' icon on the warning message to attempt to remove it. 2. Refresh the dashboard to see if the warning message still appears. If the message disappears, everything is likely in order. If the issue continues, please let us know so we can investigate further. For more detailed information, please refer to the following documentation: https://wpml.org/faq/how-to-deal-with-error-messages-about-a-broken-table-that-needs-fixing/#problem-with-some-tables-in-the-database
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 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.
Problem: You are translating a site from German to English and encounter an issue where Consent messages in Everest Forms do not appear in the string translation.
Alternatively, client changed the Consent fields to a Checkbox field and this now appears in the String translation.
If the solution provided here becomes irrelevant due to updates or if it does not apply to your case, please open a new support ticket. 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. For further assistance, you can also visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is unable to translate default sections of a paid theme using WPML, as these sections are not appearing in the string translation. Solution: 1. Navigate to WPML >> Translation Management. 2. Scroll down to the Other texts (Strings) section. 3. Click “Modify” and ensure the option “Untranslated strings that I encounter on the front-end while logged in” is selected, and click the “Save settings” button. 4. Visit the frontend page in the secondary language where this section appears. 5. Search for the required strings one by one, add translations, and use the search filters if needed.
This solution might be irrelevant if it's 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 this does not resolve your issue, please contact our support team for further assistance.
Problem: The client has completed translations for pages using the translation editor, and these are registered as completed in the Translations panel. However, the translations are not displaying on the frontend. The client recently switched from using Bakery builder to Elementor Pro and updated to the Hello Elementor child theme. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Edit the page in the default language. 2. Add "V2" to the title and update the page. 3. Delete the "V2" from the title and update the page again. 4. Update the page's translation. After completing these steps, please check if the translated page is now visible on the frontend.
This solution might be irrelevant if it's 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 issue persists, please open a new support ticket at WPML support forum.
Problem: The client has created a custom post type named 'Galleries' for their website to transition galleries from an old theme to a new one while maintaining permalinks and structure. However, the '+' icon that allows for translation in WPML is not appearing for this new custom post type, although it appears for 'Pages' and 'Posts'.
Solution: If you're experiencing this issue, we recommend that you make your post type translatable in WPML. You can do this by navigating to WPML -> Settings -> Post Type Translations. For detailed instructions, please visit Translating Custom Posts.
Please note that this solution might be irrelevant if it's 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 for further assistance.
Problem: The client reported an issue with the Croatian version of a WooCommerce product page showing an ERR_TOO_MANY_REDIRECTS error and having a URL with double slashes. Additionally, the featured image and attribute images were not displaying on the translated product page.
Solution: We advised the client to first take a full backup of their site and database. The steps included: 1) Checking in String Translation for the problematic URL and correcting it for the Croatian translation. We also suggested running the process to scan and auto-adjust links under WPML -> Settings -> Translate link targets. 2) Deactivating all plugins except for WPML, String Translation, WooCommerce, and WCML to check if the issue persists. 3) Switching to a standard theme like 2024 or 2021 to rule out theme-related issues. 4) Re-activating plugins one by one to identify any conflicts, and then switching back to the original theme to check for issues.
Alternatively, client found that plugin SEO press was causing the url to look like this, resetting the plugin fixed the issue.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client installed the new Buddyboss Glue addon and encountered issues with managing translations of profile types. They observed duplicated entries. Solution: 1. Set profile types as not translatable in the new BPML version. Instead, use WPML > String Translation to manage these translations. 2. Delete any duplicated profile type entries.
For further details on managing translations, visit the WPML documentation: Translating Your Contents.
If this solution does not resolve your issue or seems outdated, we 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: WPML Support Forum.
Problem: The client is experiencing issues with translating the checkout and cart pages on their WooCommerce site using Elementor and WPML. Specifically, the checkout page redirects to the cart page, and there are difficulties in translating labels and fields within the checkout form. Solution: 1. We recommend using the String Translation module as explained in the WPML documentation. You can find the guide here: String Translation documentation. 2. Ensure that the WCML setup is completed as per the instructions, which could help in managing the translations for the checkout and cart pages effectively. The setup guide is available here: WCML setup instructions. 3. If the issue persists, consider checking and adjusting the permalink settings to 'postname' for better SEO and functionality, which might resolve some redirection issues. 4. For translating links and ensuring they point to the correct language version, follow the guide on translating links here: How to translate links.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your specific case, please open a new support ticket. We highly recommend checking related known issues at 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 also contact our support team directly at WPML support forum.
Problem: You are trying to translate Ninja Forms date picker string. While in one language it works in another it doesn't Solution: The issue might be related to known problems with several themes and plugins not loading translations correctly in WPML. Specifically, you can refer to these errata pages for more details:
To resolve the issue with Ninja Forms, please follow these steps: 1. Ensure you make a full backup of your website. 2. Navigate to
wp-content/plugins/ninja-forms/ninja-forms.php
and locate line 779. 3. Change the following line of code:
unload_textdomain('ninja-forms');
to:
unload_textdomain('ninja-forms', true);
This modification has been tested and should help resolve the translation issues.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, 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
