String Translation

• Product category archives load again in every language when a translated product category base is the same word as the WordPress post category base (such as "category")

• wpml-string-translation: a product category base stored with a leading slash (as WooCommerce can store it) keeps its translated rewrite rules, so translated product category archives load again, and a translated shop page with the same slug shows its products again

• Fixed String Translation losing a page's untranslated strings when the auto-register queue could not be saved while another request held its lock; the queue is now kept and processed on the next run.

• Translations applied from the command line now write the page-builder texts as they do from the admin, and a job that could not write its texts no longer reads as completed.
• With string auto-registration disabled, String Translation no longer runs its string detector on every request.

What's new

• The theme and plugin scan can ignore strings from text domains that belong to other themes and plugins.
• The settings explain what each translation preference, Page URL option and scan option does to your content.
• Duplicate string packages can no longer be created.
• Translation files are regenerated when a language's locale changes.
• Security hardening: stored values are escaped, stored data is read more strictly, request input is validated and translation file names are safe.

Performance

• The site's languages are read once per request instead of once per plugin translation file, and no translation file loads twice.
• Front-end pages viewed by an administrator no longer look up every plugin's folder for each translation file, which took seconds on some hosts.
• Saving a post reads each of its string packages only once.
• Translated URL rules are built once instead of on every read, which speeds up WooCommerce pages.
• Translated URL rules are no longer rebuilt twice on every page when a theme or plugin registers post types late.
• Looking up categories and tags by slug no longer repeats the same work on every call.

Fixes in theme and plugin scanning

• The theme scan works for themes whose stylesheet sits in a subdirectory.
• Must-use plugins listed on Theme and plugins localization can be scanned for strings again.
• Theme and plugins localization lists must-use plugins as active with their text domain, and scanning a loader file also scans the folder it loads.
• Must-use code in a folder below mu-plugins can be scanned.
• With a child theme active, the parent theme is listed as active on Theme and plugins localization.
• Viewing the source of a string from a must-use plugin's folder shows its file and line.
• The 'No TextDomain' label of a theme or plugin without a text domain is no longer a link to an empty list.
• The theme scan logs each file the theme loads from outside its folder, which the scan skips, and says how to register those strings.

Fixes in translation files

• Generated translation files carry only the strings the site changed, so WordPress core plurals are no longer overridden.
• A parent theme's translation files are registered while a child theme is active.
• Translation files are imported on sites whose content folder is not directly under the WordPress folder.
• Translation files of a theme in an additional theme folder are recorded as the theme's, not as WordPress core files.
• A customization that only changes letter case, an accent or spacing regenerates the translation file.
• After translation files are rebuilt, a text domain whose customized translations all need updating gets its file back.
• Changing the language of strings regenerates the translation files of both languages, so each language's pages show the right text.
• Plugins that load translations before WPML sets the language, such as must-use plugins, get the page's language instead of the default.

Fixes in plural forms

• Every plural form of imported and customized strings is kept, and the form follows the language's plural rule.
• Plural strings use the language's plural rule everywhere in String Translation, and "0 items" no longer shows as "0 item" while translations load.
• Languages with three or more plural forms, such as Polish, get the right form for every number.
• Plural strings for zero or negative numbers use the plural form while translations load, as WordPress does.
• Text domains whose names differ only in letter case share one translation file and one plural rule.

Fixes in admin texts

• Showing the translated site title and tagline no longer costs database queries on every page.
• Admin texts stored as JSON are translated value by value instead of as one long string.
• No fatal error when a theme or plugin reads a translated admin text before WPML knows the language.
• Updating from 5.1.0 keeps a translated option's text in its own language and the file that serves it.
• Registering the first admin text on a site no longer writes an empty entry that runs extra code on every request.
• The translation files prompt also shows on Admin Texts Translation, and old Theme and plugins localization links open the theme and plugin scan.
• The translation files prompt links to the Admin Texts Translation page instead of a menu entry that no longer exists.

Fixes in Translate Everything

