WPML String Translation 3.5.3

Implemented an additional check to ensure that the “translator_note” column is created for the String Translation table.

3.4.0

[Accessibility] Improved colors and contrast according to European Accessibility Act (EAA) standards.
Fixed incorrect translation in the Customizer when the user profile language differs from the site’s default one.
Fixed inability to create taxonomy labels in a language other than English.

Fixed an error with the Glossary sync process
Improved the error parsing for corrupted content
Fixed an issue where the Other texts (Strings) section on the Translation Dashboard was displaying no strings in certain cases
Fixed an issue where linebreaks were removed from mail notifications in secondary languages
Fixed an issue with the formatting of HTML tags when importing PO files
Fixed an issue where backslashes were removed in string translation
Fixed an issue where Gravity Form Translations were not removed on the frontend
Implemented a fix that now allows using 0 (zero) as a valid input in String Translation
Fixed an error on the Translation Dashboard that happened when too many languages were active
Fixed a few edge cases where translations from translation (.po) files were not fully loaded for strings autodetected by WPML
Fixed an issue with autodetecting strings that have incorrect HTML tags
Fixed an issue with importing translation (.po) files when the default language is not English
Removed a deprecated feature for auto checking .mo files

Fixed an issue with missing strings on multisites
Fixed an error when installing the String Translation add-on using Composer 2.7.9

Features

• Added automatic registration of untranslated strings during page visits.
• Included auto-registration of front-end strings in Translate Everything Automatically.
• Revamped the String Translation UI for better usability.
• Updated the Filter sections for improved navigation.
• Hidden page builder strings by default from String Translation.
• Added a bulk select option with the ability to choose all matching selections across different pages.
• Revamped the Utilities section GUI.
• Moved the option to send strings for automatic translation to the Translation Management Dashboard.

Fixes

• Fixed an issue where the Strings table did not load after resending a string for translation.
• Resolved infinite retries when scanning MO files in cases of database corruption.
• Fixed an issue where admin strings were not added to “_icl_admin_option_names”.
• Resolved an issue where slug translation cache was not part of the cache group.
• Fixed a PHP 8 deprecation warning for the “preg_match” null parameter.
• Renamed “Clear invalid strings” to “Check for string issues” in String Translation Troubleshooting.
• Enhanced performance when String Translation is enabled with WPML 4.7.
• Fixed an issue with String filters when auto-registration of strings is enabled.
• Updated interface translations for the WPML String Translation plugin.

Fixed a PHP warning caused by a change in WPML String Translation 3.2.16. The warning would happen when the website uses open_basedir and contains the word “mo” in its domain name (e.g. “slowmotion.com”).

Fixed an issue with missing translations introduced by WordPress 6.7 changes for environments that have a custom locale, like de_DE_formal.

Prevented loading of plugin translations before the WordPress init hook to avoid warnings appearing on the front-end and backend

Fixed an issue with untranslated content being rendered on the frontend in certain cases with WordPress 6.5.