Website built with the classic WordPress editor – what should we do with the new translations?

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

Problem:
The client's website was initially translated using the classic WordPress editor. After deciding to switch to the advanced translation editor for adding more languages, they encountered an issue where products, posts, and pages originally created with the WordPress still open in that format. The client is concerned about losing existing translations and the credits used for them if they switch to the new editor for older post IDs.
Solution:
We explained that switching the translation method for content that was previously translated using the WordPress Editor to the WPML Translation Editor could result in the loss of the old translations, as they would be overwritten. This is because the translations are stored in the translation memory of the WPML Translation Editor and are applied when the content is sent for translation. If the client decides to proceed with switching to the Advanced Translation Editor and uses credits for automatic translation, it is not advisable to switch the translation method back to use the "WordPress Editor". If you run into issues where translations open on the WordPress Editor while you expect the Advanced Translation Editor to open, please revise the right sidebar of the original content inside the WordPress Editor and make sure that the translation method is set to "WPML Translation Editor". Also note, that automatic translations are technically not possible when using the WordPress Editor as translation method.

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 issue persists, please open a new support ticket.

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, Documentation request

This topic contains 29 replies, has 1 voice.

Last updated by Giulio 2 months, 1 week ago.

Assisted by: Andreas W..

Author	Posts
April 15, 2025 at 7:35 am #16932030
Giulio	I had already pointed out that, even while using the WordPress Editor, we were able to see translations of descriptions, taxonomies, attributes, and so on when translating products with WPML AI. But now you’re telling me that we shouldn’t be seeing those translations—and that to make them visible, we’d have to switch to the WPML Translation Editor. In any case, we’re giving up on this discussion—it’s not helping, and it’s actually making us more frustrated because we can’t seem to move forward. In our view, the transition from the old method to the new one hasn’t been handled particularly well, especially in terms of communication with your paying customers—and we can only express our disappointment about that. We’ll continue to muddle through with WPML as best we can. Regards.

Author

Posts

April 15, 2025 at 7:35 am #16932030

Giulio

I had already pointed out that, even while using the WordPress Editor, we were able to see translations of descriptions, taxonomies, attributes, and so on when translating products with WPML AI. But now you’re telling me that we shouldn’t be seeing those translations—and that to make them visible, we’d have to switch to the WPML Translation Editor.

In any case, we’re giving up on this discussion—it’s not helping, and it’s actually making us more frustrated because we can’t seem to move forward.

In our view, the transition from the old method to the new one hasn’t been handled particularly well, especially in terms of communication with your paying customers—and we can only express our disappointment about that.

We’ll continue to muddle through with WPML as best we can.

Regards.