Problem: In WooCommerce, when admins process orders with their profile language set to English, it causes the product to switch to the English version, affecting product IDs and language in PDF orders. Solution: We recommend updating to the latest versions of WPML, String Translation, and WCML, which include fixes for this issue. Before updating, please ensure to take a full backup of your website and database. It is also advised to perform this update on a staging or development site first to avoid any disruptions to your live website.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to translate filter names from Swedish to English using the Barn2 Filter plugin on your site, but the filter names remain untranslated. Solution: First, ensure that the issue isn't related to known compatibility issues by checking our compatibility page and the Barn2 guide at Barn2's documentation. Next, use the WPML String Translation tool. When searching for the strings to translate, make sure to check the "Include translations" checkbox. This option helps in finding strings that might already be translated or registered in other languages. If the string's language is incorrect, you may need to correct the language of the string. For more details on locating untranslatable strings, visit this guide.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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 visit our support forum at WPML Support Forum.
Problem:
I use WPML for a Kadence based WordPress website. The original language is German, with English added through WPML. I am experiencing an issue with the translation of a checkbox in a Gravity Form. Originally, the German text in this checkbox was mistakenly identified as English, so I changed the language of those strings to German and added the English translations as explained in the WPML documentation.
Symptoms:
After making other unrelated edits, the German words AGAIN appeared in the English version of the form. The strings were listed as 'English' again in string translations, requiring me to manually reset them to German and add the English translations multiple times. Additionally, in the English version of a PDF generated by Gravity PDF, merge tags for those checkboxes only work if the checkbox mistakenly shows the German text. If they show the English text, merge tags seem to be empty.
Questions:
Why do the strings revert to being identified as English after I change them to German?
How can I ensure that the language settings for the checkbox remain consistent?
Why do the merge tags in the PDF only work when the checkbox shows the German text?
Solution:
As the German checkbox choices by mistake always were identified as English, I entered the English terms instead of the German. Then I added the German translations thru WPML's string translation. The result was that the German website had the correct German translations and the English the correct English translations. Plus, the merge tags are also filled as expected
Problem:
If you're using WPML with the Traveler Theme and Elementor Page Builder and notice that your website's CSS and styling are missing, along with errors in the WordPress backend, here's what you might be experiencing:
1. The website's CSS and styling are not displaying correctly.
2. There are errors in the WordPress backend preventing access to support and WPML configuration pages.
Solution:
1. We resolved the String Translation issue by deleting the
wpml_string_table_ok_for_mo_import
key from the
wp_options
table in your database. Please check if the error message has disappeared from your dashboard.
2. For the CSS issue, it appears that your theme created different settings per language, which caused the problem. To fix this, please go to your theme options and configure them the same way you configured them before installing WPML.
Problem: The client is experiencing an issue where the currency symbol on their website displays in Arabic when the site is in English, despite needing it to match the language currently being displayed (English or Arabic). Solution: If you're facing a similar issue where the currency symbol does not match the website's language, we recommend checking the solution provided in a related support ticket. This involves configuring WPML to correctly translate custom currency symbols in WooCommerce. You can find detailed instructions on how to address this issue by visiting the following link: Translation of Custom Currency Symbols in WooCommerce Using WPML.
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 at WPML support forum for further assistance.
Problem: You are experiencing a conflict between WooCommerce bookings and WPML plugins, which was resolved temporarily by deactivating the 'WooCommerce Multilingual & Multicurrency' plugin. Solution: We recommend trying the beta version of the WPML plugin to see if it resolves the issue. If the problem persists, we suggest setting up a staging site with minimal settings to further diagnose the issue.
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 continues, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that certain content does not appear in the translation section even after duplicating the content. Solution: We recommended translating the missing strings using the WPML String Translation. This can be accessed from the WordPress admin panel. Navigate to WPML > String Translation and search for the specific strings that are missing in the translation.
If this solution does not resolve the issue, or if it seems outdated or irrelevant to your specific 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 problems persist, please open a new support ticket.
Problem: The client is experiencing issues with translations from LILT not automatically synchronizing into WordPress through WPML. Instead, translations appear as 'Translation ready to download' in the WPML → Translation Jobs list, and the client has to manually click 'Download' to import them. They have set the 'Translation pickup mode' to 'The site will fetch translations manually' due to server stability issues when multiple translations were processed simultaneously. Solution: This setting requires manual intervention to download translations. Currently, WPML does not support automatic fetching via API or cron jobs for LILT translations, and there are no alternative methods provided within WPML for automatic synchronization in this scenario. To manage translations, you should use the 'Check status and get translations' button in the Translation Dashboard.
If this solution does not apply to your situation, 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 is experiencing an issue where clicking on the 'Japanese' language link on their WordPress site redirects to the wrong page instead of the Japanese translated page. Solution: We discovered that the issue was caused by custom redirect code in the
wp-config.php
file, which was incorrectly redirecting Japanese language links to the homepage. To resolve this, we commented out the problematic code:
After making this change, the redirection issue was resolved. We recommend clearing all sorts of cache and verifying if the issue persists.
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 issue persists, please open a new support ticket at WPML support forum.
Problem: You are trying to register the WPML plugin on your site but encounter a connection error: 'Connection error: Unable to get data from service. Detailed error: cURL error 28: Connection timed out after 10028 milliseconds.' This issue occurs because your hosting provider may be blocking access to our API. Solution: We recommend contacting your hosting provider and requesting them to whitelist the following domains:
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 needed, please open a new support ticket at WPML support forum for further assistance.
Solution:
- Open the pattern/template in Edit mode.
- Make a small change (e.g., add '+' in title), save, remove it, and save again.
- Send for translation again from Translation Management.
Problem: The client is experiencing issues where an updated image on the base language page is not reflecting in the translated versions (e.g., French). Additionally, despite previous complete translations, the WPML ATE editor shows incomplete translations and requires re-translation of content that hasn't changed. Solution: 1. If you're experiencing similar issues with image updates not reflecting in translated pages, we recommend making a minor edit to the base language page (like adding an extra space) and then saving it. This should prompt an update requirement for the translations. 2. Re-edit the translation to ensure it reaches 100% completion. This process helps in syncing all content, including any text associated with images. 3. If the WPML ATE editor does not recognize previously translated content, it might be due to the content being translated using a different editor (like the Classic Translation Editor or manually via the WordPress editor). In such cases, ATE cannot reuse translations as it relies on its own translation memory stored on servers. 4. To resolve this, continue using the original translation method (Classic Editor or WordPress editor) that was used initially. If you switch to using the ATE editor for future translations, it will store and reuse translations automatically for subsequent changes. For further guidance, refer to these documentation links:
If this solution does not apply to your case, 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 issues persist, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where WooCommerce emails occasionally display mixed language strings, with some parts in Estonian and others in English, despite attempting to translate these strings using String Translation, we understand your frustration. Solution: We have addressed this issue in the WPML 4.8 release. We recommend updating to this latest version to ensure that all WooCommerce emails are consistently in Estonian. If after updating, you still encounter mixed languages in your emails, it might be due to settings that need adjustment or additional translations that are missing.
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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to translate the checkout page on your WooCommerce site using WPML, but WPML does not find the string for translation, and Loco Translate cannot translate them. Solution: We have identified this as a known issue. We recommend checking the following errata page and applying the suggested workaround: https://wpml.org/errata/woocommerce-multilingual-cart-page-strings-not-translated-when-using-blocks/
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 the problem persists, please open a new support ticket for further assistance at WPML support forum.
Problem: You are using WPML on your website and encountering a file name mismatch error that prevents proper connection to wpml.org for updates, despite having registered the plugin and confirmed outgoing connections with your hosting provider. You are concerned about losing existing translations. Solution: We recommend enabling WordPress debugging to better understand the issue. Here are the steps you should follow: 1. Edit your wp-config.php file and add the following lines before the comment /* That's all, stop editing! Happy publishing. */:
If this solution does not apply to your case, 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. If issues persist, please open a new support ticket at WPML support forum for further assistance.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive