Home›Support›English Support›[Resolved] Warning: You are about to edit your translation using the standard WordPress editor
[Resolved] Warning: You are about to edit your translation using the standard WordPress editor
This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing issues with WPML where translations of posts or products are incorrectly opening in the WordPress editor instead of the WPML Translation Editor, and you receive warnings about potential data loss, we have identified a solution. Solution: First, ensure you create a full backup of your database. Then, perform the following SQL queries via phpMyAdmin:
DELETE pm FROM wp_postmeta pm JOIN wp_posts p ON pm.post_id = p.ID WHERE p.post_type = 'product' AND pm.meta_key = '_wpml_post_translation_editor_native' AND pm.meta_value = 'yes'
DELETE pm FROM wp_postmeta pm JOIN wp_posts p ON pm.post_id = p.ID WHERE p.post_type = 'product' AND pm.meta_key = '_last_translation_edit_mode' AND pm.meta_value = 'native-editor'
UPDATE wp_icl_translate_job JOIN wp_posts ON wp_icl_translate_job.title = wp_posts.post_title SET wp_icl_translate_job.editor = 'wpml' WHERE wp_posts.post_type = 'product' AND wp_icl_translate_job.editor = 'wp'
After running these queries, verify by opening a few product translations at random to confirm that they now load in the WPML Translation Editor.
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 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.
Hi Bigul,
For some reasons, I could work on my site for a while.
Now, I have time, and I discover several issues with WPML!
I just did a translation of a post .... the html ... indeed the gutenberg codes are badly transferred.
I wanted to update a product, it directly opens in wordpress editor, and shows: "Warning: You are about to edit your translation using the standard WordPress editor but your site is configured to use the WPML Translation Editor. Any edits you do here will be lost if you later open it in the WPML Translation Editor. "
I use the WPML eidtor, I can't anymore, and I get warnings !
Nightmare !
Kind regards
Welcome to the WPML support forum. I will do my best to assist you in resolving the issue.
I have created a separate ticket for this case to make follow-ups easier and to avoid discussing multiple topics in a single thread. This will help us support you more effectively.
This warning is typically triggered when a translated post, created using the WPML Translation Editor (Classic or Advanced), is manually edited in the WordPress editor.
Please check the following screencast. I was able to translate the products as expected. I tested with a few different products, and the translations worked correctly. However, I noticed that you are using the WordPress Editor for some translations and the WPML Classic Translation Editor for others.
hidden link
To help us further investigate, please try the following steps and confirm whether you still encounter the warning while translating products:
- Go to Products > All Products.
- Make sure the Dashboard language switcher (located in the top admin bar) is set to French.
- Open a product for editing, then click on the translation link in the Language section (on the right-hand side).
– Alternatively, you can click the translation icons from the product list.
Refer to the attached images for additional guidance.
Thank you for the updates. The following German product post is a translation of this French product - hidden link
hidden link
The French Product Post is translated to English and German manually using the WordPress Editor. I was able to edit the German translation manually from the WordPress Editor as expected.
Please review the attached images for more details and let us know your feedback.
Bigul,
That is not the point, please see first message.
Why can't I use the WPML editor?
I always used it.
Why this product bugs, without my consent, no being informed.
Again, I need side by side, to see the differences and what to translate / update
Waiting for your feedback,
Kind regards
Alina
Thank you for the feedback. For your kind information, WPML does not automatically switch the translation mode of a post that was translated using the WPML Translation Editor (either Classic or Advanced) to manual translation via the WordPress Editor. I have confirmed this with our developers. Please refer to the following documentation for more details.
It appears that the translation mode for the following Product post was manually changed to "WordPress Editor" in the past. This change was applied individually to a few products, which is why some are translated manually while others still use the WPML Classic Translation Editor. This is despite the Classic Translation Editor being set as the default option globally in WPML >> Settings >> Translation Editor.
hidden link
To resolve this, please switch back to the WPML Translation Editor. After taking a full site backup, open the post for editing in the original language (French) and then re-translate it into German and English using the WPML Classic Translation Editor.
Bigul,
Believe me or not, for personal reasons, I did not touch WP for the last 6 months.
Anyway, whatever the date, I mean including 2002 or 2023, or 2024, I have products which become un-translate-able via editor.
And you say it's my decision? Or it was in 2023? 2024?
My routine has always been the same. Duplicate, update text and photo, then translate via editor, including media.
For products, and even for posts, I have no reason to change layout in other languages.
My only exception is "home" page.
Be fair, I can't have decided in 2024 or 2023 that my products should never again be translate-able via editor., basically since I always used it.
Please, be fair and factual
Kind regards
Alina
Thank you for the feedback. This may have occurred due to a conflict after duplicating the post using the Yoast Duplicate Post plugin. I noticed this about an hour ago while troubleshooting the issues you are experiencing, and we are currently investigating it further.
Please refer to the following screencast for more details, and let us know your feedback.
Bigul,
This is incorrect, I just double-checked.
Translate a post / article requires yoast duplicate post plugin.
Duplicate product (ie not a post / article) is a native function of Woocommerce. Meaning that it does not require any plugin.
Kind regards
Alina
Thank you for the updates. What I meant earlier is that I found the reason why posts translated using the WPML Classic Translation Editor are now showing their translation mode as WordPress Editor.
For example:
- I create a post Neu 01 in French (the default language) and translate it into English and German.
- I then duplicate the French post (Neu 01) using the Yoast Duplicate Post plugin.
- Since Neu 01 already has translations in English and German, the plugin creates duplicates of the post and its translations in French, English, and German.
When we edit and publish the duplicated post (Neu 01 – Draft) as Neu 2, the translation mode for Neu 2 changes from WPML Classic Translation Editor to WordPress Editor.
I was able to reproduce this issue in a clean install on our sandbox server. Please check the following URLs for more details.
Screencast >> hidden link
Sandbox site login URL >> hidden link
I will discuss this with our compatibility team and get back to you as soon as possible. Please wait.
Hi Bigul,
Thank you for that, I appreciate, but again, this is not the point.
1. I am not talking about posts but about PRODUCTS
2. I am not talking about "yoast duplicate post" but about wordpress native "DUPLICATE" in Woomercomme product listings page.
I have products that were recorded in 2024, or 2023, of earlier that I am NOW unable to edit via translator, though you wrote WPML is not changing the way of translation.
Why do you refuse here to consider what I write and repeat?
Kind regards
Alina
Thank you for the feedback. I was trying to troubleshoot the issue in depth and find the reason for the bug. I noticed that a few posts display the WordPress editor as the translation mode instead of WPML Classic Editor, similar to the Product Posts.
I conducted a very detailed test in both my local copy and a fresh WooCommerce installation to reproduce the issue. But I can only replicate it with Posts.
hidden link
I have shared the details with our second-tier team and am awaiting their feedback. We will get back to you soon. Please wait.
Hello Bigul,
OK, will wait.
Again, to resume: I have always been using the WPML editor ... and never met this situation before, where I am forced to use another editor. I can only link this situation to the new WPML. I mean that there is a logical cause/effect relationship with the abandon of old WooCommerce Multilingual. What, giving me the 2023 version of WPML should help me to prove ....
That being said, I noticed a weird "thing": when I am willing to translate a product, I am led to WPBakery editor, which I am not using (only 1 exception: homepage). I only use native wordpress editor and gutenberg. Here could be another cause/effect relationship ... for whatever reason, WPML considers that I use WPBakery, what is totally incorrect.
Also, you will find attached a product, made via Gutenberg editor, where the HTML is not managed by WPML, and where WPML also considers that it's a WP Bakery.
Question: If I miss to add a tag, like or translate <H3> in <H2>, could WPML consider that it was "translated" via page builder, though made with WPML editor?
Kind regards
Alina
I meant:
Question: If I miss to add a tag, like < strong > or translate <H3> in <H2>, could WPML consider that it was "translated" via page builder, though made with WPML editor?
Kind regards
Alina
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi Alina,
my name is Marcel, and I’ll be taking over your ticket. We have a solution you can test after creating a full database backup (very important before running the queries via phpMyAdmin):
1) Remove post meta where the key _wpml_post_translation_editor_native is set to yes:
DELETE pm
FROM wp_postmeta pm
JOIN wp_posts p
ON pm.post_id = p.ID
WHERE p.post_type = 'product'
AND pm.meta_key = '_wpml_post_translation_editor_native'
AND pm.meta_value = 'yes'
2) Remove post meta where the key _last_translation_edit_mode is set to native-editor:
DELETE pm
FROM wp_postmeta pm
JOIN wp_posts p
ON pm.post_id = p.ID
WHERE p.post_type = 'product'
AND pm.meta_key = '_last_translation_edit_mode'
AND pm.meta_value = 'native-editor'
3) Update the recorded editor in the translation jobs table:
UPDATE wp_icl_translate_job
JOIN wp_posts
ON wp_icl_translate_job.title = wp_posts.post_title
SET wp_icl_translate_job.editor = 'wpml'
WHERE wp_posts.post_type = 'product'
AND wp_icl_translate_job.editor = 'wp';
4) Verification step:
Open a few product translations at random and confirm that they now load in the Classic Translation Editor instead of the WordPress editor.
If you’d like, I can also help you to run these queries.
