Have you experienced the issue after upgrading the WPML plugin to the latest version (v4.6.1)? Did you also check in a minimal environment, such as disabling all plugins except WPML and its add-ons? Doing so will help you determine if the issue is caused by a conflict with other plugins.
If none of the methods worked, please share the access details to your site with me. I’m enabling a private message for the following reply.
**IMPORTANT**
- Please backup the site files and database before providing us access.
- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.
After further investigation, I have transferred your issue to our second-tier support team. They will investigate the issue and attempt to resolve it as soon as possible. Once I have received an update from them, I will be sure to let you know.
In the meantime, please refrain from changing the login credentials or deleting anything from your staging site.
I appreciate your cooperation and understanding. If you need any assistance, please do not hesitate to reach out to me.
After further investigation, our 2nd tier support team discovered that the page was initially edited in the Advanced Translation Editor (ATE).
If you run the SQL query below, you'll see that the result for "editor" is "ate", indicating that the page was first edited using the ATE editor:
SELECT `editor` FROM `y57hb_icl_translate_job` WHERE `title` = 'Alkoholfreie Getränke' AND `rid` = '2366' ORDER BY `revision` DESC LIMIT 1
Also, the job has already been generated with the editor value set to "ate", so it won't be re-generated unless there's an update - meaning the value will remain as ATE. If you delete the original page, create a new one with the same content, and then translate it using the Classic Translation Editor (CTE), you'll be able to use CTE afterward.
I hope this helps. If you have any questions or need further assistance, please don't hesitate to ask.
Good morning. I'm glad to hear that you've fixed the issue. Another workaround would be to get the "rid" of the element, which can be obtained by the job id, and set the editor column to "wpml" in the translate_job table.
First, you can inspect the gear as shown in this screenshot (hidden link) to get the job_id.
Then you can run a query:
SELECT * FROM `y57hb_icl_translate_job` WHERE `job_id` = '4221'
This returns an example for the column "rid" with the value of 2366. Next, you can run an update by supplying the "rid":
UPDATE `y57hb_icl_translate_job` SET `editor` = 'wpml' WHERE `rid` = '2366'
This sets the editor to the classic editor for the language in question. Please make sure to create a backup of your website before making these changes.
I hope this helps. If you have any questions or need further assistance, please don't hesitate to ask.
I translated a website with the Classic Translation Editor.
Later I switched to the Advanced Translation Editor and selected: "Editor for translations previously created using Classic Translation Editor = Classic Translation Editor (recommended)".
THIS OPTION DOES NOT WORK
When I want to translate a page translated with the Classic Editor, the Advanced Editor opens and translations are missing.
Are you still encountering the editor issue after restoring the backup? It seems that the post/page had been previously translated using ATE, which is why the ATE editor is set in the database.
In cases where old posts or pages won't translate using ATE, WPML won't change the editor within the database. If you or your client are unable to run an SQL query, you can ask your hosting provider for assistance. This is a special case and shouldn't be a frequent occurrence.
If you can't access PHPmyAdmin or the database, you can use the Database My Admin plugin (https://wordpress.org/plugins/my-database-admin/) to run SQL queries directly from the WordPress dashboard.
If you run into any difficulties, please don't hesitate to let me know. I'm more than happy to help you.
Are you still experiencing the same issue on other pages of your website? If so, please let me know the name of the affected pages so I can review them and create a copy of your website to escalate the issue to our 2nd tier support team.
Our team can investigate why the editor has been modified from the database, but if the issue doesn't occur on other pages, I suggest that you let us know if it happens again in the future.
Please feel free to contact me if you have any further questions.
SELECT `editor` FROM `y57hb_icl_translate_job` WHERE `title` = 'Kategorien' ORDER BY `revision` DESC LIMIT 1
returns wpml
When I click on the icon for "Update translation" the "Advanced Translation Editor" opens and a lot of translations are missing.
When I change the setting "Editor for new translations" to "Classic Translation Editor", all pages open with the classic editor and no translations are lost.
I have consulted with our 2nd tier support team regarding the issue. After careful consideration, we do not believe that the Editor can be set to "acf" as we do not recall this as a possibility. If "wp" is returned, the native Editor (WordPress editor) must be opened.
However, if the page was sent for translation and ATE was used with the setting in Editor for new translations, then ATE will be opened if the translation was just created for the first time.
I hope you have already resolved the translation editor issue by following our guidelines. If you encounter the same issue in the future, please do not hesitate to inform us immediately so we can further investigate.
"(...) then ATE will be opened if the translation was just created for the first time."
The translations were fully created with the Classic Translation Editor, but now they open with the Advanced Translation Editor and translations are missing.
How can I make all translations that were created with the Classic Translation Editor open with the Classic Translation Editor?
The SQL-query you posted returns "wpml" for the pages I mentioned.
Is it correct behaviour of wpml that they open with the Advanced Translation Editor?
Regarding the issue you encountered with the editor, I created the "Das setzt mich natürlich unter Druck" post in German and translated it using CTE. I tried a couple of times and did not encounter the same issue. Therefore, whenever I opened it, it was with CTE, not ATE.
Could you please try using CTE for a new post and let me know if the editor changes to ATE? This way, we can identify the root of the issue and find a solution.
Unfortunately, we could not determine which editor you used from the previous records because the database records indicated the opposite. So, if you encounter the same issue with new posts, it will help us to investigate further.
I recorded my screen when I created and translated the post to assist you better. You can check it out here: hidden link.
