Undo button in andvanced translation editor

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

Problem:
The client is trying to create custom translations for each post using the WPML Advanced Translation Editor (ATE), skip translation fields, avoid adding HTML, and manage non-WPML plugin translations separately.

Solution:
1. Custom translations with different designs or content amounts cannot be created using ATE; instead, use the WordPress editor. For more details, see this guide.
2. There is no persistent 'undo' button in ATE. To undo automatic translations within the same session, use the available 'Undo translation' button. To redo translations, consider deleting them or resending them via the Translation Management Dashboard.
3. All translation fields must be completed in ATE; to add text not present in the original, or to skip HTML, use the WordPress editor.
4. To exclude WPML ATE from translating content managed by other plugins like WP Recipe Maker, use the WordPress editor.

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. We highly recommend opening a new support ticket for further assistance 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: Exception

This topic contains 2 replies, has 0 voices.

Last updated by francesca 1 day, 19 hours ago.

Assisted by: Waqas Bin Hasan.

Author	Posts
August 7, 2025 at 1:59 pm #17302848
francesca	<b>Background of the issue: </b> I am trying to create a custom translation for each post using the advanced translation editor in WPML. I want to skip some translation fields and leave them empty in the translated language. Additionally, I sometimes don't want to add HTML to the translated language. <b>Symptoms: </b> I cannot find an 'undo' button in the advanced translation editor. <b>Questions: </b> Is it possible to create a custom translation for each post using the advanced translation editor? Where can I find an 'undo' button in the advanced translation editor? 1) Can I skip some translation fields and leave them empty in the translated language? 2) Can I add a text (which is not in the original language) only in the translated language? It's useful to fully localize the content for different cultures. 3) Is it possible to avoid adding HTML to the translated language? 4) I use the wp recipe maker plugin. I want to manage the translation of the recipe with this plugin, not with WPML. So I don't want WPML ATE to include the recipe into the translation.
August 8, 2025 at 11:46 am #17305287
Waqas Bin Hasan WPML Supporter since 05/2014 Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Hi, Thank you for contacting WPML support. Usually we can take only one issue per ticket, however, I'll try my best to answer your questions, please consider following: Is it possible to create a custom translation for each post using the advanced translation editor? Generally, when you translate a post in other languages (secondary languages), each translation is created as a separate post, but is connected with the default language. However, if you meant by "custom translation" to create different design per translation (i.e. different visual design and/or different amount of content), then you can not use Advanced Translation Editor (ATE). You've to use WordPress editor to create such of each translation. See this guide for details. Where can I find an 'undo' button in the advanced translation editor? There's only one "Undo translation" button and it is offered when the translation is done automatically within the ATE. And it is available only for that active session. It actually is used to undo the automatically translated content, which consumes credits and reverts the credits. Other than that there's no undo button available. But there's a button on right-side-floating bar to copy original content over the currently focused translated item. See attached image. However, you can redo the translation by either deleting it, or, by resending from the Translation Management Dashboard. 1) Can I skip some translation fields and leave them empty in the translated language? Unfortunately not, the translations done via WPML Translation Editor, must be 100% completed, saved and published to take effect on the frontend. Until you are finished translating, you can just "Save" and go back to WordPress. In this case, it stays as in-progress state and no changes are published. 2) Can I add a text (which is not in the original language) only in the translated language? It's useful to fully localize the content for different cultures. Yes, you need to use WordPress editor for translations in this case, as mentioned above. See this guide for details. 3) Is it possible to avoid adding HTML to the translated language? When using ATE, if original content has HTML markers, then translated content must use the same markers in the same order, in order to complete the translation. Otherwise, you'll have to use WordPress editor, as mentioned above. 4) I use the wp recipe maker plugin. I want to manage the translation of the recipe with this plugin, not with WPML. So I don't want WPML ATE to include the recipe into the translation. Again, you'll have to use WordPress editor, as explained above. I hope this helps you getting around. If you need more help on any of your questions, I recommend opening a separate ticket/chat because as per forum policy we can only handle one issue per ticket. So you can get more to the point help, without mixing up several issues in one long ticket. Regards. P.S.: I'll be off over the weekend and 'll be able to attend on Monday.
August 8, 2025 at 12:55 pm #17305480
francesca	Okay, thank you. That's a real shame. ATE is only a tool for people who automatically translate text 1:1, and therefore not for translators who know that a translation must always be localised and rarely produces 1:1 texts. I will stop using it and switch to WP translator.