WPML

Changelog

What's New

  • WPMLSupport has a new tool, "Translated terms that show the original name". It finds categories, tags and attributes WPML copied without translating, and sends them for translation.
  • Plugins can keep their string packages out of Translate Everything with the new filter wpml_exclude_packages_from_auto_translate. WPForms Multilingual uses it for trashed forms.
  • Block themes: the Site Editor warns, on a translated template, template part, menu or page, that edits made there are lost at the next translation update.
  • Elementor: fields that another plugin adds to sections and columns can be translated when that plugin's language configuration declares them.
  • More texts of WordPress core blocks reach translation: embed captions, Tabs and Icon labels, post navigation and read-more labels, social link labels, cover image alt texts and button tooltips.
  • In the WPMLSettings languages editor, you can now drag languages into the order the language switcher shows. Adding or removing languages keeps that order.
  • New WP-CLI command wp wpml config reload reads every wpml-config.xml file again. WP-CLI and cron requests now also pick up a file a deployment changed.
  • On a subdomain multisite network, WPML refuses a language domain that belongs to another sub-site and warns when a sub-site's address is a language domain.
  • Post lists have two new bulk actions: "Translate independently" for duplicated translations, and "Overwrite with <default language> content" for regular translations.
  • WPMLSupport now shows whether WPML's template cache is on, and why it is off.

Fixes for Problems that Started in 5.3.0

Fixes for problems that WPML 5.3.0 introduced, in one place so you can find them.

  • Sending many pages at once no longer loses translations that the translation system finished while the send was still running.
  • A finished translation that your site fails to save is reported once, with Resend, instead of staying in progress after every redelivery.
  • A translation your site could not download can now be delivered with Retry in WPMLSupport.
  • When your site cannot confirm a received translation, it tries again. The translation system no longer closes that translation as not needed.
  • A translation collected during a visitor's page view now links to the translated pages, not to the default-language pages.
  • Translate Everything no longer refuses a category or tag whose translation keeps the original name with "already used by another term in this language", also when its slug has a dot, a slash or an apostrophe. Terms refused this way are sent again.
  • WPMLSupport tells a moved or copied site, or one whose access key was removed, to register again. It no longer says to wait while showing "All good".
  • The Translation delivery box asks for payment after a declined final charge, instead of asking for more words. It also says that Retry charges the words again.
  • For a failed translation, the card in WPMLSupport says what Report opens when support does not have the details yet.
  • Sending content for translation no longer fails with "send not confirmed" on sites whose translations table has a damaged row. WPML now replaces the row.
  • Block themes: the default language no longer shows another language's header and footer, and the Site Editor no longer lists template parts twice.
  • Elementor: WPML no longer repeats a refused Site Settings step on every admin request or starts duplicate background tasks, which kept the Elementor editor from loading on some sites.
  • Avada: on sites without String Translation, admin requests such as autosave and heartbeat no longer end in a fatal error.
  • Avada One: portfolio items with a translated portfolio base open in every language instead of showing "Page not found". Sites that WPML 5.3.0 already affected are repaired without saving the permalinks again.
  • Unlimited Elements: listing cards built with an Elementor loop template keep the template's design in every language.
  • Divi 4: Theme Builder layouts made per language before WPML 5.2 show per language again. The update, and WPMLSupportRepair Divi Theme Builder, link them as translations.
  • The database indexes that WPML 5.3.0 adds are now also added on MyISAM tables, instead of failing with "ALGORITHM=INPLACE is not supported".
  • The WPMLSupport repair for links rewritten to ?page_id= addresses now fixes them in their common shapes, including large page builder blocks, and counts the links it leaves.
  • The update of WPML's internal link records that started with 5.3.0 now continues in the background when nobody is in wp-admin. WPML's screens show its progress.

Automatic Translation and Translate Everything

