Allgemeine Texte übersetzen
See full descriptionVersion 3.5.1
Fixes
- Fixed an issue where the post slug appeared as not translated when using the „Translatable – use translation if available or fallback to default language“ translation setting.
- Removed some file leftovers that were causing false positive security issues to be flagged by WordFence.
- Fixed an issue where translation of strings would not overwrite existing translations even when selecting that option in the Translation Dashboard.
- Added a check to prevent Greek character slugs from being converted to HTML entities.
Version 3.5.0
Feature
- Added support for translating strings found in JavaScript files.
Fixes
- Added a meaningful status feedback for stuck jobs.
- Added the JavaScript files to the „Can’t find strings section?“ on the WPML > String Translation page.
- Fixed incorrect formating in right-to-left (RTL) language emails.
- [Object Cache] Fixed an issue where a scan done on the WPML > „Themes and plugins localization“ page would only register new strings after clearing object cache.
- [Object Cache] Fixed an issue where the translation term page didn’t work on the frontend after translating the term slug with String Translation.
- [Object Cache] Fixed an issue with deleted strings not added after rescanning.
Version 3.5.0-b.3
Fixes
- Reverted a change that was causing 504 Gateway Timeout errors when updating the String Translation plugin.
Version 3.5.0-b.2
Fixes
- Added a meaningful status feedback for stuck jobs.
- Added the JavaScript files to the „Can’t find strings section?“ on the WPML > String Translation page.
- Fixed incorrect formating in right-to-left (RTL) language emails.
Version 3.5.0-b.1
Feature
- Added support for translating strings found in JavaScript files.
Version 3.4.1
Fixes
- Implemented an additional check to ensure that the „translator_note“ column is created for the String Translation table.
Version 3.4.0
Fixes
- Added the option to search by a string name in the „Other texts (strings)“ section on the Translation Dashboard.
- Fixed an issue with partially translated WooCommerce emails.
- Added support for database optimization to reduce the size of the
*_icl_translateand*_icl_translation_statustables. - Fixed a fatal error caused by an incorrect WPML core dependency.
Version 3.4.0-b.1
Fixes
- Added the option to search by a string name in the „Other texts (strings)“ section on the Translation Dashboard.
- Fixed an issue with partially translated WooCommerce emails.
- Added support for database optimization to reduce the size of the
*_icl_translateand*_icl_translation_statustables. - Fixed a fatal error caused by an incorrect WPML core dependency.
Version 3.3.3
Fixes
- [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.
Version 3.3.2
Fixes
- 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
Version 3.3.1
Fixes
- Fixed an issue with missing strings on multisites
- Fixed an error when installing the String Translation add-on using Composer 2.7.9
Version 3.3.0
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.
Version 3.3.0.rc.1
Fixes
- Fixed issues reported during testing of WPML 4.7 Beta 2 version
- Updated interface translations for the WPML String Translation plugin
Version 3.3.0-b.2
Fixes
- Enhanced performance when String Translation is enabled with WPML 4.7
- Fixed an issue with String filters when auto-registration of strings is enabled
- Fixed issues reported in Beta 1
- Added support for WordPress 6.7
Version 3.3.0-b.1
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.
Version 3.2.18
Fixes
- 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“).
Version 3.2.17
Fixes
- Fixed an issue with missing translations introduced by WordPress 6.7 changes for environments that have a custom locale, like de_DE_formal.
Version 3.2.16
Fixes
- Fixed an issue where .mo files failed to load due to recent changes in WordPress 6.7.
- Fixed an issue where strings with custom or default plugin translations did not load after upgrading to WordPress 6.7.
- Fixed an issue where default string translations were not loaded on the default WordPress theme when custom translations were added using WPML.
Version 3.2.15
- Prevented loading of plugin translations before the WordPress init hook to avoid warnings appearing on the front-end and backend
Version 3.2.15-b.1
- Avoid loading plugin translations before WordPress init hook. This causes warnings to be displayed on front-end and backend.
Version 3.2.14
- Fixed an issue with untranslated content being rendered on the frontend in certain cases with WordPress 6.5.
Version 3.2.13
- Added PHP 8.3 compatibility
- Fixed various deprecated notices with PHP 8.x
Version 3.2.12
- Fixed a broken access control vulnerability.
Version 3.2.11
Fixes
- Fixed a fatal error that occurred on sites installed before WPML 4.3, which had MO files in the languages/wpml/missing folder.
- Improved the cache mechanism for loading MO files to invalidate the cache on a per-language basis.
Version 3.2.10
- [WordPress 6.5] Fixed a discrepancy between the „locale“ settings in WordPress and WPML objects.
- Adapted our translation loading mechanism to the changes in WordPress 6.5
- Enforced the update of custom translation files when the strings in a package job are updated.
- Enabled the loading of string package API on CRON requests
Version 3.2.9
- Added an effective way to query widget options
- Added a hook to support the WordPress Performant Translations plugin
Version 3.2.8
- Fixed a compatibility issue with the MO file loader in WordPress 6.3 which was causing performance problems and missing translations on some environments.
Version 3.2.8-b.2
- Fixed compatibility with WP 6.3 MO loader that was causing serious performance problems and missing translations on some environments.
Version 3.2.8-b.1
- Fixed an endless translation loop in String Translation occuring on sites running both WordPress 6.3 and WooCommerce.
Version 3.2.7
- Added more fixes for PHP 8 deprecations.
- Added a new string troubleshooting button to the Support Troubleshooting section.
Version 3.2.6
Fixes
- Added PHP 8.1 compatibility.
- Fixed an issue with HTML tags being stripped from original strings while importing a .PO file.
- Replaced capability with the updated capability library.
- Fixed Right-To-Left styling issues.
- Fixed an issue where the notification about the directory being not writable.
- Fixed an issue when search using a single quote returned no results.
- [Security] Sanitized the user input fields.
- Added support for searching for HTML encoded strings.
- Added notice on the WPML Strings Translation page informing that strings created in non-default language cannot be automatically translated.
- Fixed an issue with all admin string status changes to Needs Update when only one admin string is updated.
Version 3.2.5
Fixes
- Resolved an issue with scanning strings which was related to PHP 8.1 compatibility.
Version 3.2.4
Fixes
- Improved caching for the custom domains query.
- Fixed an issue with taxonomy slugs registered with a forward slash.
- Fixed a fatal error which occurred when domain names contained single quotes.
- Updated security checks for all the ST Ajax endpoints.
- Removed the umask() call.
Version 3.2.4-b.1
Fixes
- Improved caching for the custom domains query.
- Fixed an issue with taxonomy slugs registered with a forward slash.
- Fixed a fatal error which occurred when domain names contained single quotes.
- Updated security checks for all the ST Ajax endpoints.
- Removed the umask() call.
Version 3.2.3
- Fixed a fatal error that occurs when running WPML with WordPress version 6.1.
Version 3.2.3-b.1
- Fixed a fatal error that occurs when running WPML with WordPress version 6.1.
Version 3.2.2
- Fixed an issue with the cancellation of string-related translation jobs
- Fixed an issue with autoregistering strings when „Load textdomain“ option is enabled as well
- Fixed an issue with the MO files preloading query to match only the possible official WP patterns
- Fixed an issue where automatic loading of MO files was not enabled when the option to auto-register strings was turned on
- Fixed an issue with Translate Link Target when the category base is translated
- Fixed multiple issues related to PHP 8 deprecations
- Fixed an issue with allowing to force translating admin texts
- Applied further optimizations to reduce the amount of autoloaded data from the database
Version 3.2.1
Bugfixes
- Fixed an issue where the translation modal was not displayed correctly on large screens.
- Fixed an issue with small spacing between filtering options rows.
Compatibility
- Fixed an issue with translation of Woodmart theme header.
Version 3.2.0
Features
- Added support for translations of JavaScript strings (particularly for features in the admin pages).
Fixes
- Disabled Translate button in String Translation UI when no languages are selected.
- Fixed an issue with wrong translations of admin texts showing in admin UI.
- Fixed an issue with escaping the apostrophe in SQL query when searching for strings.
- Added the ability to register strings from legacy Text widgets in a default language. Before, it was always registered in English.
- Fixed an issue with translating admin-texts that have special characters in their name.
- Fixed a problem with upgrade failing to finish.
Version 3.2.0-rc.1
Fixes
- Fixed a problem where the plugin update failed to finish.
Version 3.2.0-b.2
Fixes
- Fixed an issue with escaping the apostrophe in SQL query when searching for strings.
- Fixed an issue with registering strings from legacy Text widgets in a default language. Before, they were always registered in English.
- Fixed an issue with translating admin texts that have special characters in their name.
Version 3.2.0-b.1
Features
- Fixed the lack of translations of JavaScript strings (particularly for features in the admin pages).
Fixes
- Disabled Translate button in String Translation UI when no languages are selected.
- Fixed issue with wrong translations of admin texts showing in admin UI.
Version 3.1.10
- Added a small performance fix.
Version 3.1.9
- Fixed an issue with registering data attributes content as strings.
- Fixed an issue with registering MO files for some languages.
- Fixed the missing expiration time for an upgrade lock.
- Added support for WordPress 5.8 widget blocks.
- Removed legacy multilingual widgets and prepared their migration to text widgets.
Version 3.1.8
Fixes
- Fixed issue with wp_localize_script in WordPress 5.7.
- Fixed error on String Translation page when string contains encoded HTML entities.
Version 3.1.7
Features
- Improved settings consistency for term link filtering.
Fixes
- Fixed styling for String Translation database upgrade message.
- Fixed handling of slug translation for Display as translated post types.
- Fixed missing pagination in WPML → String Translation.
- Fixed an issue so that query to create wp_icl_string_batches table is only run once.
- Fixed a 404 error after changing the language of a custom post type’s slug.
Version 3.1.7-b.1
Features
- Improved settings consistency for term link filtering.
Fixes
- Fixed styling for String Translation database upgrade message.
- Fixed handling of slug translation for Display as translated post types.
- Fixed missing pagination in WPML → String Translation.
- Fixed an issue so that query to create wp_icl_string_batches table is only run once.
- Fixed a 404 error after changing the language of a custom post type’s slug.
Version 3.1.6
Fixes
- Replaced incorrect documentation link.
- Fixed required parameters following optional ones.
- Replaced usage of deprecated function _get_path_to_translation with wp_textdomain_registry class.
- Fixed problem with slug translation when post type slug has a numeric value in it.
- Fixed WPML_Package_Exception when trying to edit translation.
Version 3.1.6-b.2
Fixes
- Added sanitization of user inputs in GET and POST.
Version 3.1.6-b.1
Fixes
- Replaced an incorrect documentation link.
- Fixed issues with required parameters following optional ones.
- Replaced usage of deprecated function _get_path_to_translation with wp_textdomain_registry class.
- Fixed problem with slug translation when post type slug has a numeric value in it.
- Fixed WPML_Package_Exception when trying to edit translation.
Version 3.1.5
Fixes
- Remove match function for PHP 8 compatibility.
- Fixed wrong link to the String Tracking documentation page.
- Fixed JS error on Admin texts page caused by unescaped string values.
Usability
- Fixed filtering WPML packages.
Version 3.1.4
Fixes
- Show ’needs update‘ icon in string translation UI as required.
- Fixed changes comparison in Classic Editor when Gutenberg post is edited.
Compatibility
- Fixed a JS conflict due to different versions of the select2 library.
Version 3.1.3
- Handled the fatal error which appeared when an option’s value has been changed from flat to nested value.
Version 3.1.2
- Fixed corruption when saving options in a language different than the original.
Version 3.1.1
Fixes
- Fixed disabled state of Change the language of selected strings and Change translation priority of selected strings after selecting strings in the String Translation table.
- Removed inactive languages from String Translation interface.
- Fixed adding strings with default language other than English to the Translation Basket.
Version 3.1.0
Features
- Added pagination options and sorting to the Admin Strings table. Changed table rows to have fixed height and expand on click.
- Removed unused code from Admin Strings.
- Improved copyright in the Admin Texts Translation screen.
- Improved styling on the Admin Texts Translation page.
- Changed Admin Texts Translation search to be not case-sensitive.
- Added the ability to automatically (re)generate custom MO files if they are missing or outdated.
Fixes
- Fixed error in String Translations when the String Translation table contains strings with quotes.
- Fixed translating of the admin texts via the WooCommerce Settings Page.
- Increased the length of domain field in icl_mo_files_domain table to allow for some plugins that have long domain names.
- Fixed problem where MO file translation was not being overridden by translated value in database.
Compatibility
- Fixed 404 error when using display as translated mode for products and product base is /product/%product_cat%/.
- Improved the slug translation compatibility for 3rd party themes and plugins.
Usability
- Improved search in String Translation to include also string name and context.
- Fixed problem with String Translation when using multisite and more than 100 subsites.
Version 3.1.0-b.1
Features
- Removed unused code from Admin Texts Translation page.
- Improved copyright in the Admin Texts Translation screen.
- Improved styling on the Admin Texts Translation page.
- Changed Admin Texts Translation search to be not case-sensitive.
- Automatically (re)generate custom MO files if they are missing or outdated.
Fixes
- Fixed error in String Translation when the string translation table contains strings with quotes.
Compatibility
- Improved the slug translation compatibility for 3rd party themes and plugins.
Usability
- Improved search in String Translation to include also string name and context.
- Fixed problem with String Translation when using multisite and more than 100 subsites.
Version 3.0.14
Fixes
- Fixed calls to deprecated jQuery functions.
Version 3.0.13
Fixes
- Fixed unexpected checkbox behaviors due to jQuery changes in WP 5.5.
Version 3.0.12
Fixes
- Fixed a potential security issue with select2.
Usability
- Fixed the translating of a string when its original language is changed.
Version 3.0.11
- Fixed a parse error in PHP 5.6 due to reserved function name forEach.
Version 3.0.10
Fixes
- Added a meaningful icon and tooltip when a translation is still being processed.
Compatibility
- Fixed incorrect processing of media shortcodes.
Version 3.0.9-b.1
Fixes
- Fixed generation of missing native MO files when a site has been moved to a different location.
- Fixed a problem with translating strings via the _x function when the $number parameter has a string value of „1“. We used to use a plural form instead of singular.
- Code improvement in the String Translation plugin.
Compatibility
- Fixed a fatal error that happened because of an outdated hook signature for get_the_author_{$field}.
- Added a fix to prevent infinite loops when loading „just in time“ MO objects.
Version 3.0.8
- Handle gracefully the fatal error when JED files are generated.
Version 3.0.7
Features
- Detect automatically if an MO file from a domain should be pre-loaded.
Fixes
- Fixed a performance issue in „WPML_String_Translation::get_string_language_filter“ caused by incorrect caching.
- Fixed loading of custom string translations when a language locale is custom and unusual.
Compatibility
- Fixed an error preventing from scanning translation files when the PHP version is older than 7.0.
Version 3.0.7-b.2
Features
- Detect automatically if MO file from a domain should be pre-loaded.
Fixes
- Fixed performance issue in `WPML_String_Translation::get_string_language_filter` caused by incorrect caching.
- Fixed loading of custom string translations when a language locale is custom and unusual.
- Fixed an error preventing from scanning translation files with PHP < 7.0.
Version 3.0.7-b.1
Fixes
- Detect automatically if MO file from a domain should be pre-loaded.
Version 3.0.6
Fixes
- Fixed the generation of custom MO Files when a string has an empty original value. It could happen for admin strings.
- Fixed a broken link to one of our documentation pages about performance considerations.
Compatibility
- Fixed deprecation notices (`Function get_magic_quotes_gpc() is deprecated`) when running PHP 7.4.
- Fixed PHP 7.4 notices shown when translating a page created with Beaver builder and OPCache is used.
Version 3.0.5
Fixes
- Fixed an issue blocking translation memory when a string has quotes.
- Fixed a database error when the wp_icl_mo_files_domains table does not exist yet.
- Fixed the translation of strings with the same value but different names inside a common domain.
Version 3.0.4
Features
- Restored functionality to translate page builder strings from ST UI.
- Implemented a better handling of missing language folders for custom MO files.
- Always display the MO pre-generation button in the troubleshooting page when there’s at least one custom translation.
Fixes
- Fixed a warning in WPML > Theme and Plugins Localization when the plugin was removed.
- Fixed translation of strings translated with `icl_translate` when the original value is not matching.
Version 3.0.4-b.1
Features
- Restored functionality to translate page builder strings from ST UI.
- Implemented a better handling of missing language folders for custom MO files.
- Always display the MO pre-generation button in the troubleshooting page when there’s at least one custom translation.
Fixes
- Fixed a warning in WPML > Theme and Plugins Localization when the plugin was removed.
- Fixed translation of strings translated with `icl_translate` when the original value is not matching.
Version 3.0.3
- Fixed a fatal error when a locale language contained a number (e.g. „fr3_FR“).
- Fixed an issue where string translations were not shown on the front-end when strings are registered with long names.
Version 3.0.2
Compatibility
- Fixed an infinite loop error where the „override_load_textdomain“ filter would always return „true“, even if the MO object was not loaded.
Version 3.0.1
Fixes
- Fixed a fatal error for WordPress versions older than 5.0.0 with missing function wp_set_script_translations.
- Fixed a warning „Strict standards: Static function…“ thrown with PHP 5.6.
- Fixed an error preventing from scanning translation files with PHP < 7.0.
Version 3.0.0
Features
- Added a troubleshooting action to re-display the „pre-generate MO files“ dialog if the translation files are
deleted from the server. - Added a troubleshooting option to clean up and optimize the strings tables in the database.
Fixes
- Fixed an error that could happen when WPML Core, String Translation, and Translation Management plugins were active but the setup was not complete.
- Fixed an issue with too big flags shown in the admin panel when custom flag image of a large size is used.
- Fixed the way of handling quotes in the blog title and description so translated strings are displayed correctly.
- Fixed the generation of PO files on the „Theme and plugins localization“ page. Now, we include only strings belonging to a selected domain, instead of all strings from a plugin.
Compatibility
Fixed the generation of the .htaccess file when the permalinks cache is flushed.
Performances
- Allow using the „Assume all strings have English original“ option on any language to improve performance.
- Improved the performance of upgrade commands.
- Introduced a completely new way of how String Translation handles strings. It is now based on MO Files instead of querying data from the Database. This helps to significantly reduce performance costs.
- Added the Multisite support to the new way String Translation loads strings using MO files. Now, it is possible to define different translations per site for the same string.
- Generate partial MO files for translated strings and use them for displaying strings in other languages, instead of accessing the database.
- Improve the new usage of MO files in the String Translations plugin to support WordPress Multisite setup.
- Significantly improved the site performance on when updating the page, post, or a WooCommerce product page in the admin.
Usability
- Don’t show package strings in the String Translation user interface.
Version 3.0.0-rc.1
Features
- Added a troubleshooting action to re-display the „pre-generate MO files“ dialog if the translation files are
deleted from the server. - Added a troubleshooting option to clean up and optimize the strings tables in the database.
Fixes
- Fixed an error that could happen when WPML Core, String Translation, and Translation Management plugins were active but the setup was not complete.
- Fixed an issue with too big flags shown in the admin panel when custom flag image of a large size is used.
- Fixed the way of handling quotes in the blog title and description so translated strings are displayed correctly.
- Fixed the generation of PO files on the „Theme and plugins localization“ page. Now, we include only strings belonging to a selected domain, instead of all strings from a plugin.
Compatibility
Fixed the generation of the .htaccess file when the permalinks cache is flushed.
Performances
- Allow using the „Assume all strings have English original“ option on any language to improve performance.
- Improved the performance of upgrade commands.
- Introduced a completely new way of how String Translation handles strings. It is now based on MO Files instead of querying data from the Database. This helps to significantly reduce performance costs.
- Added the Multisite support to the new way String Translation loads strings using MO files. Now, it is possible to define different translations per site for the same string.
- Generate partial MO files for translated strings and use them for displaying strings in other languages, instead of accessing the database.
- Improve the new usage of MO files in the String Translations plugin to support WordPress Multisite setup.
Usability
- Don’t show package strings in the String Translation user interface.
Version 3.0.0-b.9
Features
- Allow to use the „Assume all strings have English original“ option on any language to improve performance.
- Improved the performance when running the upgrade commands.
- Introduced a new String Translation workflow on MO Files instead of data in the database. This helps improve performance significantly.
- Generate partial MO files for translated strings to use when displaying strings in other languages, rather than accessing the database.
- Added a troubleshooting action to re-display the „pre-generate MO files“ dialog.
- Added a troubleshooting option to clean up and optimize strings tables in the database.
- Prevent to display package strings in the String Translation user interface.
Fixes
- Fixed an error when WPML core, String Translation, and Translation Management plugins are active but setup is not complete.
- Fixed a problem with too big flags in the admin panel when custom flag images of big dimensions are loaded.
- Fixed an issue with quotes in the blog title and description so translated strings are displayed.
Version 2.10.7
- Fixed an issue with 404 errors for translated pages using certain page builders (such as SiteOrigin) where the slug base was translated (e.g. for products).
Version 3.0.0-b.8
Features
- Added a feature that generates partial .mo files for translated strings. These partial .mo files are then used for displaying strings in other languages, rather than accessing the database.
- Added a troubleshooting option to cleanup and optimize strings tables in the database.
- Don’t show package strings in the String Translation user interface.
Version 2.10.6
Fixes
- Fixed caching of translated slugs on multisite WordPress installs.
- Implemented the caching of results for WPML_Slug_Translation::rewrite_rules_filter filter to avoid a severe performance problem which appears when Toolset Access plugin is activated.
- Exclude node_modules directories when scanning theme or plugins on the „Themes and plugins localization“ page.
Version 3.0.0-b.6
Features
- Stopped hooking to gettext functions to optimize performance.
- Improved the performance to run the upgrade commands.
Fixes
- Fixed a problem with too big flags in the admin panel when custom, large big flag image is loaded.
- Fixed an error when WPML Core, String Translation, and Translation Management plugins are active but the setup is not complete.
- Added a possibility to allow using the „Assume all strings have English original“ option on any language, to improve performance.
Version 3.0.0-b.5
Features
- Stopped hooking to gettext functions to optimize performance.
- Improved the performance to run the upgrade commands.
Fixes
- Fixed a problem with too big flags in the admin panel when custom, large big flag image is loaded.
- Fixed an error when WPML Core, String Translation, and Translation Management plugins are active but the setup is not complete.
- Added a possibility to allow using the „Assume all strings have English original“ option on any language, to improve performance.
Version 2.10.5.1
Features
- Improved performance when English is default and current language
Fixes
- Fixed an error when Core + ST + TM plugins are active but setup is not complete
- Fix icl_string_pages fields to unsigned and add index to improve query times
- Stop excessive DB queries when the ST page cache needs to be rebuilt
- Fix how the url is determined for the string page caching
- Fix issue with ST mo file import so that wp_option table is not updated unnecessarily
- Fixed an issue with the filesystem method chosen
Version 2.10.4
Fixes
- Fixed an issue with String Translation .MO file import so that the wp_option table is not updated unnecessarily.
Version 2.10.3
Fixes
- Fixed an issue with the cancellation of string translation jobs.
- Fixed an error on the Translation Management Jobs List page when non-English strings were sent for translation.
- Added a fix to prevent PHP warnings in the String Translation plugin.
- Fixed the table header on the String Translation page.
Version 2.10.3-b.1
Fixes
- Fixed a PHP warning in the String Translation plugin.
- Fixed the table header on the main String Translation page.
Version 2.10.2
Fixes
- Fixed an error message when slugs are longer than 255 chars.
- Added a fix to ensure the translation fields appear in the same order as they appear in the original.
- Added a fix to prevent „variable mismatched detected“ error in the admin, caused by String DB Caching.
Version 2.10.1
Fixes
- Added a fix which prevents the „variable mismatched detected“ error in admin caused by String DB Caching.
- Fixed a fatal error that happened when loading JED files from 3rd part plugins.
- Do not throw hard exception when .mo file passed to scanning is a blank value.
Version 2.10.0
Fixes
- Introduced the wpml_st_slug_translation_sanitize filter hook.
Version 2.9.2
- Fixed an issue with the duplicated string in Beaver Builder translation job.
Version 2.9.2-b.2
- Fixed the duplicated string in Beaver Builder translation job.
Version 2.9.1
Fixes
- Handle alternative line breaks in translation memory fixing issues with memory translation for Avada.
Version 2.9.0
Features
- Performance improvements.
- Added an option to extend string search to translated values.
Fixes
- Renamed the .mo file for Ukrainian language since we adjusted its locale to uk.
- Fixed cache invalidation when updating options.
Version 2.9.0-b.2
Features
- Performance improvements.
- Added an option to extend string search to translated values.
Fixes
- .mo file for Ukrainian language renamed since we adjusted locale to uk.
- Fixed cache invalidation when updating options.
Version 2.9.0-b.1
Features
- Performance improvements.
- Added an option to extend string search to translated values.
Fixes
- Fixed cache invalidation when updating options.
Version 2.8.8
Fixes
- Fixed an issue on the „Themes and Plugins Localization“ screen when saving the option to not use String Translation for translating themes and plugins
- Fixed the „check all items“ checkbox, found on the Themes and Plugins Localization screen
- Fixed the PHP 7.2 incompatibility issue in „Themes and Plugins Localization“
Version 2.8.7
Fixes
- Fixed performance issue when deleting Attachments by caching of long SQL request.
- Fixed an issue with string context when defined with double quotes.
Version 2.8.7-b.1
Fixes
- Fixed performance issue when deleting Attachments by caching of long SQL request.
- Fixed an issue with string context when defined with double quotes.
Version 2.8.6
Fixes
- Fixed four instances of wrong text-domain.
- Fixed an issue when adding an existing string to the database.
- Added some logic to automatically fix the strings table on string registration.
- Fixed an issue with the checkbox toggle on the Themes and Plugins Localization page.
Version 2.8.6-b.1
Fixes
- Fixed four instances of wrong text-domain.
- Fixed an issue when adding an existing string to the database.
- Added some logic to automatically fix the strings table on string registration.
- Fixed an issue with the checkbox toggle on the Themes and Plugins Localization page.