In WPML 4.6, 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.
Here are the specific scenarios we are aware of and currently handling:
After site migration or changing the site URL, the site action notice doesn’t appear.
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
- And more!
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!