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.
Problem: After migrating a site from a staging to a live environment, two main issues arose: 1) The WPML site key was not working due to a domain change (adding 'www'), and 2) the language switcher arrow on the homepage displayed as '3' instead of the correct arrow, while other pages displayed correctly. Solution: For the WPML site key issue: 1. Unregister WPML from your site by navigating to Plugins → Add New → Commercial and clicking 'Unregister WPML from this site'. 2. Generate a new site key for 'https://www.dupagelegalaid.org' from your WPML.org account and paste it back in the 'Commercial' tab. 3. Optionally, clean up your WPML.org account by removing the old site key.
For the language switcher display issue: 1. Clear all site and browser caches. 2. Resave Permalinks under Settings → Permalinks by clicking 'Save Changes'. 3. If the issue persists, it might be due to CSS referencing old staging URLs. Update these references in your database, regenerate Divi's static CSS, and clear caches again.
If these solutions do not resolve your issues or seem 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 at WPML Support Forum.
Problem: The client's site stopped translating automatically. They tried clearing the cache, erasing translations, and canceling in-progress automatic jobs, but none of these actions resolved the issue. Solution: We ran an internal tool to fix the communication settings with the Automatic Translation Engine (ATE). After this adjustment, the automatic translation functionality was restored. We asked the client to verify that the issue was resolved on their end.
If you're experiencing similar issues with automatic translation not functioning, we recommend checking your communication settings with ATE or trying the steps the client initially attempted, such as clearing the cache or canceling any in-progress jobs. If these steps do not resolve the issue, it might be due to an outdated solution or a different underlying problem. We highly recommend visiting related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
