WPML String Translation 3.3.2

Features

• Implemented the scanning of strings for Must-use (MU) plugins.

Fixes

• Implemented multiple security fixes.
• Fixed an issue where page builder fields were missing when creating a new translation of pre-existing posts.
• Fixed escaping of contexts when exporting .po files.
• Fixed an issue when saving Elementor page translation, to save the post body correctly.
• Made Elementor form select fields translatable.

Fixes: Fixed issue with 404 errors on products created in secondary languages when default language is different than English.

Features

• Added filters used when shortcode attributes (from page builders) are encoded/decoded
• Performance improvement in automatic .mo file scanning
• Adjusted the option for assuming that the original language of strings is in English in the case that the default site language is different than English

Fixes

• Fixed an issue where converting a text widget to multilingual text widget adds another instance of the widget
• Converting text widget to multilingual text widget adds another instance of the widget
• Fixed an issue with Elementor Pro slide’s links which were not translatable
• Fixed an issue when trying to scan string with no item selected
• Remove post string packages when the related post is permanently deleted
• Fixed issue with strings caching in secondary languages
• Fixed performance bottleneck by allowing empty strings to be registered
• Fixed issue with String translation loading translations from db instead of .mo files when the respective options are checked in Theme and plugins localization
• Resolved exception resulting in many entries in wp_icl_string_urls table when Languages as Directories are configured
• Fixed issue with automatic .mo scanning for Child themes.
• Fixed issue with notice for applying fastest settings in Theme Plugin Localization screen
• Fixed issue with the admin being partially shown in the wrong language
• Fixed issues with Taxonomy label translation