- Released
- July 8, 2013
- Channel
- Stable
- Tested with WordPress
- 3.6.0
- Product
- WPML Multilingual CMS
Changelog
Features
Title tags added to navigation
rel=canonical now optional configurable under WPML -> Languages → SEO Options
Allow to select all languages when sending documents to translation from the Translation Dashboard
Improved Import/export .po from String Translation screen
Flag only language switcher. Including horizontal layout.
Preserve url parameters in the language switcher
Use directory for default language
Duplicate all custom fields and taxonomy when duplicating the post
New function in the Troubleshooting section to set update translation tables after changing the slug for custom posts or custom taxonomies that had translated elements.
Allow re-assigning translation jobs
Support wildcards in wpml-config.xml for entries in the options table
Added the Malay language
Bugs
Browser language redirect (some IE versions)
Custom flag icons do not display on post table columns (posts screen)
Slug translation in LS not working when WPML default language is different than ST original language
Language order not applied before first drag
Changing the slug of a taxonomy breaks things
Wrong url for custom posts with translated slug.
WPML making Bbpress menu disappear
Notifications not being sent to translators when jobs were cancelled
Misc
Changed references to deprecated jQuery function live() -> WPML minimum required WordPress version is now 3.3
WPML Core – 2.9
WPML String Translation – 1.8
WPML Translation Management – 1.7
WPML Media – 1.5
Update or download
The update is available to all WPML clients with an active subscription — it appears on the Plugins page in your WordPress admin within 24 hours of release. You can also check for it right away under Plugins → Add New Plugin → Commercial. To download and install manually, go to Downloads in your wpml.org account (see the installation instructions) and remember to update all components together without mixing versions.
Need help or want to give feedback? Please use our technical support forum.