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 CoreFeaturesSync content between domains, when using languages in domains. This was needed for WooCommerce, and in preparation for other upcoming featuresAdded button to to clear all WPML cachesWPML now allows to load a taxonomy template by language, also for the default languagePerformance improvementsImproved browser redirect performanceFixed performance issues when listing posts (easily noticed when listing many WooCommerce products)FixesFixed the “Display hidden languages” options for usersFixed an issue causing a notice and incorrect results for certain taxonomy queries that involved custom post typesFilter url for scripts and styles when language is per domainResolved notice “Undefined index: strings_language” after WPML activationResolved http(s) protocol and different domains per language issuesAdded button to to clear all WPML cachesResolved broken settings issue with WooCommerce during WPML activationFixed redirection for child pagesResolved notices when selecting “All languages” in adminRemoved Translation Management dependency when duplicated posts are updatedResolved 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 languageAdded ‘blog_translators’ filter to programmatically change the list of translatorsString TranslationFeaturesAllow icl_register_string to register a string in any languageAdded 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 basketFixesEmail footer text is now properly translatedFixed string status, when they are created by packagesTranslation ManagementFeaturesAdd support for sending strings in any language to the translation basketAdded action in Translation Jobs tab, to trigger translation download for batchesAdded words count feature in Translation DashboardFixesAdded action in Translation Jobs tab, to trigger translation download for batchesAutomatically detect the best polling method and update the settings accordinglyCreated a filter to override WPML_TM_Blog_Translators::is_translatorFix so that post format is synchronized as requiredWPML-MediaFixesFix duplication of featured image when using the translation editorGravityforms MultilingualFeaturesAdded ability to change the language of a formWPML CMS NavigationFixesBreadcrumb menu for archive pages and CPT single pagesDownload
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.
Questions? Suggestions? Ideas? Leave your comment and we’ll get back to you.
Read more here:: WPML 3.3 RC – String Languages, Stability and Performance