WPML String Translation 3.2.15

Features

• Allow scanning of multiple themes at once
• Added filters so that a plugin or a theme can override the page builder shortcode content or save the translated content

Fixes

• Fixed the wrong “Needs update” behaviour when using CornerStone
• Fixed malformed output for Call To Action in Visual Composer
• Fixed page builder shortcode handling so previous translation aren’t lost when the original is updated.
• Fixed the array_key_exists() expects parameter 2 to be array, null given warning on front-end in some circumstances
• Fixed issue preventing the string translation interface from showing up when the user had at least one language pair
• Fixed handling of Visual Composer’s links in “Button”, “Custom Heading” and “Call to Action” cells
• Fixed an issue when removing all strings from a particular context in a filtered view

Fixes

• Fixed the query which list items in the Translation Management dashboard
• Fixed exporting in po files duplicated strings with different contexts
• Removed feature for page builders that updates the translated post when the original post is updated

Features

• Grouped strings registered without context / domain

Fixes

• Raised the order of calling the wpml_translatable_user_meta_fields filter to allow displaying translated user meta on the front-end

API

• Add actions for cleaning up unused package strings wpml_start_string_package_registration and wpml_delete_unused_package_strings