WPML String Translation 5.3.0

Changelog

Requires WPML 5.3.0.

What's New

• Security hardening.

Performance

• With string auto-registration disabled, String Translation no longer watches every translated text and preloads theme strings on each request.
• Saving a page-builder page reads its strings once and no longer rewrites strings that did not change.
• Admin texts of very large options, such as Avada's theme settings, are read faster: only their registered keys are walked on the front end.
• In the admin-only string registration mode, visitor requests no longer run the registration work.
• Translated URL slugs are read with one batched query per request.
• Clearing the skipped translation files is one database update instead of one per file, so admin pages of large sites no longer hold the table.

Fixes in Translate Everything

• Strings left "in progress (automatic translation)" by an automatic translation that ended are released, also when automatic translation is off.

Fixes in Admin Texts

• An admin text registered while its value was empty, for example by an importer or on plugin activation, is translated on the front end once it gets a value.
• Translated date and time formats and other admin texts work again after the update to String Translation 5.2.0: the translation files that update removed are rebuilt once.

Fixes in Translation Files

• After a language's locale changes, its translation files keep the language's plural rule even when other pages load at the same moment.
• A language that still had an outdated locale from an old WPML version gets it corrected once and its translation files rebuilt, so its translated strings show on the front end again.
• A translation file that went missing, for example after a migration or a restore, is rebuilt on the next admin page instead of the front end showing the original text.
• Fixing links, converting absolute links and the other actions that change translations without a save now update the translation files too, so the front end shows the new translations.
• A text domain with capital letters, such as Widgets, stays translated after a plugin switches the locale and back.
• Custom translations of a plugin's or theme's own text domain apply again after updating, even with no native translation file.

Other Fixes

• The Strings tab links to the theme and plugin string scan.
• Page builder texts are saved when a translation is delivered through WP-CLI.
• The Widget and Widgets labels of block widgets in the Translation Dashboard are shown in your admin language.
• Images set in theme options, such as Blocksy's header and off-canvas logos, show their translated version for the first item of a list too.
• Saving a site option such as the site title in a secondary language with the original value no longer replaces that language's translation.
• Untranslated strings on a page an administrator views are registered even when another request is saving strings at the same moment.
• A translated shop or product category base saved with a leading slash stays in the URL rules, so translated category archives no longer show a 404 error.
• Users who can manage translations, not only administrators, can save translations of taxonomy labels.
• A translated slug base that is the same as another post type's or taxonomy's base no longer breaks that type's URLs, so product category archives no longer show a 404 error.
• Registering untranslated strings that an administrator sees while logged in no longer switches itself off two hours after setup, and sites where WPML 5.0 to 5.2 switched it off get it back once.
• No fatal error while String Translation updates: language pack translations are reloaded on the next admin page instead of during the update.
• A failed read of the stored String Translation settings no longer reruns upgrades or empties the MO scanning table.
• A text translated as part of a package shows where to translate it.
• String Translation works when WordPress loads it before WPML.

Need Help with This Release?

Ask a support question