Problem: The client needed to know how to restart automatic translations in WPML after adding new translation credits. Solution: 1. Navigate to WPML -> Settings. 2. Change the translation method to
'Translate what you choose'
and save the changes. 3. Switch the translation method back to
'Translate everything'
and save again. Upon saving, a window will appear asking what to do with the existing content. Here, you can start the automatic translation for it.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. Additionally, 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, please visit our support forum at WPML Support Forum.
Problem: You are trying to translate all page content, including content created in Avada, but the translation editor does not include Avada fields. Additionally, you encountered a WordPress database error indicating invalid data during the translation attempt. Solution: We recommend following these steps to resolve the issue: 1. Edit the page in the original language. 2. Resave the widgets on the page. 3. Make slight changes to the page and update it. 4. Go to the translation editor; all the content should now appear, allowing you to complete the translation.
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. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: The client reported that icons on their website's German translation pages were displaying as squares instead of the intended icons. Solution: We identified that the issue might be related to the Cross-Origin Resource Sharing (CORS) Policy, as the client uses different domains per language. We suggested checking the browser console for any CORS-related error messages and sharing these with their hosting support to allow access to font/icon files across domains. Additionally, we recommended a potential fix involving setting the 'Access-Control-Allow-Origin' header, which can be found in detail here: WPML documentation on CORS and custom fonts.
If this solution does not resolve your issue, or if it 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: You have updated links in the English version of your website, but the translated versions still display the old, inactive links. Solution: We recommend using the 'Translate Link Targets' option found in WPML → Settings. If this does not resolve the issue, please follow the step-by-step guide on translating links using the Advanced Translation Editor, which can be found here: Translating Links with Advanced Translation Editor. Before making any changes, ensure to backup your database.
If this solution does not apply to your case because it might be outdated, or if you encounter further issues, 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 you need additional assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are unable to save a translation using the Advanced Translation Editor. When you try to save, nothing happens. Solution: We recommend checking if a link for the texts is missing in your translation setup. Adding the necessary link as indicated in the documentation might resolve the issue. If you're experiencing this, please refer to the Advanced Translation Editor documentation for detailed guidance.
If this solution does not apply because it's outdated or not relevant 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. Should these steps not resolve your issue, please open a new support ticket.
Problem: If you're experiencing issues where the auto-translated product descriptions do not maintain the original line breaks, resulting in all paragraphs merging into one, we can help.
Solution: We recommend turning off the "I prefer bigger segments" option in the Advanced Translation Editor (ATE) and then resending the product for automatic translation. Make sure to select the "Overwrite existing translations" option. This workaround is detailed in our errata page, which you can find here: https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-edior/.
Additionally, subscribing to the comments on the errata page will keep you updated on when the issue is resolved.
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.
Problem: You are unable to save 'TBD' next to the Zulu language in the Edit Languages section. When you try to save, the screen refreshes, and the update is not saved.
Solution: We discovered that the 'Default locale' field for the Zulu language was empty, which caused the issue. To resolve this, you need to fill in the 'Default locale' field. The correct locale code for Zulu in South Africa is
zu-ZA
. You can adjust this default locale according to your needs. For more information on locale codes, visit Locale Codes Documentation.
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.
Problem: If you're experiencing issues with the Ninja Forms Multilingual plugin where the PDF Form Submission extension fails to export PDFs when a form includes a checkboxlist field, this might be due to a compatibility problem between these plugins.
Additionally, subscribing to the comments on this errata page will keep you updated on when a permanent fix is rolled out.
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 at WPML support forum for further assistance.
Problem: You are trying to ensure that all original text on your site is translated, but you've encountered an issue where not all text is translated, particularly with WP Bakery modules. Your theme does not include a wpml-config.xml file, despite claiming WPML compatibility. Solution: We recommend following our guide on registering WP Bakery modules for translation. You can find the guide here: Register Page Builder Content for Translation. Please try the following steps: 1. Register one module by adding the necessary code to the WPML-> Settings-> Custom XML tab. 2. Edit the page in the default language, make a minor edit, and update it. 3. Attempt to translate the page again and check if the strings appear correctly in the translation editor.
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.
Problem: If you browse to the website without the language suffix (e.g., https://telium.io), the site renders incorrectly. This issue is likely related to how WPML handles redirection and language URL settings. Solution: We recommend checking the WPML settings under WPML → Languages → Language URL format. If you have the option 'Use directory for default language' enabled, you have two main options: 1. Uncheck the 'Use directory for default language' option. This change will allow https://telium.io/ to display the root page as intended. 2. Set up a redirect from https://telium.io/ to https://telium.io/en/ if you prefer to keep using the 'Use directory for default language' setting. You can find detailed instructions on setting up this redirect here.
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 is using the WCFM - WooCommerce Multivendor Marketplace plugin along with its additional plugins. After exporting translations from Polylang to WPML, some Hebrew strings were mistakenly recognized as English. The client attempted to correct this using the 'Change language of selected strings' feature in WPML, but this led to further issues. Specifically, the menu item 'Store Vendors' in English was incorrectly changed to 'Store Name Vendors', and in Hebrew, it appeared as 'Vendors שם החנות'. Solution: We recommend locating the strings in question within WPML > String Translation. From there, change the default language of the string to a language that is not currently set up on the site. This will allow you to add a 'translation' for the English language, effectively correcting the string in both languages.
If this solution does not resolve the issue, or if it seems outdated or irrelevant 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. Should further assistance be needed, please do not hesitate to open a new support ticket with us at WPML support forum.
Problem: The client was experiencing issues with WPML where translations were not being applied correctly. Despite translating text and title bars to 100%, the changes were not reflecting on the site. Additionally, a persistent yellow gear icon indicated a malfunction in the WooCommerce Multilingual & Multicurrency plugin. Solution: We identified that the Advanced Translation Editor (ATE) ID on the client's website was invalid. We corrected this ID. We recommended the client to try translating the content again and to clear the cache after doing so to ensure the changes take effect.
If this solution does not resolve your issue, or if it 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 problems persist, please open a new support ticket for further assistance.
Problem: The client is experiencing issues with ACF fields not maintaining consistent category assignments across different languages in a WPML environment. Specifically, when adjusting categories in one language, they appear random or default to the first alphabetical categories in another language. Solution: 1. Ensure all categories are correctly translated under WPML > Taxonomies translation. 2. In the default original language, adjust the field group's settings to have "identical fields on all languages". 3. Create a new post or page and assign it to one of the categories listed in the ACF group configuration. Save and check if the field displays on the original language post. 4. Duplicate or translate the post to a second language and verify if the fields are visible and if the correct category is assigned. If these steps do not resolve the issue, we recommend trying to replicate the issue on the provided sandbox environment. Additionally, please ensure that you have the latest versions of all themes and plugins installed. If the problem persists, it might be due to an outdated solution or a different issue. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix. If necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to copy the content from an English page to a German page using the WPML plugin. When clicking the 'Overwrite with English content' button, the load wheel continues to spin indefinitely, and the 'Copy content from English' button becomes unclickable. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Delete the Translate page. 2. Remove it from the trash. 3. Edit the page in the default language. 4. Duplicate it. 5. Edit the translated page using the WordPress editor. 6. Click "Translate Independently". 7. Translate the page manually. For more detailed guidance on manual translation, please check this guide.
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: You have paid for a subscription and received 90,000 credits, but you are still receiving notifications about a debt and your account remains locked. Solution: We have identified that there is an unpaid invoice on your account. To resolve this issue and unlock your account, please visit the following link to view and pay the invoice: Pay Invoice. After clearing the invoice, you should no longer receive notifications about the debt, and you will be able to proceed with purchasing more credits.
If this solution does not apply to your situation, or if it seems outdated, we recommend checking for 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
