Every
release.

• The glossary now reaches what is already translated. Until now it only applied to translations made after saving it, so a term you fixed kept the old wording everywhere it had already been translated. When you change the glossary, the brand tone or formal/informal, Settings tells you how many saved translations use what changed and offers to translate them again. Nothing is sent without you asking: translating again counts against the characters of your license.
• Translations you reviewed by hand are never redone, and the site keeps showing the current text until each new translation arrives — no page falls back to the source language meanwhile.

• Edit translations shows where each text is. The page marked only about one text in ten — the rest are in a closed menu, hidden, or an attribute such as alt — so it looked as if nothing happened. The mark now goes only to what you can see, a text you can’t see says Not visible next to its status, and the mark stays while you look at the page with the field still selected.
• The editor title looks right on Breakdance sites. It took the site’s heading style — huge, in capitals, dark on the dark header.
• The language suggestion bar shows the flag. It showed a globe; now it shows the language’s flag, drawn the same on Windows and Mac, when Flags is on in the switcher.

• The sitemap shows the translated addresses right away. With Rank Math or Yoast SEO, turning on Translated addresses left the old addresses in the sitemap for up to 100 days, each one a redirect in Search Console. The sitemap is now refreshed whenever the addresses change, and once when you update.

• Translated addresses. Every address can be in the reader’s language — pages, posts, products, categories, custom post types and taxonomies, their bases and the WooCommerce endpoints (/en/product/linen-blouse/, /de/mein-konto/bestellungen/), turned on in Settings → Translated addresses — on by default on new installs. The old addresses redirect (301) to the new ones, an address never changes on its own, and each one can be edited in the new Addresses tab.
• Close languages get a real translation. Between languages as close as Portuguese and Italian, a short text could come back unchanged, as if it were already translated.
• Password reset works in every language. On a translated page, the WooCommerce reset link sent the customer back to “Lost your password?” instead of the form for the new password.
• The home page gets its languages in the Rank Math sitemap. It was the only page there without its translated versions and hreflang.
• The order received page stays in the customer’s language. After an order placed on /en/ with bank transfer, the customer was sent to the order received page in the source language, at an address with two slashes.

• The Edit translations panel scrolls again with smooth-scrolling themes. On themes that use smooth scrolling (Lenis), the mouse wheel over the panel scrolled the page behind it instead of the list of texts. The list now scrolls, and reaching its end no longer moves the page.

• New languages start as drafts. A language added in Languages is translated right away, but only administrators can open it, and it stays out of the switcher, the hreflang tags and the sitemap until its translation is complete — then it goes live by itself. Google no longer indexes pages that are half translated, for instance when a free trial ends halfway. Visitors who open a draft address go to the same page in the source language. The languages you already have stay published.
• Each language in Languages has a Published / Draft choice and a Preview link. Publishing or unpublishing clears the page cache, since every page lists the languages.
• Every section of the panel has the same header: the dark band the License card already had.
• Structured data in the visitor’s language. The JSON-LD that Google reads — the product name and description, the breadcrumb, the page title, from WooCommerce and the SEO plugins — stayed in the source language on translated pages, so a search result could show a product in Portuguese on the English site. It now uses the same translations as the page, and its addresses point to the translated pages. It uses no characters.
• Flags that show on Windows. The switcher’s flags were emoji, and Windows has no flag emoji: it showed the letters PT instead. They are now drawn inside the page, only for the languages you have, and look the same on every system — still with no images and no extra requests. The System box keeps the emoji, since an option can only hold text.
• Database changes arrive with the update. The plugin’s tables were only created or changed when the plugin was activated, and an update does not activate it again. Now each site brings its tables up to date the first time it loads a new version. On a multisite network, sites other than the main one get their tables too — before, they had none.
• You hear about it when translation stops. Before, running out of characters or a refused license only showed on the plugin’s Dashboard, and new products stayed in the source language without anyone knowing. Now a notice appears at the top of the WordPress admin while translation is stopped, and the site’s admin email gets one email — not one every hour. With less than 10% of the plan left, a notice shows on the Dashboard and Plugins screens, and one email is sent.
• Formal or informal, per language. Settings has a new Per language table: choose Sie or du for German, vous or tu for French, usted or tú for Spanish, and every translation in that language uses it. Before, the same page could mix both. Each language also gets its own glossary, for translations that only fit that language. With nothing chosen, translation works as before.
• Better translations of short texts. Buttons, menu items, headings and shipping methods are now translated knowing where they appear, so Início in a menu becomes Home, not Start, and menus and buttons keep the capitalization of the original instead of English Title Case. The translation also knows your site’s name and tagline (Settings → General), instead of treating every site as a store. It uses no extra characters.
• Translations into English (United States) now say which English they are, as the other languages already did: product words come out American (sweater, pants), not British (jumper, trousers).
• Keep a block in the original language, without code. In the block editor, write notranslate under Advanced → Additional CSS class(es), and that block — with everything inside it — is never translated. Page builders work the same, in their CSS class field. Before, it took the translate="no" attribute, typed into the HTML. Text that already has the notranslate class, which Google Translate also respects, now stays in the original language too.
• The switcher as a block and as a menu item. In block themes, add the Language Switcher block to the header — also inside a Navigation block, next to its links — or anywhere in a page. Its sidebar picks the shape, name or code, and flags, or follows the Switcher tab. In classic themes, Appearance → Menus has a Language switcher box: the item becomes one link per language, drawn by the theme like the other items, with the other languages in a submenu when the shape is Menu. Either way, the floating switcher steps aside on that page. Before, it took the shortcode or PHP.
• The Menu shape no longer stretches across the page when it is placed in content: the button is as wide as the language name.
• Edit translations on the page itself. Logged in as an administrator, pick Edit translations in the toolbar of any page, and a language. A panel next to the page lists that page’s texts in the order they appear: the original above, the translation below. Point at one and the page shows where it is; change it, press Save, and the page updates straight away. It works for draft languages too. Before, fixing a translation meant finding it among all the site’s texts in Strings.
• A translation typed by hand with an ampersand (&) showed a code on the page instead of it. It now shows as typed.
• Visitors see your corrections. A translation fixed by hand, in Strings or on the page, now clears the page cache a minute later. Before, you saw the fix — logged-in users skip the cache — while visitors kept the old translation until the cache expired.
• Text from page builders, custom fields and custom tabs. Pages and products made with Elementor, Breakdance, Oxygen, Bricks or any other builder, fields from ACF and similar plugins, and custom product tabs keep their text outside the fields the plugin reads from the database. That text stayed in the source language, with no warning, unless the page was one of the few the weekly check opens. Now the plugin also reads the page itself: after you save, and when someone opens a translated page with text it has not read yet. It works the same with any builder. Two saves in a row — a typo fixed right away — are read once, a few seconds after the last one.
• The plan cards in License show the current prices: Starter $9, Pro $19 and Agency $49 a month, or $90, $190 and $490 a year. If you already subscribe, you keep the price you have.

Added

• FlyingPress support. When new translations arrive, the plugin now clears the FlyingPress cache of the translated pages, as it already did for LiteSpeed Cache, WP Rocket and W3 Total Cache. Visitors see the new translation right away instead of waiting for the cache to expire.

Fixed

• The plugin stays active after an update. On some servers WordPress deactivated the plugin right after updating it, even with the files in place, and the translated pages returned “not found” until someone activated it again. The plugin now puts itself back on the list of active plugins when WordPress removes it silently and its files are fine. Deactivating it by hand works as before.