Translations lost

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is using both the Advanced Translation Editor (ATE) and the default WordPress Editor (Gutenberg and Kadence Pro) for translations on their website. They are concerned about losing translations when switching between these editors.
Solution:
We recommend choosing one editor for consistency to avoid conflicts or data loss. If the client prefers the default WordPress Editor for certain pages and wishes to stop using the WPML Translation Editor for those pages, they can disable the Translation Editor on a per-page basis by following these steps:
1. Open the default language page in Edit mode.
2. In the Languages metabox, disable the WPML Translation Editor for that specific page.
3. Now, when editing the translated page, it will open in the default WordPress Editor, and any manually updated changes will remain.
For more details, please refer to our documentation on using different translation editors for different pages.

If this solution does not fully address your issue 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. If further assistance is needed, please open a new support ticket at WPML support forum.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: ATE, Exception

This topic contains 5 replies, has 2 voices.

Last updated by Noman 2 months, 1 week ago.

Assisted by: Noman.

Author	Posts
October 5, 2024 at 3:44 pm #16256812
amauryC-5	Background of the issue: I'm a consultant working on the new version of ski-mojo.com/generated-homepage. We have rebuilt and translated the site using automatic translations. My customer prefers to manage translations via the WordPress visual editor (Gutenberg and Kadence Pro). He has done many translations via the 'edit page' button. Symptoms: We opened the WPML translation editor and fear that we have lost the translations. We had to roll back using the WordPress revision function. Questions: What is the good practice if we prefer to use the visual editor? Shall we avoid using the translation editor to avoid any conflict?
October 6, 2024 at 8:59 am #16257642
Noman Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Hi, Thank you for contacting WPML Support. When you translate a page using the Advanced Translation Editor (ATE), the content is saved both in your site’s database and in ATE’s translation memory. However, if you edit the translation using the default WordPress Editor, the changes are saved only in the site’s database, and ATE’s translation memory is not updated. - When you view the page on the frontend, it pulls content from the site’s database. However, if you open the page in ATE, it will load content from ATE’s translation memory. This means any manual changes made using the default WordPress Editor won’t be reflected in ATE, potentially causing those changes to be lost. - We recommend sticking to one type of translation editor for consistency. If you are using WPML’s Translation Editor, continue editing the translations within that editor to avoid any conflicts or data loss. - If you prefer to use the default WordPress Editor for certain pages and no longer wish to use WPML Translation Editor for those, you can disable the Translation Editor on a per-page basis by following these steps: 1. Open the default language page in Edit mode. 2. In the Languages metabox, disable the WPML Translation Editor for that specific page as you can see in the attached screenshot. 3. Now, when you edit the translated page, it will open in the default WordPress Editor and your manually updated changes will remain as it is. Here is a doc for more details: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/ Please let me know if this resolves the issue or if you need further assistance with this issue Thank you
October 7, 2024 at 8:28 am #16259618
amauryC-5	THank yuo so much, that really helps and clarifies the situation. One last question to make there wont be any side effect : I'd like to use the wordpress editor for all the pages of the website then If I click on the "use wordpress editor" button, I have a pop up asking if I want to use only for this page or for all pages of the website. If I clic on "use on all pages of the website", can you confirm this will not consider the ATE translations anymore ? SInce we have discrepancies between the ATE translation and the translations within the wordpress editor, I want to make sure that we'll not loose the translations made within the wordpress editor (the latest translations are into the wrodpress editor and not into the ATE) Thank you for your confirmation
October 7, 2024 at 10:24 am #16260387
Noman Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Thanks for your question. If you click to use “WordPress editor" for all pages, WPML will stop using the ATE for all pages, and future translations will only be handled through the WordPress editor. Your current translations in the WordPress editor will be safe, and they won’t be overwritten by the ATE. Just keep in mind that if you later switch back to ATE, it won’t have the latest updates made in the WordPress editor. Let me know if you have any more questions! Thank you
October 8, 2024 at 9:24 am #16264661
amauryC-5	THank you for your confirmation that helps Can you please also confirm that 1. What if I go to WPML > translation management > tick the page or post I need to update or translate and select Translate > translate automatically > start translation => will this upde ATE or the wordpress editor table ? In other word, what is the process I should follow to creat automatically translations when I create a new post / page / product ? 2. when I go to WPML > translation i see a lot of translation waiting in queue. SHould I keep on using it if I choose to translate via the wordpress editor and never via ATE anymore ? See screenshot when I click on "take and translet" I got an error message" THxs for ur help A
October 8, 2024 at 1:35 pm #16265664
Noman Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	1. If you choose the Translate Automatically option from WPML >> Translation Management page it will translate the page using ATE and not using default WP Editor and your manually edit changes using default WP Editor may lost using this process. So, if you want to use ATE for new posts/pages, please follow the below steps: - Make sure to enable the WPML Translation Editor for that page from Languages metabox. - You can translate the page by clicking the translation icon from inside page edit screen or page/post list page or using Translate Automatically option from WPML >> Translation Management page 2. If you want to use default WP Editor for those pages, you may leave them as it is. Thank you
October 8, 2024 at 3:56 pm #16266656
amauryC-5	ok now i'm good thank you for ur help