In WPML 4.5.9, we’re addressing a few issues between WPML and its Advanced Translation Editor. We need your feedback, to make sure that we’re covering everything that you need.
WPML 4.5.9 is now available
We released WPML 4.5.9, which includes fixes to the issues mentioned in this post, as well as improvements to the Translation Jobs and Translations Queue pages. Read more about it in our announcement post.
Here are the specific scenarios we are aware of and currently handling:
This causes a communication error between the Advanced Translation Editor and WPML. The Advanced Translation Editor doesn’t open or translations don’t save. You may see an error message: “WPML tried to translate this page three times and failed” or “WPML didn’t manage to translate this page.”
Before saving and completing a translation in the Advanced Translation Editor, someone makes a change to the page or post in the default language.
In-progress translations are not saved. You need to re-translate the page or post.
A page or post has already been translated, and you later join sentences and re-translate in the Advanced Translation Editor.
After updating the default content, the joined sentences are missing their translations or the segmentation is broken.
When you translate a page or post manually using the native WordPress Editor, then later try to translate using the Advanced Translation Editor.
Instead of the Advanced Translation Editor opening, it is only a blank screen with a URL ending with ?ateJobCreationError=102&jobId=1.
Upcoming Release: WPML 4.6
Our developers are working on WPML 4.6 now and expect to release it in September. It will include all major fixes mentioned here, plus some great features including:
An all-new language switcher block
Improvements to the workflow for using automatic translation on multiple pages or posts in bulk
Improvements to the Translation Jobs and Translations Queue interfaces
Is There Anything Else We Should Include?
We want to be sure WPML 4.6 includes fixes to all recent issues with the Advanced Translation Editor. If there’s a problem you’ve experienced that isn’t on the list above, please open a support ticket (if you haven’t already) and share the link with us in the comments below.
I will be reading all the comments and sharing them with our development team!
77 Responses to “Upcoming Improvements to WPML’s Advanced Translation Editor”
How about an option making it possible to complete the translation without having to edit (or press the check mark) for each and every sentence ?
How about an option to accept proposed formatting marks – without having to redo them in the translation ?
Hi Ben – Thank you for your comment. Right now we’re focused on fixing bugs and issues, but I have shared your feature requests with our development team for future consideration.
Well, I really appreciate this initiative …
Bugs are much more widespread than seen above. I had to make some changes to a multilingual site (ITA DEU ENG) in which WPML was installed. When I went to change the default language, wpml indicated that even the secondary languages needed intervention. I accessed the advanced editor and unfortunately the translations already present were lost. I had to restore all the translated texts with copy / paste from the front-end.
Hi Stefano – Thanks for your comment. Have you opened a support ticket about this? If so, could you please share the link to the ticket so we can look into it further?
my post was only related (and a replied) to your email of 21/7/2022 in which you asked for feedback to make sure that no problem remains unsolved in the new 4.6 version.
Hi Stev – Yes, thank you for letting us know. The reason I ask for a ticket is because our support team can properly investigate and diagnose the issue. I wanted to be able to help escalate it to our developers so we can be sure to include it in the 4.6 release if possible.
Hi, I’ve just seen your message regarding the upcoming release WPML 4.6. I was wondering what I can expect from the “all-new language switcher block”. I’m asking because I’m looking for a specific solution, and maybe this is going to be the one. Maybe you can say a few more words to that. Thanks.
Hi Rene – Currently, you can add a language switcher using PHP, shortcodes, or the WPML language settings. WPML 4.6 will make it possible to add a language switcher as a block when using the Gutenberg Block Editor and Full Site Editing.
Compatibility with lazyblocks would be great. 🙂
Thank you for your comment, Felix. You can refer them to our Go Global Compatibility Program to get started!