We are very happy to release WPML 3.1.7 today. This releases includes several exciting improvements, some bug fixes and complete compatibility with WordPress 4.0.
Auto-Upgrade Inside WPML
A while back, WPML had its own auto-upgrade code. Then, we removed it and started using our Installer plugin. We heard your voice and we realized you’re not happy with that decision. Today, we retire Installer and WPML gets its own auto-upgrade code again. This time, auto-upgrade is much more powerful, convenient and secure for you.
One of the highlights of this change is the introduction of unique site-keys. Now, when you install WPML on a new site (for yourself or for your client), you will need to generate and insert a site-key, created especially for that site. This way, you no longer enter your login for wpml.org into client sites. Your clients will receive automatic upgrade for WPML, from your account, but without using your login. If you ever need to, you can also cancel site-keys that you have created.
You can see the new registration workflow in WPML’s installation instructions.
Automatic Download and Install for wpml-config.xml Files
WPML can read configuration files for themes and plugins, telling it what needs translation (CPTs, fields, option entries).
From now on, WPML will be able to automatically download these config files. This means that when we work on compatibility with other themes and plugins, you don’t need to wait for their update, to get compatibility with WPML. We are going to use that very soon to improve compatibility with all WooThemes themes and their ‘addon’ plugins.
WordPress 4.0 Compatibility
To achieve full compatibility with WordPress 4.0, we had to make some changes to how WPML uses the Visual Editor and also stop using a few API functions which got deprecated in WordPress 4.0. Overall, the changes were not huge, but they are important. Before you upgrade WordPress to 4.0, be sure to upgrade WPML and all its components.
Bug Fixes and Performance Improvements
WPML core
- Compatibility with WordPress 4.0
- Added « Remote WPML config files » functionality
- Added shortcodes for language switchers
- WP SEO plugin compatibility enhancements
- New version of installer
- Fixed broken relationship consistency when translating posts
- Fixed url filters for different languages in different domains configured
- Added various descriptions of WPML settings, displayed on configuration screens
- Gained better compatibility with non-ASCII languages
- Several additional bug fixes
- Several cosmetic changes
WPML Media Translation
- Fixed compatibility with Types plugin
- Fixed issue with hundreds of duplicated images
- Language_filter_upload_page() supports now multiple mime types and mime types with wildcards
WPML String Translation
- New way to translate strings from plugins and themes: being on plugin/theme configuration screen, switch language using switcher in admin bar and provide translation
- Several additional bug fixes
WPML CMS NAV
- Changes to improve stability of the WPML core plugin
WPML Sticky Links
- Changed priority for the ‘save_posts’ hook
WPML Translation Management
- Changes to improve stability of the WPML core plugin
- Cosmetic changes to improve usability
Download and Upgrade
Now that we are retiring the Installer plugin, please deactivate it from your sites. Then, manually download WPML 3.1.7 from your WPML.org account, install and activate.
After activation, go to Plugins and you will see a prompt to register WPML. Have a look at the updated installation instructions to see how you should generate a site key. It’s easy, more secure and takes less than a minute.
Next times, updates will be available automatically for your sites.
Next for WPML
Like you probably know, we have been hard at work on WPML 3.2. This major update will come with significant enhancements to the translation management and offer exciting new possibilities for professional translation.
We are also getting ready with a new API for translating ‘complex’ plugins. This will allow you to easily translate sites created with page-builders. The first working example will be our very own Layouts plugin, which will be multilingual-ready using this interface.
Questions? Ideas? Suggestions? Leave your comments and we’ll reply.