WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
Hi, thanks for creating the ticket. It´s been simplified too much and some issues have been left behind.
The markers issue seems to be resolved, though the new editor erases the texts breaklines when "I prefer bigger segments" is selected.
It happens in normal text and in the Toggle element text aswell.
I´m glad to have the option of having paragraphs -not- split into infinite sentences.
But it´s not useful if 5 paragraphs become just one...
Find attached the screenshot where this can be seen.
FRE translation> hidden link
Thank you for waiting. This is a known issue with the new ATE. I've switched to the previous version, by clicking on the gear icon, inside the editor, and chnaging the editor to the previous version.
After that, I made a small change to update the original content and updated the FR translation. Now the line breaks show as expected. Please let me know if that fixes your issue.
Thanks Lucas
What I see is:
+ The text fields with paragraphs are still being read as one large paragraph
+ The toggle text content is indeed split into different lines, but my previous translations have been reset!
Am I supposed to be working like this? Switching back and forth between the editor versions and losing time and credits every time?
When having issues with line breaks, you can change to the previous version and keep it that way. Both versions of the translation editor have the same features.
If you check the translation and maintain the previous ATE version, you should have no issues. Please let me know, if using the previous version, the line breaks issue is resolved and you can translate your website.
I apologize for the inconvenience, but meanwhile using the older ATE is the only solution we have. As I said, there's no need to go back and forth switching the versions, stick with the older one and you should have no issues.
As for the credits, can you please check how many were spent translating that page? I can reimburse them for you.
Hi Lucas
Thanks fro the clarification. I opened the translation and, even though you switched to the old ATE, the new one was the one to be displayed (and the translations reset). Would the translations be recovered if I switch to the old ATE, after it automatically opened ion the new one?
Credits, thanks! I´ll let you know when I´m done <3
I'm not sure what is the answer to that question, you'd have to test that, if possible. Let me explain: the expected behavior is, when switching to the older ATE version, it will change for all posts. That means that, posts translated from now on will use the older ATE, as well as previously created posts. That needs to be done only once and is permanent.
I just tested that in a test-website. Please keep using the older ATE and don't switch to the new one, until we find a fix for it. If the behavior in your website is different than the one I just described, please let me know.
Also, please don't switch "I prefer bigger segments" on and off. I'm afraid this is what's causing the content to be lost.
Bottom-line is: switch to the older version and keep it that way 🙂
Hi Lucas
Sorry for the delay in replying.
Can you please tell me where I can find the option to deactivate the new ATE for all the posts? I was only selecting that option on the top right menu of the translation editor screen of the problematic post..
I manage many websites using WPML and I definetly don´t want to have them messed up because of this issue. Some of them still have translatinos in the Classic editor, so this "permanent" swith to the old ATE may cause unexpected results.
Let me explain how it works: when switching to the old ATE, all the posts that use the ATE will be switched together. That means that when changing to the old one inside the problematic posts, the other posts that use ATE will also get changed automatically. You only need to do that once. Switch to the old ATE, wait for the page to refresh and you're done.
That does not apply to posts that use CTE (Classic Translation Editor). Posts that use CTE will stay as they're, regardless of the settings of ATE.
Please let me know if that answers your question. Also let me know if you notice a different behavior on your website.
1) Can you clarify the safe steps to switch to the old ATE that will automatically apply to the whole website? As i mentioned, when I changed it on one page using the top right menu, but when reopening it, it switched back to the new one.
2) Once we switch to the old ATE, will the translation be reset? It already happened to me and it would be a problem if other translation got broken due to this.
3) I understand this is a known bug (quite problematic). When are you going to fix this?
1) I recorded a video showing how it works. As I said, you can simply change to the old ATE inside one post, that the change will reflect to all other translations that use ATE: hidden link
2) No, the translation stays as it is.
3) This issue is already fixed, in theory. Applying the solution I gave should work.
If the behavior you're seeing on your website is not the same as I shared, please record a video reproducing the issue. You can use Loom.
