Problem: The client accidentally set their site to automatic translation, which depleted their translation credits significantly. After attempting to reset by disconnecting, removing, and reinstalling the plugin, the client found they only had a small fraction of their original credits left. Solution: Unfortunately, once translation credits are used, they cannot be restored as they are immediately compensated to the translation engine. More details can be found here: https://wpml.org/faq/can-i-get-a-refund-for-automatic-translation-credits/
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with translating content into English using WPML, where updating content in the primary language (Czech) and then switching to ATE results in the content for translation not loading and displaying the message: 'Unable to retrieve job details,' it might be due to the translation job containing no translatable data. This issue could be evident across multiple sites using the WPML plugin. Solution: We recommend checking the .xliff file generated by WPML. If the
<body>
element within the .xliff file is empty and the 'wpml-words-to-translate-count' is '0', it indicates that WPML is unable to extract any translatable content. This could be due to server-side issues rather than a problem with WPML configuration, plugins, or themes. Possible server-side causes include multiple applications of output compression (e.g., zlib.output_compression in PHP combined with server-level gzip/Brotli), modifications by security or performance layers (e.g., WAF, CDN, reverse proxy, or caching layer), or incorrect headers or content encoding (e.g., globally applied 'Content-Encoding: gzip'). To resolve this, contact your hosting provider, explain the issue, and ask them to investigate how responses are encoded and compressed on the server. This step is crucial especially if the issue affects multiple sites, suggesting a shared server configuration problem.
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 the problem persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that automatic translation does not translate all fields in Elementor widgets; some text fields remain untranslated despite being marked for translation in WPML settings. Solution: We recommended adjusting the translation preferences for custom fields and using the Multilingual Tools plugin to ensure WPML recognizes all text fields for translation. Here are the steps: 1. Install the Multilingual Tools Plugin from https://github.com/OnTheGoSystems/multilingual-tools. 2. Create a test page with the problematic widgets and fill in all text fields. 3. Generate XML configuration by updating the page and copying the XML code from the 'WPML: Elementor Widgets' section. 4. Add the custom XML configuration to WPML under 'WPML → Settings' in the Custom XML Configuration tab. 5. Resave the original page to force WPML to re-scan with the new configuration. 6. Re-translate the page using WPML's Translation Dashboard or Advanced Translation Editor.
If these steps do not resolve the issue or if the solution 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that the Arabic version of their website was not displaying correctly after updating WPML plugins. Solution: 1. We advised the client to check and verify their WPML site registration key under Plugins → Add New Plugin → Commercial tab. 2. We suggested increasing the WordPress memory limit by adding the following code to the wp-config.php file:
3. We recommended deactivating the Slider Revolution plugin and any other related plugins to see if the issue resolves. 4. We created a staging site to further investigate the issue, where it was discovered that the problem was not with WPML but potentially with the Ave theme or incorrect HTML format.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to purchase additional credits for automatic translation but are encountering an error message stating that the VAT number is in the incorrect format. Additionally, the VAT field is not visible, preventing the purchase. Solution: We have determined that the VAT field only appears for countries where we are required to collect EU VAT, which applies solely to EU member states. Since the UK is no longer part of the EU VAT system post-Brexit, the VAT field is not displayed for UK customers. As an international company, we do not collect or process UK domestic VAT. Therefore, you should be able to complete your purchase without entering a VAT number.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: On four websites, the WPML plugin fails to translate the 'Gastronomie' page, showing an error that WPML has attempted to translate the page three times unsuccessfully. The issue persists across all sites with this specific page. Solution: 1. Cancel the in-progress translation job for the 'Gastronomie' page by navigating to WPML -> Translation Management -> Translation Jobs. 2. Make a minor edit to the original 'Gastronomie' page. 3. Change the translation setting for the
_elementor_data
custom field from 'Translate' to 'Copy' by going to WPML → Settings → Custom Fields Translations, clicking on Show Custom Fields, and adjusting the setting. 4. Disable the Multilingual Tools plugin. 5. Update the page and attempt to edit the translations again.
If these steps do not resolve the issue or if the solution 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 the problem persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was unable to translate the footer text 'book an innovation tour' from English to German using WPML. Despite trying automatic translation and pay-as-you-go options, the translation did not appear correctly, and accessing the footer translation showed a different text. Solution: We identified that the footer was created as an Elementor template. Here are the steps we took to resolve the issue: 1. Accessed the Elementor footer template in the default language. 2. Made a minor edit to the template and updated it. 3. Removed the edit and updated the template again. 4. Added the translation via the WPML Advanced Translation Editor (ATE). 5. Checked the front end to ensure the translation appeared correctly.
If you're experiencing a similar issue, we recommend following these steps. However, if this solution does not resolve your problem, 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 issue persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: After upgrading to WPML Advanced Translation Editor and using Elementor Pro, the client found that links were not being translated as expected, despite settings indicating they should be. Solution: We recommend the following steps to ensure links are translated correctly: 1. Review and Translate Links in Advanced Translation Editor: * Go to the page or post containing the links you wish to translate in your original language. * Edit it and send it for translation to the Advanced Translation Editor. * Once in the ATE, internal links are usually automatically pointed to the language-appropriate version. You can still edit them if needed, as they will appear highlighted. * For external links, use the search bar within the ATE to find and manually adjust them.
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 at WPML support forum.
Problem: The client was experiencing issues with ACF field strings in Bricks being auto-translated by WPML, which was breaking the content. Specifically, headings and class names were being incorrectly translated, causing display issues on multilingual pages. Solution:
We recommended the client to check the solutions from here: https://wpml.org/forums/topic/wpml-auto-translating-acf-variables-inside-bricks-builder/#post-17328592
We also recommended the client to check the error log to identify any specific issues with ACF fields containing both text and functions. By separating these elements and addressing other ACF/Bricks/WPML related issues, the client managed to resolve the problems. Additionally, if the issue persists, we suggest checking the translation settings and ensuring that the XLIFF files are correctly applied. For unresolved issues, we recommend sharing a backup of the wp-content folder and database for further analysis.
Please note that this solution might be outdated or not applicable 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 the problem persists, please open a new support ticket.
