We just released an update to WPML, String Translation, and Translation Management. It improves Translation Management usability and fixes a few bugs.
Improved Translation Jobs tab
We added a Batch name column to the list of jobs on the Translation Jobs tab in the Translation Management. You can filter the list by entering the batch name in the controls at the top.
This allows you to find jobs that you sent to your translation service more easily. Since you send translation jobs in batches, it’s easier to search by the batch name than by the pages in the batch.
Bug fixes
WPML 4.2.9
We fixed a fatal error that happened when the show_untranslated_blog_posts option is active.
WPML String Translation 2.10.7
We fixed an issue with 404 errors for translated pages using certain page builders (such as SiteOrigin) where the slug base was translated (e.g. for products).
Download and Update
This is the first release that is being rolled out gradually.
Only a part of the sites running WPML will receive this update on the first day. After making sure we did not receive any outstanding bug reports for the new version, we will roll out this update to all sites.
Even if your site is not in the first receiving group, you can start the update yourself. Go to the Plugins -> Add New page, click the Commercial tab and then the Check for updates button. Finally, click to update the plugins.
If needed, you can always log-in to your WPML account to download and install manually.
We recommend doing a backup before updating anything on your site.
Feedback? Questions?
If you have any questions, ideas or suggestions, please add your comments and we’ll get back to you.
Thanks for the new version. Do you have a guide that teaches how can one optimize the impact of WPML on page load speed?
Hi, Umair! In a day or two, we should release WPML 4.3 which is solely focused on improving WPML performance and optimizing its load.
The thing is, after months of optimizing we are sure that WPML 4.3 is fast as-is, without you needing to do anything to “optimize it”. Of course, there could be other factors you might need to optimize, that have nothing to do with WPML, like updating WordPress and all plugins, using a caching plugin, etc.
I suggest waiting for this to go out (literally this week) and updating, then checking your site’s performance. We will provide a new page that provides steps for preventing performance issues with WPML and will also publish a tutorial post about using Query Monitor to profile your WPML-powered site.
Kind regards,
Dario