Home›Support›English Support›[Resolved] Feedback moving from CTE to ATE : about your advice not to convert Classic Translated Content to ATE
[Resolved] Feedback moving from CTE to ATE : about your advice not to convert Classic Translated Content to ATE
This thread is resolved. Here is a description of the problem and solution.
Problem: The client has migrated their content from the Classic Translation Editor to the Advanced Translation Editor (ATE) in a test environment and is considering cleaning up the database after the migration, despite the content being mostly individually edited. Solution: We recommend continuing to use one editor, the Advanced Translation Editor, for all site content to maintain consistency and ease of use for translators. After switching from the Classic Translation Editor to the Advanced Translation Editor, existing translations will still be visible on the frontend. However, these translations might be completely or partially missing when opening the post in the Advanced Translation Editor. For more details, you can visit Switching from Classic to Advanced Translation Editor. Additionally, there is no need for a database cleanup after moving to the new editor, even if the content was initially translated using the Classic 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 if needed.
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.
Background of the issue:
For a couple of weeks, I did convert my whole content to ATE v2 on a test environment.
I ran quite extensive tests, which went very well.
Almost all my content is edited individually, and I didn't encounter any issues while working on that new setup.
This "setting migration" seems robust in all the cases I thought of.
I tested the translation of individually edited content to a new language, and it worked great. I could translate it, and get it published without issues.
I tested to change the original content afterwards. It didn't break any of its translations, and I have been rightfully informed, from the translation manager, that these pages needed an update.
I checked few of the contents which were translated through the CTE, and if the ATE v2 shows no translation data regarding this content, the translations are accessible as individually edited content, and displayed correctly. Therefore, if I need to edit this content later, I can edit the translations individually.
I also checked that I could edit this from the original content, without breaking its translations.
Then, I checked that could successfully apply new translations for such content through the ATE, again, without breaking the rest of it. I could also submit it for a new translation to an editor, and publish it, still without breaking the existing content.
Finally, I could remove an existing individually translated page then create it again through the ATE.
Symptoms:
None
Questions:
So I wonder why you recommend not to move the existing CTE translated content to ATE?
Are there scenarios I didn't think of?
Are there other issues to expect?
Things you already identified as a no go?
The only reason I can think of not doing it, is if I would like to adjust existing classic translated content, without the need to type it all again. Which is not the case for me, since I have very few of such content, and would rather move it all to the new editor.
Welcome to WPML support. I'd be happy to help you with this.
After you switch content previously translated using the Classic Translation Editor to the Advanced Translation Editor, existing translations will still show on the frontend. But, these translations may be completely or partially missing when you open the post in the Advanced Translation Editor.
Hi,
Thanks for your answser.
So I understand this main information you spotted in your message.
Now, in our case, we have very few content that's not individually translated.
So we'd rather move everyting to this new editor, which is now the standard one.
Rather that asking our translators to learn 2 different editors with their own specificities.
Does that make sense to you?
One last question: should I consider clean the setup with the troubleshooting options after moving to this new editor? Even if my content is mostly edited individually, it used to be translated through the classic editor first, so that some data could get cleaned up from the database.
Rather that asking our translators to learn 2 different editors with their own specificities.
Does that make sense to you?
Yes, using one editor for all site content is a good move.
One last question: should I consider clean the setup with the troubleshooting options after moving to this new editor? Even if my content is mostly edited individually, it used to be translated through the classic editor first, so that some data could get cleaned up from the database.
There is no need for cleanup when moving the editor.
