WPML 3.5 released, with major improvements to String Translation

After months of development, we’ve just released WPML 3.5. This version focuses on String Translation, improving performance and adding few features. WPML 3.5 also handles a few compatibility issues with WordPress 4.6.

Compatible with WordPress 4.6

WordPress 4.6 is almost ready (due tomorrow morning). This update of WPML includes a number of changes to support WordPress 4.6. Before you upgrade WordPress, be sure to upgrade WPML and all its add-ons. Like we recommend in every WordPress release, you should update with caution. We always test first on a staging site, review the site and see that nothing is broken, check the PHP error log and see that it’s clean and then update. Before updating the production site (even after we’ve tested on a staging site), we prepare a complete backup.

Usually, we never need to use that backup. However, in the very rare cases when it’s needed, having this backup will prove to be a good idea.

String Translation improvements

We introduced the changes to String Translation in the WPML 3.5 beta announcement blog post. Since the betas, we’ve made more performance improvements to String Translation in the admin and front-end. The overall performance improvement numbers depend on your content, the theme, other plugins and PHP version.

The graph on the right looks very promising, but please keep in mind WHAT we’re showing there. These are the numbers for String Translation only. Of course, a real site has more running than WPML String Translation. On our production site, the overall improvement is about 5% in CPU and 10% in memory. From that, you can see the part that String Translation was responsible for. We’re also running PHP 7.

Generally speaking, sites that have a large number of strings, not so many other plugins and run PHP 5.x will see the greatest performance improvement. PHP 7 is already a lot faster than PHP 5, especially for the functions that String Translation uses. There’s a significant performance improvement with PHP 7, but it’s smaller than on PHP 5 (which is a good thing). Sites that have many many plugins are likely to be less optimized for performance, so the overall gain from the new String Translation is less significant.

Since the performance gain in WPML 3.5 is both in CPU and in memory allocation, it’s best to measure the actual server load, rather than only use a profiling plugin. Profiling plugins are great, but they don’t give you the full picture of how your site handles real load.

I recommend to check:

• The overall server load, both CPU and memory
• The response time for front-end pages
• The response time for admin pages

We will be monitoring the server loads of our sites and will post updates about the changes that we’re seeing. We need a week to collect these updated stats, so that we can show a meaningful comparison.

A bit more coming in WPML 3.5.1

The last pocket of inefficiency is in the interaction between GetText and WPML. Today, translation happens twice. WordPress loads .mo files, which sometimes are huge. Then, WPML basically overrides all translations in String Translation.

You can see how this is wasting resources.

In WPML 3.5.1, we are planning to prevent WordPress from loading .mo files for contexts that String Translation is handling. You will not lose anything and only gain in page load time. This gain can be very significant, because WPML now only loads the strings that are needed for each page (while WordPress would load the entire .mo file).

WordPress 4.6 changed the loading of .mo files. Now that it’s out, we can complete this feature in WPML.

A glitch in String Translation update causes a (harmless) warning

Immediately after release of WPML 3.5, we noticed a cosmetic glitch which may happen in some of the sites updating automatically. These messages will appear only once and they don’t cause any problem to the site.

This glitch doesn’t look nice, but it’s not causing any damage. Since WPML 3.5 is needed for WordPress 4.6 (which is coming out tomorrow), we didn’t hold with that update. We’ll fix that glitch tomorrow morning and release a minor update for WPML String Translation.

Removed the WPML Widget from the WordPress Dashboard

Until WPML 3.5 there was a WPML Widget on the Admin Dashboard. This widget started with good intentions, but grew to be a resource sink. Over time, we kept adding all sorts of information to that widget. It pulled and displayed recent blog posts, the languages summary and translation status and a host of other trivia. You can imagine that all this wonderfully useless information required database queries (and some remote queries) and PHP processing.

We decided that the added value in this information doesn’t justify the load it produces and we removed it. If you feel that any of that information was useful to you, let us know. Our admin dashboard became a lot faster, just by removing that widget.

As a side note, while reviewing that widget, we noticed a few similar widgets, suggestions and “nice to know” tips from other plugins and themes. If you’re seeing them on your dashboard, make sure that they’re not slowing down your sites (like WPML’s widget did).

Download and update

As always, the best way to get updates to WPML is by registering your sites and updating automatically. You can always download from your WPML account. Be sure to update all of WPML’s components that you’re using.

Feedback?

Let us know your thoughts about this update by leaving a comment. We’re eager to know how it’s working for you. If you need help resolving problems, please first create a ticket in our technical support forum. Then, add a comment here with a brief description and a link to the support ticket.