Translate Everything translates what you chose, and stops cleanly when you turn it off.

  • Translate Everything no longer creates jobs without end for content it cannot match to its translations, such as ACF field groups. This filled the database and slowed saves.
  • Turning Translate Everything off on a large site cancels every job at the translation system in the background, instead of timing out and leaving jobs open.
  • The Translate Everything switch says that turning it off cancels and refunds translations in progress, and that turning it on again sends changed pages.
  • Adding a language with Translate Everything on follows each post type's setting. Category and tag names are translated only for post types you chose to translate.
  • Terms that WPML creates as copies of the original, for example when duplicating a post, now count as not translated. Translate Everything translates them.
  • Category and tag jobs whose send failed are retried like posts. Translations shown as in progress with no job behind them are sent again.
  • When a copy of your site gets its own translation account, WPML turns Translate Everything off on the copy and tells you why.
  • Shortcodes declared in wpml-config.xml stay protected in every automatic translation, including sends from WP-Cron, the REST API and WP-CLI.
  • A post translation skips a category or tag whose translated name is longer than 200 characters, and tells you why.
  • When you change the default language, WPML removes language mappings onto it, so no language is translated into itself.
  • The Languages screen shows Kurdish (Sorani) as supported by PTC, without asking you to map it.
  • With Translate Everything on, saving and deleting a post in the same request no longer ends in a fatal error.
  • The "Your automatic translation pricing has been upgraded" notice on the WordPress Dashboard has a "Don't show again" button.
  • Retrying a waiting automatic translation cancels it when its content type is no longer translated automatically, instead of sending it as a manual job while WPML still shows it waiting.
  • Translate Everything sends updates when you edit an original of a type set to "display as translated".

Words and Charges for Automatic Translation

You pay for the words that need translating, once.

  • Saving a page whose translation is finished but not yet collected saves that translation first and sends only your change. You no longer pay for the page twice.
  • Categories and tags are charged by the same rules as posts, so the Translation Dashboard's estimate and the charge agree.
  • Two quick clicks on "+" for the same page and language create one job, not two.
  • Word counts match each job's content when one post goes to several languages at once, and after a send from the editor failed.
  • Sending a page-builder page again no longer counts texts already translated in String Translation, so you are not charged for them again.
  • When part of a translated field changes, WPML sends its unchanged sentences with their existing translation, and only the changed sentences as new text.

Delivery of Finished Translations

Finished translations reach your site, and jobs you no longer need are closed.

  • Finished translations that your site stopped asking for are now delivered, or closed at the translation system when they are no longer needed.
  • Sites with a large backlog collect finished translations faster: each check asks for 200 translations instead of 50.
  • When a page is sent again, its old job is closed at the translation system, also on sites where nobody opens the WordPress admin.
  • Translations that WPML 5.3.0 or older gave up after download errors are delivered by the first check after the update.
  • When a delivered translation cannot be saved, the error says why, instead of "The uploaded xliff file doesn't belong to this system".
  • After a glossary change, the Translation Dashboard's progress message ends within two hours. If the improvements could not be applied, it says to send the pages again.
  • Permanently deleting a post also cancels its open manual jobs in the Advanced Translation Editor.
  • When saving a delivered translation fails, the cause is also written to the server's PHP error log.

Translation Jobs and the Advanced Translation Editor

Jobs open with their content, and the jobs list says what is really happening.

  • The Advanced Translation Editor no longer opens every job empty when a plugin allows an HTML tag with an unusual name.
  • Opening a finished translation for editing works when the translation system cannot copy its job. WPML opens a new job instead of "WPML didn't manage to translate this page".
  • The Advanced Translation Editor no longer opens empty for a translation whose later automatic job was cancelled.
  • Translators can open and review automatically translated category and tag jobs, not only managers.
  • Existing translations of posts with links, images or bold text show as suggestions paragraph by paragraph, instead of being dropped for the whole body.
  • WPML's own data-wpml attributes no longer show up in translated pages.
  • Clicking "+" in the posts list of a secondary language translates from that language, not from the original.
  • Jobs waiting for an automatic retry can be cancelled from the Translation Jobs list.
  • A retry blocked while WPML reconnects no longer counts as a failed try. A job that keeps failing shows "Failed – needs attention" with its error.
  • With Translate Everything off, a job that waits for you reads "Waiting for you" in the jobs list, instead of promising an automatic retry.
  • XLIFF export on a host without zlib skips the jobs it cannot read, exports the rest, and lists the skipped jobs.

Connection to Our Translation System

Your site stays registered and the Translation Dashboard keeps working through short outages.

  • A site that lost its access keys for automatic translation registers again from any admin page, not only when it sends a job.
  • The Translation Dashboard no longer fails with "503 Service Unavailable" after one slow answer, on sites that route it through WPML.
  • When the connection comes back, the Translation Dashboard reads again what it missed, so Translate Everything can start without a page reload.

Registration, Updates and Support