• Turning Translate Everything off while strings are translating no longer leaves them "Translation in progress" for good.
• Translate Everything no longer re-sends a job you cancelled during the first site-wide pass, so it is not charged twice.
• Translate Everything no longer sends and charges a taxonomy label twice when its status record is lost.
• A discarded failed automatic translation job stays discarded, and the strings pass no longer slows down on sites with many past batches.
• Admin texts registered for translation are sent by Translate Everything automatically, like every other string.
• Translate Everything's record of completed languages no longer grows with repeated entries, and stays accurate when a language is removed.
• Translate Everything no longer loses its progress record when two requests save its settings at the same time.
• Taxonomy labels that Translate Everything sends have their own row in the estimate.
• The setup wizard's estimate includes the category and tag fields each post's job carries.
• The setup wizard's estimate includes the taxonomy label strings sent right after setup.
• The setup wizard's estimate includes the string packages that the first pass sends on page-builder sites.
• The estimate row for block widgets is titled Widget and Widgets instead of Block.

Other fixes

• Translating or duplicating a post into several languages at once no longer saves a link to a custom post type with a translated slug in the wrong language.
• After you click Update Now, the "WPML needs to update the database" notice no longer returns on every admin page.
• The Elementor editor and other admin screens stay in your profile language instead of mixing in the page's language.
• A string registration batch interrupted by a server limit is set aside, and background registration stops while automatic string registration is off.
• Two admin requests at the same time no longer register the same string package twice.
• String package tables are created on sites set up through WP-CLI or REST, so saving posts logs no errors.
• Changing a string's language no longer leaves a translation in that same language behind.
• The String Translation screen no longer shows "No strings found" after you delete one domain's strings while others remain.
• The Translation Dashboard section for block widgets is titled Widgets again, not Block.
• Custom post type and taxonomy addresses with a translated slug, such as the Avada Portfolio, no longer return 404 errors.
• Translated WooCommerce Brands links and language switcher links no longer lead to 404 errors.
• WPML creates all its tables with one character set and collation.
• String Translation re-checks the strings table index until it is in place instead of remembering a failed check.
• WooCommerce Memberships "Ended" emails reach customers in their own language when sent in the background.
• The Translation Priority setting is removed.

• Fixed translation files of a language whose locale was changed keeping the default plural rule instead of the language's own.

• Fixed a fatal TypeError in String Translation (WP_Translation_Controller::set_locale() with a null locale) when a theme or plugin read a translated admin text before WPML's language was determined.

• The Elementor editor, and other admin screens, no longer show a mix of your profile language and the page's language: String Translation puts WordPress back on your language after it looks up a string in another language.
• The theme scan on Theme and plugins localization now writes a log line naming each file the theme loads from outside its folder, which the scan does not read, and says how to get those strings registered.

• After clicking Update Now in the "WPML needs to update the database" notice, the notice appeared again on every admin page. The update is now remembered and the notice goes away.

• Fixed the String Translation screen showing "No strings found" after deleting all strings of the filtered domain, although strings in other domains still exist.
• String Translation: the Translation Dashboard's section for block widgets is titled Widgets again, not Block.

• Fixed brand links and language switcher links that carried the URL base of the last request's language and led to a 404 when WooCommerce Brands are translated.

• String Translation: Theme and plugins localization lists must-use plugins as active with their text domain, and scanning a must-use plugin's loader file also scans the folder it loads
• String Translation: after you change the language of strings, the translation files are regenerated for the old and the new language, so each language's pages show the text meant for it
• String Translation: viewing the source of a string found in a must-use plugin's folder shows its file and line
• String Translation: on Theme and plugins localization, the 'No TextDomain' label of a theme or plugin without a Text Domain is no longer a link to an empty string list
• String Translation: text domains whose names differ only in letter case share one translation file with one plural rule, used both in the file and when choosing singular or plural, instead of the rule of whichever spelling rebuilt the file last
• Translate Everything's string pass no longer slows down on sites with many past string batches.
• String Translation no longer rebuilds the translated rewrite rules a second time on every page load when a theme or plugin registers post types late

• Plural strings now take the form the language's plural rule names in every String Translation path (for example "5 minut" in Polish), and "0 items" no longer shows as "0 item" while translations load.
• Sites that need String Translation's .mo files generated now see the prompt on the Admin Texts Translation page too, and old links to Theme and plugins localization open the theme and plugin scan.
• After the generated translation files are rebuilt, a text domain whose only customised translations need update gets its file back too.
• The .mo files prompt now sends you to the Admin Texts Translation page, with a link, instead of a menu entry WPML 5.x does not have.
• Translate Everything: admin texts registered for translation are sent automatically, like every other string.
• Admin texts stored as JSON are translated value by value instead of as one string.
• Fix: updating from 5.1.0 no longer removes a translated option's text in the string's own language, nor the generated file that served it
• String Translation: must-use plugins listed on Theme and plugins localization can be scanned for strings again
• String Translation, Media Translation, ACF Multilingual and BuddyPress Multilingual say which WPML version they need instead of failing on an older one
• String Translation: a string registration batch that a server limit interrupts is set aside instead of being retried in a loop, and the background registration no longer runs while automatic string registration is off

