ATE

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:
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.