Updates finish on more servers, and setup cannot be undone by accident.

  • A site key refused by an automatic check stays saved and flagged. Only Refresh license removes it, so one wrong address no longer unregisters the site.
  • One failing update step no longer stops the others. A plugin that runs code when a term is deleted no longer causes a fatal error during the update.
  • Database updates now succeed on MyISAM tables that hold empty dates, without turning off the server's strict modes.
  • When the database refuses to create a table during activation, the error names the table and the database's reason.
  • A page request that started before the setup wizard finished can no longer reset the finished setup.

Elementor

Translated Elementor pages keep their forms, popups, styles and display conditions in every language.

  • Forms in popups, headers and footers send the visitor's language, not the first visitor's language after a cache clear. The Pro Search widget searches in the current language.
  • The Elementor editor works in the language of the page you open, not in the language last picked in the admin bar.
  • With "Translate raw HTML" off, automatic translation keeps the scripts and embeds of HTML widgets on the translated page.
  • A template, global widget or popup whose translation is not published yet shows the original instead of an empty space. Maintenance mode does the same for its template.
  • Display conditions work on translated pages: Page Title and Post Title conditions, and the post, page and category conditions of Elementor V4 elements.
  • Elementor V4: translated and duplicated pages show the original's style changes without a manual cache clear.
  • Elementor V4: buttons and links with Open Popup or an internal link open the translated popup or page.
  • Elementor V4: Heading and Paragraph texts reach translation even when WPML's downloaded Elementor configuration is missing. Images in V4 components offer their alt text.
  • Page, popup and template settings follow the original after each update, and their images and links point to the translated ones.
  • Forms: email subjects of Elementor Pro 4.4 V4 forms show the visitor's answers, not field codes. Email messages translated in the Classic Translation Editor keep their line breaks.
  • Menu Anchor links work on pages translated into Arabic, Hebrew, Japanese and other non-Latin languages.
  • A Text Editor widget whose dynamic tag Elementor no longer knows, for example after Elementor Pro is deactivated, sends its text to translation.
  • Posts widgets and other lists of "display as translated" posts filtered by a category with no translation show their posts again in other languages.
  • Content imported with Elementor, such as Website Templates, Cloud Library templates and AI drafts, gets your site's default language. WPML shows a notice naming it.

Divi

Divi pages, global modules and Theme Builder layouts save, show and translate correctly in every language.

  • Divi 5: edits to a translation or Theme Builder layout made in the Visual Builder, page manager or Divi AI agent survive the next translation update.
  • Divi 5: the Visual Builder saves a default-language page when the admin is in another language and a Theme Builder layout is translated.
  • Divi 5: section ids and other custom attributes keep their original values, so anchor links work. Only attributes visitors read, such as title, alt and aria-label, go to translation.
  • Divi 5: a global module whose translation is a draft shows the original on the page and in the Visual Builder. Content loaded with AJAX shows the translated module.
  • Divi 5: the Search module searches in the page's language on sites with the language as a URL parameter. The backend builder notice no longer shows on Divi 5.

Blocks, Block Themes and the Site Editor

More block texts reach translation, and translated templates, menus and patterns show what you expect.

  • Synced patterns: a page's customized button text and link, image alt, title and caption are translated with the page. An unsynced pattern's translation stays unsynced.
  • Block themes: a template or template part translated automatically no longer gets a "-2" slug, so translated pages use the translated template.
  • Navigation block: a visit to a language with no translated menu no longer creates a stray menu. Visitors see your menu with links to their language.
  • Block themes: updating from WPML 5.1 or older no longer brings back older or English copies of translated templates, template parts and menus.
  • Navigation block: links inside a submenu point to the translated page and highlight the current page.
  • Blocks that contain other blocks keep their translation when their text has quotes, ellipses or curly apostrophes.
  • Custom blocks with no WPML configuration no longer send colors, spacing, bindings or ids to the translator, and empty wrapper blocks add no strings.
  • Stackable: block CSS no longer shows as text on translated pages, and it no longer reaches the translator or counts as words.
  • After a page changes, the Advanced Translation Editor no longer puts one block's earlier translation into another block's segment.
  • Translation editors: the picture next to a block's alt text is the block's own image, and block labels from wpml-config.xml show as written.
  • Block editor: the Language panel follows a synced pattern edited with "Edit original", and WPML notices can be dismissed on WordPress 7.2.
  • Greyd Suite and other blocks: URL-encoded text in a block attribute is offered for translation, instead of turning into "null" in translations.