• String Translation re-checks the strings table index until it is in place, instead of remembering a failed check.
• String Translation: the notice about a broken strings table shows on the String Translation screen, not only on WPML → Support
• String Translation: plugins that load their translations before WPML sets the language (must-use plugins) now get the language of the page, not the site's default locale.
• String Translation: changing a string's language no longer leaves a translation in that same language behind; existing such rows are removed on update
• String Translation: the string-package tables are created on sites set up without the admin (WP-CLI, REST), so saving posts logs no missing-table error
• Performance: saving a post reads each of its string packages once
• String Translation: the theme scan works for themes whose stylesheet is in a subdirectory
• String Translation: the translation files of a parent theme are registered while a child theme is active
• String Translation: generated translation files carry only the strings the site changed; WordPress core plurals are no longer overridden by singular-only entries
• String Translation: custom post type and taxonomy URLs with a translated slug no longer return 404 in one language when the theme registers the type with a different slug per language (for example, the Avada Portfolio)
• String Translation: the site's languages are read once per request instead of once per plugin translation file, and a plugin's translation file is no longer loaded twice (slower uncached pages with many plugins since 5.1.0)
• String Translation: translation files of a theme in an additional theme directory are recorded as the theme's, not as WordPress core files
• String Translation: with a child theme active, the parent theme is listed as active on Theme and plugins localization
• String Translation: translation files are imported on sites whose content directory is not directly under the WordPress root
• String Translation keeps every plural form of imported and customised strings, and chooses the form the language's plural rule names
• String Translation: a customisation that changes only letter case, an accent or spacing regenerates the translation file

This release fixes removing strings by domain, the string filters and the status of string packages, and speeds up two checks that ran on every request.

Removing strings

• "Remove strings by domain" clears the whole domain: a lost batch is retried in smaller pieces, the screen says when the removal stopped, and strings whose automatic translation is in progress are left alone.
• Closing the "Remove strings by domain" dialog no longer forgets the domains you ticked.

String packages and word counts

• A string package's translation status reflects strings translated in String Translation or written by code.
• Packages synced from an automatic translation job no longer land in a "Manual Translations" batch.
• Package and string translations made without a job count as translated in the word quote and in the string lists.
• Word counts for strings match what the bill counts.

Also in this release

• "Check for string issues" filters the list again.
• Taxonomy labels are looked up with one query for all taxonomies instead of two per taxonomy on every admin page, and registering an unchanged string no longer looks up its language.

This release fixes a fatal error on hosts that disable a PHP function WPML relied on.

• Sites on hosts that disable PHP's getmypid() function no longer get a fatal error in wp-admin and on the front end after updating to WPML 5.0; String Translation writes its translation files again, so translated strings show as before.
• The download no longer includes .po translation source files; your translations are unaffected.

String Translation 5.0.0 focuses on a faster, more reliable Strings screen and translation queue, fixes taxonomy and slug translation, and makes string handling consistent on sites whose default language is a regional English variant.

Faster, more reliable string screen and queue

• The String Translation screen now loads faster because it uses an indexed lookup instead of scanning every string.
• Adding a new language no longer times out and only loads the translations you actually need for that language.
• Sites with a large number of auto-registered frontend strings no longer run into timeout errors while the queue is processed.
• String registration and the pending-strings queue are now more fault-tolerant, so a single bad file or database write no longer blocks every later string.
• The cache behind your site's translated language files now stays within a safe memory budget instead of growing without limit.

Taxonomy and slug translation fixes

• Translating a taxonomy's slug now actually takes effect on the front end.
• Taxonomy labels are now registered and shown under the correct source language, fixing labels that incorrectly appeared as translated.

Consistent behavior on English-variant sites

• String Translation now behaves consistently when your site's default language is a regional English variant such as en-US or en-GB.

Also in this release

