Changelog
Requires WPML 5.4.0.
What's New
You can translate the archive slug of a custom post type.
- A custom post type archive with its own slug, such as ACF's "Custom slug for the Archive URL", can be translated. Its archive page, feed and language switcher use the translated slug.
Fixes for Problems that Started in 5.3.0
Plugin texts, the admin and the String Translation settings work again as before 5.3.0.
- Plugin texts on the front end show in the page's language again. After 5.3.0 they could show in English on every language.
- The admin no longer stops with a critical error after activating String Translation 5.3.0 when its database tables are missing. String Translation creates them on the next admin page.
- The "Detect strings in JavaScript files" setting can be switched off and saved again.
Translated Texts on the Site
Texts translated in String Translation show in the right language in more places.
- Emails sent by a shop manager whose profile language differs from the order language show String Translation texts in the order language.
- Texts in the next email or on the same page keep their language when another plugin, such as a PDF invoice plugin, loads translations during an email.
- An admin text registered while its value was empty, such as Yoast's front page description, shows translated on the front end once it has a value.
- Widget titles and text widget content registered again get the site's default language as source. On non-English sites they can be translated again.
- The wpml_translate_single_string hook returns the translation of a widget title.
- Saving the permalinks while the admin shows a secondary language no longer replaces Avada's original portfolio slug. Portfolio links in the default language no longer show "Page not found".
- Sites with thousands of taxonomies no longer log a "regular expression is too large" PHP warning, and texts that WPML must not translate stay excluded there.
Translation Jobs
Translation jobs keep your edits and declare the words that are really translated.
- A text you corrected in String Translation is kept when its page builder or ACF options page is sent for translation again without changes.
- A string that is only a URL counts no words, the same as in posts. The word count and estimate of a string job match what is translated.
- Saving a large Elementor page with many links no longer runs out of memory with String Translation active.
String Scanning and Import
Theme and plugin scans and .po imports record strings correctly.
- A theme or plugin scan keeps the "View in source" locations of every string, not only of the last ones found.
- Scanning JavaScript files for strings no longer fails, or breaks another plugin, when that plugin ships the same libraries. String Translation is about 6 MB smaller.
- On WordPress 7.2, importing a .po file keeps strings with double-quoted HTML attributes, such as links, intact. Their translations show on the site.
Updates and Error Logs
Updates finish and logs stay clean.
- Updating String Translation from 5.1 or older together with language packs no longer ends in a fatal error.
- The translation file rebuild after the update to 5.2.0 finishes on sites with hundreds of text domains. Admin pages are no longer about 20 seconds slower while it runs.
- On hosts where another plugin holds the database at the end of each request, such as some LiteSpeed setups, String Translation no longer logs four database errors per request.
- Reading the queue of untranslated strings no longer writes a "Failed to open stream" warning to debug.log when another request takes the queue at the same moment.
Performance
Pages, the admin and translation deliveries run fewer database queries.
- Admin texts, such as theme and plugin options, are translated several times faster on the front end of sites with many of them.
- With "Only strings viewed by administrators", visitors' page views no longer run database checks for the string queue.
- The Translation Dashboard reads the status of taxonomy label translations once, instead of once per taxonomy and language.
- Front-end pages of sites with thousands of string packages, such as one per translated post, are about 30 ms faster when the cache is empty.
- Each request reads String Translation's translation file caches with one query instead of two.
- Sites with translated product, category or tag URL bases no longer run extra queries on every request to find those bases' language.
- A translation delivery that saves many page builder jobs at once rebuilds each translation file once, not once per job.
- On sites that turn on translation memory, the Classic Translation Editor looks up all empty fields in one query instead of one per field.
Update or Download
The update is available to all WPML clients with an active subscription — it appears on the Plugins page in your WordPress admin within 24 hours of release. You can also check for it right away under PluginsAdd New PluginCommercial. To download and install manually, go to Downloads in your wpml.org account (see the installation instructions) and remember to update all components together without mixing versions.