All Page Builders

Fixes that apply to every page builder WPML supports.

  • The setting "Send to translation the content of raw HTML cells" now works in the block editor, Beaver Builder, Elementor, Divi, Avada and Cornerstone.
  • Apostrophes in translated headings and buttons of shortcode builders, such as Divi, WPBakery and Avada, no longer show as codes like "&#039;".
  • A draft translation of a builder page written by automatic translation gets the translated images.
  • A long post pasted from Word, with a linked image shortcode as in Flatsome, sends its full text to translation again.
  • Saving an original built with a page builder no longer replaces a translation's own content with the original's text.
  • Updating a page no longer stops with the fatal error "Argument ID must be numeric" on sites whose database gives revisions no ID.

Other Page Builders and Themes

Cornerstone, Avada, WPBakery and other builders translate more of their content.

  • Cornerstone: headers, footers, layouts and components can be translated on every site with no setting. With the X and Pro themes, so can the logo text and shop titles.
  • Cornerstone: rich text parameters of components reach the translation editor.
  • Cornerstone: a header translated automatically keeps its content and links when the site refuses unfiltered HTML. Dynamic content links keep working.
  • Cornerstone: other plugins that ask for the posts of all languages get them again.
  • Avada: the "This post is also available in" links show once, not again in headers, footers and other layout sections.
  • Avada: the dynamic texts of an icon, with their before, after and fallback texts, show as separate texts in the translation editor.
  • WPBakery 9: Single Image and Image Gallery use the translated image, and each image's custom link can be translated.
  • Beaver Builder: a Button set to open a Lightbox no longer sends its hidden link to translation, and the lightbox's HTML can be translated.
  • Enfold: a button that links to the same page as an earlier image no longer gets the URL added to its translated label.
  • SiteOrigin: content inside a Layout widget in a Layout Block reaches the translation job and the translated page.

Translation Dashboard and Translation Editors

Translation jobs carry all their text, and the Dashboard and editors show what is really happening.

  • Text saved with old Latin-1 characters reaches the Advanced Translation Editor with its letters, instead of an empty field.
  • Resend in the box of jobs that could not be completed sends each item only to the languages listed for it. Finished translations are no longer translated and charged again.
  • Reopening a Classic Translation Editor job in progress, after the original changed, keeps the translator's saved drafts and the assigned translator.
  • After a Resend and a cancel, the pencil icon opens the existing translation instead of the cancelled job.
  • Translators get translation memory suggestions in the Classic Translation Editor again, instead of an "Insufficient permissions" error.
  • When Sticky Links is not active, a relative internal link stays relative in the translation when its target is translated.
  • The allow-translatable-job-fields rule in wpml-config.xml now also applies to jobs created through the REST API, WP-CLI and scheduled tasks.
  • When a translation was already started in another tab, its "+" link is refused with a notice. It no longer takes the language away from the first translation.
  • The classic Language box no longer offers "Connect with translations" while a translation job of the page is still on its way.
  • In the Posts and Pages lists, a duplicated translation shows the duplicate icon, and a trashed translation with an open job shows the trash icon.
  • With no automatic translation engine on, WPMLLanguages and the Translation Dashboard say so, instead of a connection error or a language mapping prompt.
  • "Show all selected items" in the Translation Dashboard also reveals taxonomies its filter hides. A search for a title with a backslash works on MySQL 5.7.
  • The translation jobs list no longer ends in a database error when filtered by type. WPML restores a missing translation status column instead of showing a blank screen.
  • The Classic Translation Editor wraps field labels between words, not inside a word.
  • The daily and weekly translation summary emails now say how to stop receiving them.
  • When the translation service improves translations your site already received, WPMLTranslations lists them in an Updated translations tab. You apply or skip them per page or all at once, at no cost.

Languages, URLs and the Language Switcher

Language links point to the right address, and language names and admin languages are right.

  • When a language's URL code differs from its stored code, such as /en/ for en-us, the language switcher keeps /en/ on that language's own pages. Visitors no longer get "Page not found".
  • With LearnDash nested URLs on, links to lessons and topics open in translated languages instead of redirecting to the course.
  • With the language as a URL parameter, page links of archives that combine tags keep the "+" and no longer lead to "Page not found".
  • Saving a translated post in the block editor gives other plugins, such as cache plugins, links in the right language.
  • In REST requests sent from the post edit screen, links in shortcodes now follow the language of the content, not the language of the edit screen.
  • The language in your WordPress profile now sets your admin language, even when an older WPML admin language setting is still stored.
  • WPML no longer logs "Unknown column 'wp_code'" database errors after an update. It adds the missing column to its language presets table.
  • Slovak is named correctly in the 19 admin languages that called it "Slavic", such as "Slavo" in Italian. Existing sites are corrected on update.

