Problem: If you're encountering an issue while trying to upload XLIFF translation files and are facing an error, it's important to ensure that the files are in the correct format. Solution: First, verify that the files you are attempting to import are indeed in XLIFF format. RTF files, for example, cannot be imported into WPML. XLIFF files should be the same as the ones exported, but translated using CAT tools or similar software. It's also crucial to note that exported files are connected to create a translated job and can only be imported for the one from which they were exported. For more information on configuring XLIFF file options, please visit our documentation:
If this solution doesn't seem relevant to your situation, we encourage you to open a new support ticket for further assistance. You can do so by visiting the WPML support forum.
Problem: The client is experiencing unwanted automatic translations with the new WPML version, which incurs charges. The client wishes to disable this automatic translation feature and revert to having the option between automatic and manual translation. Solution: 1. Open the Advanced Translation Editor. 2. Click on "Undo Translation". 3. In the popup, select the option to disable automatic translation for future translations. 4. This is a one-time action; once set, automatic translations will not occur by default. 5. If you undo an automatic translation, you will not be charged for that content. If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client needs to send account verification emails in three languages (English, German, and Spanish) but currently, they are only being sent in English. Solution: First, we need to identify if a specific plugin is being used to send the verification emails. If so, the solution may vary depending on the plugin. However, in general, to send emails in multiple languages, some coding is required. We recommend following the instructions in our documentation on sending emails with WPML:
Problem:
The client wants to translate the "I would like to receive exclusive emails with discounts and product information" string that is coming from Mailpoet plugin
Automatic translation 100$ first limit has been reached, but the user cannot proceed with the payment.
Solution:
If you use pay-as-you-go, there are two safety limits that prevent you from accidentally spending too much and protect us from fraud. These limits occur the first time you spend €100 and €4,000 in one month. If you reach these limits, you will be asked to pay before you can continue translating. At the end of the month, the amount you paid will be deducted from your invoice.
If you face this issue, please open a ticket in our support forum.
Problem: The client is asking if they can safely delete the
icl_string_pages
table from the database after having stopped using WPML on their website. Solution: We informed the client that if they do not plan to use WPML on their website in the future, they are free to delete the WPML tables from their database. We also provided a link to our documentation for reference on WPML tables:
Problem:
I have this error message, I need your support please. I think it's because the value it's HTML. (Please note I deleted this HTML content for this question because it was too long).
I tried to search this values in my database, at 'formeld_icl_strings' table to delete it but I can't find it no where...
This is the error message I have in all my dashboard pages:
We have detected a problem with some tables in the database. Please contact WPML support to get this fixed.
WordPress database error: Could not perform query because it contains invalid data.
[status] => 0
[translation_priority] => optional
[allow_empty_value] =>
) Solution:
The error could be a false positive. Could you please close the message via the (x) icon in the top right corner? After that, please check if the banner will appear again.
Problem: The client was unable to view all created templates/pages in different languages when using Elementor Pro with the WPML plugin. Templates were not appearing in the list to be used as a base for translation, and they only became visible when the WPML plugin was deactivated. This issue was causing difficulties in creating a new version of a template in a different language. Solution: We found the missing templates in the database using the Adminer tool. We then adjusted the page edit URL to include the specific language parameter, which allowed the templates to load correctly. For example, to edit a Spanish template, the URL was modified to:
After making this adjustment and updating, the templates started showing correctly in the Templates section. If this solution does not seem relevant to your issue, please open a new support ticket with us, and we will be happy to assist you further.
Problem: You are trying to translate a page using the WPML translation editor, but when you click to edit the French translation, it opens an empty (white) page. This issue has occurred despite using different browsers and ensuring that admin/translation user details are correctly set. Solution: We checked it and the issue was related to escaping special characters in regex for some glossary entries. Our developers worked internally and found a solution. If you're still experiencing a similar issue, please open a new ticket for us to double-check it.
Problem:
It was proving difficult to locate a string which continued to be displayed in the default language on the front end on translated pages.
Solution:
Somehow the small string in question ("KM") was wrongly labelled as originally Russian. Locating the text within String Translation the language can be reset to the correct language, and then a translation to Russian provided.
Problem: The client was unable to translate certain texts on WooCommerce pages created with JetWooBuilder and Elementor templates. Specifically, the client had issues translating the 'Add to Cart' button on a listing grid and activating a specific template for posts in the English version of the site. Solution: 1. We recommended translating the Woo Builder templates to address the initial translation issues. 2. To fix the translation of the 'Add to Cart' button on the listing grid, we set the listings to be translatable in WPML under the Post Type Translation section and asked the client to translate the listings. 3. For the issue with the single post template not appearing in the English version, we found that the template was saved as a draft. We published the template, which resolved the issue.
Problem: The client is trying to set Chinese pages to private, but the status keeps reverting to public. They have already disabled the option to copy the publish status from the English version to the Chinese version.
Solution: We recommend disabling the "Synchronize private flag" feature. To do this, go to WPML > Settings > Posts and pages synchronization.
Here is a step-by-step guide:
1. Navigate to the WPML Settings page.
2. Locate the 'Posts and pages synchronization' section.
3. Uncheck the option for 'Synchronize private flag'.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
