WPML String Translation 3.2.11

Features

• Performance improvements for String Packages
• Allow registering page builder strings when the post has the “draft” status
• Merged WPML Page Builder plugin into WPML String Translation
• Set optimal ST settings to improve performance
• Performance improvements in translating functions
• Disable ST gettext hooks in English language
• Handle settings coming from the custom XML

Fixes

• Improved performances of the [wpml-string] shortcode
• Fixed a compatibility issue between Gravity Form and Beaver Builder while sending a translation job
• Added the ability to allow html tags in shortcode attributes
• Prevent parsing shortcodes mixed with regular content
• Fixed the taxonomy label translations from WPML -> Taxonomy Translation which were not applied
• Fixed issue where translation was not updated when the same string value was used in two different element types
• Added filters for Elementor and Beaver Builder so developers can add translation support for custom widgets and modules
• Title of Widget Language Switcher has been registered two times
• Fixed a fatal error when translating strings as a translator with PHP 7.1

• Cleaned up the page builder strings after a translation job is completed
• Stopped multiple occurrences of the same page builder field in the Translation Editor
• Fixed the page builder translations fetched via XML-RPC
• Fixed the [wpml-string] shortcode not registering strings with the given context or name
• Fixed an issue where links pointing to the Home page weren’t adjusted properly in translations

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