Menus, terms and WP-CLI commands act on the item you name, in the right language.

  • WP-CLI commands that delete a menu, update a term or update a menu item now act on the translated menu or term you name, not the default-language one.
  • Saving a menu no longer removes an item that links to a term of a taxonomy WPML does not translate.
  • When two taxonomies share a term, such as two WooCommerce product attributes, WPML returns the translation from the taxonomy you asked for.
  • With a persistent object cache, checking a post's category in one language no longer stores that language's terms for the post's other languages.
  • With an Elementor Pro single post template and Yoast SEO, translated posts keep their primary category in the URL.

Custom Fields and Settings

Custom field values reach translations as set, and WPML's settings stay intact.

  • A copied custom field whose value holds a backslash now updates on the translation, instead of adding a new row on every change.
  • A Pods File or relationship field copied to a translation now shows its files and items in the editor and on the site.
  • When the custom field preferences table is missing, WPML creates it again instead of logging a database error on every request.
  • The Custom Fields Translation notice no longer presents fields from an old, unfinished check as a change to your settings.
  • A compatibility configuration update that needs a newer WPML no longer reaches sites that run an older version.
  • Two background tasks no longer run the same step twice when a second admin screen opens.

Multisite

Sub-sites that do not use WPML yet work as they should.

  • A sub-site where WPML is active but not set up no longer shows "Page not found" on its front page when a plugin such as BuddyPress switches sites.

Compatibility with Other Plugins

Caching, forum and events plugins keep the right language.

  • With The Events Calendar, the calendar's navigation (Today, the arrows, Previous Events and Next Events) stays in the page's language, also for visitors who used the language switcher in the admin.
  • LiteSpeed Cache: with a different domain per language, combined CSS and JS files load from each language's own domain.
  • bbPress: with the language as a URL parameter, user profile links, pagination, reply links and the language switcher open the right page.

Other Fixes

Fewer conflicts with other plugins and fewer errors in the background.

  • WPML's Ant Design styles apply only on WPML's own screens and no longer change other plugins' blocks and screens.
  • WPML's settings pages no longer change other plugins' admin pages that use a section parameter in their address.
  • XLIFF export no longer ends in a fatal error on servers without PHP's mbstring extension.
  • Saving a translation updates the links in the other translations of the same original again, without an error in the log.
  • The translation status icons that other plugins, such as WCFM, use are back in the WPML package.
  • WPML's newer database tables are now created on servers where InnoDB is turned off.

Performance

Admin pages, the front end and large sites do less work.

  • While your site cannot reach the translation system, admin pages no longer rewrite about 150 KB of log data on every load.
  • Front end: image captions, post lists and Avada global elements read their translations in batches. Shortcode ID settings are read once per page.
  • Category archives and menus no longer run one database query per term on sites with older split terms.
  • On large sites, the background task that records which media posts use runs each batch faster.
  • Saving a post on a site with thousands of translatable custom fields no longer takes minutes. WPML checks the translations' status once per save.
  • On sites with many tags, the Translation Dashboard keeps its taxonomy counts between loads, and the Posts list and tag screens load much faster.
  • Category lists, such as the WooCommerce product categories widget, read their terms' translations in one query. So does the Categories screen for default categories.
  • Pages in a secondary language read the language of all sticky posts in one query, not one per post.
  • Every wp-admin page runs fewer queries: WPML reads more of its options at startup, and reads its flags, task locks and update list once.
  • WPML's settings are no longer loaded twice on every request, and the Translation Dashboard no longer saves the settings on every load.
  • With Redis or Memcached, links already in the page's language no longer cost an object cache lookup each.
  • A page view no longer waits up to a second for WPML's URL cache to update.
  • Multisite: a sub-site request that switches to another site and back loads the languages once, with fewer database checks.
  • When refreshing the list of translation services fails during an update, WPML waits a day before trying again, not every admin page.
  • The Languages settings page reads the language names once.

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.

Need Help with This Release?

Ask a support question