• Searching strings by language name or text now returns results again.
• Uploading a .po file and adding the selected strings works again on the Strings tab.
• Changing a string's language now works correctly for non-admin Translation Managers, without a JavaScript error.
• String Translation now correctly scans themes and plugins when WPML is installed through a symbolic link.
• WPML now respects a custom REST API prefix instead of assuming the default one.

Security

• This release includes security hardening.

GUI Changes

• Moved String translation menu to WPML > Translation > String translation
• Adds support for WPML Multilingual CMS 5.0 admin UI changes

Fixes

• Improvements in handling string auto registration when same the page is visited concurrently.

New

• Ensures full WordPress 7.1 compatibility
• Extensive security hardening pass across WPML String translation

Fixes

• Removed an unused regex helper file that was causing false positives in some malware scanners.
• Cleaned up deprecation notices related to PHP 8.4 and 8.5.
• Removed leftover translation files that were no longer needed.

Improvements

• Removed unreliable file hash caching from String Translation scanner to prevent database corruption on large plugins.

Fixes

• Fixed an issue with date and time formats not being localized correctly for secondary languages.
• Fixed an issue with custom post type slugs not being translated correctly in sitemaps when using the "Use translation if available or fallback to default language" translation setting.

• 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.

• Added support for translating strings found in JavaScript files.

• 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.

• Reverted a change that was causing 504 Gateway Timeout errors when updating the String Translation plugin.

• 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.

• Added support for translating strings found in JavaScript files.

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

• 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_translate and *_icl_translation_status tables.
• Fixed a fatal error caused by an incorrect WPML core dependency.

• 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_translate and *_icl_translation_status tables.
• Fixed a fatal error caused by an incorrect WPML core dependency.

• [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

• 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.

• 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 issues reported during testing of WPML 4.7 Beta 2 version
• Updated interface translations for the WPML String Translation plugin

• 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

• 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.

• 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.

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").

Fixes

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

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.

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

• Avoid loading plugin translations before WordPress init hook. This causes warnings to be displayed on front-end and backend.

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

• Added PHP 8.3 compatibility
• Fixed various deprecated notices with PHP 8.x

• Fixed a broken access control vulnerability.

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.

• [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

• Added an effective way to query widget options
• Added a hook to support the WordPress Performant Translations plugin

• Fixed a compatibility issue with the MO file loader in WordPress 6.3 which was causing performance problems and missing translations on some environments.

• Fixed compatibility with WP 6.3 MO loader that was causing serious performance problems and missing translations on some environments.

• Fixed an endless translation loop in String Translation occuring on sites running both WordPress 6.3 and WooCommerce.

• Added more fixes for PHP 8 deprecations.
• Added a new string troubleshooting button to the Support Troubleshooting section.

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.

Fixes

• Resolved an issue with scanning strings which was related to PHP 8.1 compatibility.

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.

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.

• Fixed a fatal error that occurs when running WPML with WordPress version 6.1.

• Fixed a fatal error that occurs when running WPML with WordPress version 6.1.

• 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

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.

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.

Fixes

• Fixed a problem where the plugin update failed to finish.

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.

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.

• Added a small performance fix.

• 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.

Fixes

• Fixed issue with wp_localize_script in WordPress 5.7.
• Fixed error on String Translation page when string contains encoded HTML entities.

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.

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.

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.

Fixes

• Added sanitization of user inputs in GET and POST.

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.

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.

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.

• Handled the fatal error which appeared when an option's value has been changed from flat to nested value.

• Fixed corruption when saving options in a language different than the original.

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.

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.

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.

Fixes

• Fixed calls to deprecated jQuery functions.

Fixes

• Fixed unexpected checkbox behaviors due to jQuery changes in WP 5.5.

Fixes

• Fixed a potential security issue with select2.

Usability

• Fixed the translating of a string when its original language is changed.

• Fixed a parse error in PHP 5.6 due to reserved function name forEach.

Fixes

• Added a meaningful icon and tooltip when a translation is still being processed.

Compatibility

• Fixed incorrect processing of media shortcodes.

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.

• Handle gracefully the fatal error when JED files are generated.

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.

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.

Fixes

• Detect automatically if MO file from a domain should be pre-loaded.

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.

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.

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.

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.

• 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.

Compatibility

• Fixed an infinite loop error where the "override_load_textdomain" filter would always return "true", even if the MO object was not loaded.

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.

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.

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.

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.

• 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).

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.