WPML 3.3 is ready as “release candidate”. This means that we’ve fixed everything we knew about, was reported to us, or found internally. We’ve done initial testing for everything, but not yet our full QA cycle.
The main feature in this release is the ability to run sites without English, easily. We got good feedback about this and now we’re almost ready to release WPML 3.3 for production sites.
Here is a full list of changes. Some of the updates in WPML 3.3 resolve problems. If a problem that bothers you appears here, we encourage you to try this RC and see that the problem goes away.
WPML Core
Features
- Sync content between domains, when using languages in domains. This was needed for WooCommerce, and in preparation for other upcoming features
- Added button to clear all WPML caches
- WPML now allows to load a taxonomy template by language, also for the default language
Performance improvements
- Improved browser redirect performance
- Fixed performance issues when listing posts (easily noticed when listing many WooCommerce products)
Fixes
- Fixed the “Display hidden languages” options for users
- Fixed an issue causing a notice and incorrect results for certain taxonomy queries that involved custom post types
- Filter url for scripts and styles when language is per domain
- Resolved notice “Undefined index: strings_language” after WPML activation
- Resolved http(s) protocol and different domains per language issues
- Added button to to clear all WPML caches
- Resolved broken settings issue with WooCommerce during WPML activation
- Fixed redirection for child pages
- Resolved notices when selecting “All languages” in admin
- Removed Translation Management dependency when duplicated posts are updated
- Resolved issues when deleting a Layout which has no cells (hence no package)
- WPML now allows to load a taxonomy template by language, also for the default language
- Added ‘blog_translators’ filter to programmatically change the list of translators
String Translation
Features
- Allow icl_register_string to register a string in any language
- Added the package language to the URL to the translation dashboard (this applies to the Package box, where used by other plugins like Layouts)
- Add a language selector to the package metabox (eg. as seen on the Layout editor)
- Add a language selector to the Admin bar menu to set the language of a package (eg. as seen on GravityForms)
- Add support for sending strings in any language to the translation basket
Fixes
- Email footer text is now properly translated
- Fixed string status, when they are created by packages
Translation Management
Features
- Add support for sending strings in any language to the translation basket
- Added action in Translation Jobs tab, to trigger translation download for batches
- Added words count feature in Translation Dashboard
Fixes
- Added action in Translation Jobs tab, to trigger translation download for batches
- Automatically detect the best polling method and update the settings accordingly
- Created a filter to override \WPML_TM_Blog_Translators::is_translator
- Fix so that post format is synchronized as required
WPML-Media
Fixes
- Fix duplication of featured image when using the translation editor
Gravityforms Multilingual
Features
- Added ability to change the language of a form
WPML CMS Navigation
Fixes
- Breadcrumb menu for archive pages and CPT single pages
Download
To download, go to your WPML account. Click on Downloads and scroll all the way to the bottom. Download the CMS Beta Package. This ZIP file includes all of WPML’s components. You need to use the WPML components from this ZIP only and not mix development versions with production versions.
Schedule for production release
WPML 3.3 is going into full QA now. It usually takes us about two weeks to run a complete testing cycle. We encourage you to use this RC on development sites. By now, everything should work. Of course, that’s what testing is for.
Feedback?
Questions? Suggestions? Ideas? Leave your comment and we’ll get back to you.