PerfLocale

Changelog

Each release below is a short summary. The complete notes for every
version, with the reasoning behind each change, live at
perflocale.com/changelog

1.0.7

Security hardening.

Languages: a language that still has posts, pages or products outside the Trash can no longer be deleted; the Languages screen, the REST API (409 language_has_content) and WP-CLI say what it still has. Move that content to the Trash first, or deactivate the language instead. Terms, media and block theme template copies do not block a delete.

Export and import: a Merge import no longer changes this site’s settings, add-on settings, add-on list or roles; it reports them as not applied. Replace applies them, and a file with only the Settings and Roles sections deletes no rows.

Sync Fields: copying a field to the other language versions changes only that field; their content, title, excerpt, publish date and status stay exactly as they are, whoever saves.

Custom fields: ACF, Meta Box and SEO values stay correct however a post is saved (editor, REST API, WP-CLI, WooCommerce saves from code), including nested groups, repeaters and flexible content. A field a translator empties stays empty. Field changes made during a front-end page view are copied to translations on the next save, and on multisite each site follows its own Sync Fields setting.

WooCommerce: language copies of a product share one stock at checkout, in the cart and when adding to the cart, including stock held by pending orders. Saving a product no longer overwrites the stock of a copy that manages its own stock, so a sale made during the save is never lost. New product translations get the source’s catalog visibility, featured flag, shipping class and brand, and on WooCommerce 10.8 or newer their product lookup row, so they sort by price and are found by SKU; on older versions, and for translations created before this update, WooCommerce → Status → Tools → Product lookup tables → Regenerate builds the missing rows. Shop managers can create product translations. The block Cart and Checkout show product names, short descriptions and images in the page language from the first view, order line names no longer start with “Protected:”, and a sold-individually product cannot be bought twice as two language copies. Every order is tagged with its language whenever the WooCommerce add-on is active, and an order without a language that is paid on a translated order-pay page takes that page’s language, so its emails use it. Each order email keeps its own language and exchange rate, and an order’s personal-data export includes its language.

Machine translation: the WordPress AI Client prefers small models (filterable), and its error message, Site Health and the editor’s setup link point to Settings → Connectors when no provider is ready. A password-protected post is sent to a machine translation service only when someone picks that post (in the editor, with a bulk action on selected rows, or by its ID); automatic runs and wp perflocale translate –all skip it. The new perflocale/mt/send_password_protected filter can change this for any run. In the block editor, “Fill in from source” fills each block’s own text, and blocks marked “Do not translate” are kept; a block inside one shows why it cannot be translated. Bulk and site-wide translation say how many new translations kept the source content because of “Do not translate”, on the Translations screen and the Jobs page. Bulk string translation selects only strings still missing a translation, fills every plural form, and says how many remain. Product translation also covers variation descriptions and local attribute options. A machine translation server on a private network (for example a self-hosted LibreTranslate) must be listed with the perflocale/mt/trusted_hosts filter.

Background jobs: bulk translation jobs run in slices of up to 20 seconds or 500 pairs and continue where they stopped, so hosts that stop long requests no longer kill them. A job that stops on a PHP fatal error is marked failed at once, and a killed worker no longer holds up the Action Scheduler queue (WooCommerce included) once its lock expires.

Importers: WPML, Polylang and TranslatePress imports run one at a time, refuse a first import when the default language differs or a language is missing (a later catch-up import shows a warning instead), and bring menus, strings and order languages. The TranslatePress import brings full post data and WooCommerce order languages, replaces only the whole texts, attributes, block settings and translation blocks that TranslatePress translated, and reports translations it skipped. The Jobs page shows each import’s current stage and how many of its items are done, and a background import whose worker stopped can be started again after 15 minutes. The WPML importer reports conflicting translation sets instead of relinking them, and large imports and interrupted background jobs are handled reliably; an import that loses its lock stops with a message instead of continuing. Bulk tools ask before running on data that has not been imported yet.

URLs and redirects: with the language cookie turned off, the browser-language, GeoIP and edge-hint redirects no longer run, so the default language stays reachable; otherwise they redirect only to a page that shows content in that language. Domain mode serves a default language without a domain of its own on the site’s own host. Fallback chains work in subdomain and domain mode.

Translations screen: the status filters, the Dashboard and wp perflocale status take each translation’s status from its own post, so a translation in the Trash counts as missing.

Block themes: customising a template part again after “Reset to theme default” brings its translations back, and a Navigation block without a chosen menu shows the default-language menu or its translation.

Strings: in files mode, translation files are rebuilt when languages change, and Site Health names each language without files.

Roles: changes a site owner makes to the Translator role are kept across updates and reactivation.

Multisite: network activation is refused, listing the IDs of the sites that failed, when any site cannot be set up.

New filters: perflocale/language_cookie/enabled decides per request whether the language cookie is written (consent still comes first), and perflocale/addon/enabled turns an add-on off or on per request; perflocale()->is_addon_active() tells whether it runs. Also perflocale/mt/send_password_protected, perflocale/jobs/bulk_translate/slice_seconds and perflocale/jobs/bulk_translate/slice_max_pairs, perflocale/roles/translator_caps, perflocale/roles/shop_manager_caps and perflocale/sync/seed_meta_value.

Changing an existing post’s language (on its edit screen, in Quick Edit or with WP-CLI) swaps its categories, tags and other translatable terms for their translations in the new language; a term without one is kept.

Also fixes hreflang tags on page 2 and later of a listing pointing to pages that do not exist in another language, force-deleting a translation leaving its siblings’ hreflang tags pointing to it, page 2 and later and the feeds of translated term archives redirecting to page 1, redirects to another language’s domain in domain and subdomain URL mode, posts without a translation link (shown on their own URL, with hreflang tags), unknown two-segment URLs loading the front page, a settings tab saved without changes resetting settings it does not show, the per-language domain table showing in subdomain mode, wp perflocale languages delete reporting success for a delete that was rolled back, excluded paths matching part of a path segment or missing non-Latin paths, custom fields such as book_author, whose names hold a credential word inside a longer word, not being copied into a new translation, uninstall with “Delete all plugin data” leaving WooCommerce order data (including High-Performance Order Storage) and scheduled actions behind, a server error from an unusual post_type query parameter, deleting a language with an empty code removing the language tag from every menu, links showing untranslated slugs after a failed database query, an expired cached translation list being rebuilt on every request on sites without a persistent object cache, and a converted price that rounded to zero in a store currency without decimals. Admin notices appear above the PerfLocale tab strip, and the perflocale() helper can be called from a perflocale/loaded listener.

Full notes: perflocale.com/changelog

1.0.6

Security hardening and stricter permission checks.

Importing a JSON file from another site, or a backup of this site that records a language-specific address, can now ask you to confirm that this site is a copy of it: tick the checkbox under Settings → Export & Import, or pass --force in WP-CLI.

On WooCommerce stores, a visitor’s first page in the site’s default language no longer sets the language cookie, so full-page caches can store those pages. Cart and checkout keep working in every language.

Also fixes previews of draft translations that share their slug with a published page, synced patterns and navigation menus rendering blank when their translation was published empty, the WPForms builder’s “+ Create” failing even for administrators, an error or a duplicate when two requests created the same translation at once, page titles (WooCommerce’s Create Page Translations) and term names (Create Taxonomy Translations) saved in the admin’s language when the target language had no WordPress language pack, Strings-screen hints shown in the wrong language, and the Jobs screen showing “Not scheduled” for a task that was running. Front-end pages, feeds, sitemaps and REST requests also run fewer database queries – 2 to 8 fewer on each one we measured on a WooCommerce test site with Redis – with the same output.

On multisite, deleting the plugin now works through a large network in batches and records where it stopped if a request runs out of time: re-install the plugin and delete it again, without activating it, and the next pass carries on from there. Each site’s own “Delete data on uninstall” choice survives the interruption. Network activation no longer stops at the first site that fails, and rendering content from another site no longer leaves the original site without its detected language.

Full notes: perflocale.com/changelog

1.0.5

Translates block-theme templates and template parts, so the header, footer and page layouts you customise in the Site Editor can be translated like any other content, and shows a Translations panel in the Site Editor and in the Contact Form 7 and WPForms form editors — screens the existing panels could not reach. Fixes a class of defect where content that a plugin looks up by identity rather than by language disappeared on every non-default language: Contact Form 7 embeds rendered “Error: Contact form not found”, Oxygen pages rendered with no layout at all, block-theme navigation fell back to an auto-generated menu, and on WooCommerce block themes the entire product body vanished. Also fixes Contact Form 7 forms missing from the Translations screen, translated grouped products losing their product type and their child products, the shop page showing every language’s products when it is the front page, cart and checkout links pointing at unpublished pages, a “Needs update” badge that could never be cleared, an Oxygen template that could render in the wrong language once its translation group was reduced to a single translation, a dashboard that counted trashed translations as translated, a multisite case where one subsite’s active add-ons could switch off language filtering on another, and WPForms forms that could not be translated by anyone at all — every translation request was refused, administrators included. Elementor translations also no longer inherit the original page’s generated CSS and cached HTML, which could make a newly created translation render unstyled or show the original language.

Saving a block template now creates it in every language, each seeded with the original’s blocks and created as a draft, so nothing changes for visitors until you publish one. Add a language later and the next save picks it up.

Page-builder layouts are no longer overwritten between languages. Elementor, Beaver Builder, Bricks, Oxygen and Oxygen 6 store a page’s text inside their layout data, and PerfLocale had been keeping that data identical across a translation group in both directions – so saving a translated page could replace the original with the translated language, and saving the original could replace a finished translation. A new translation is still created as a full copy of the original layout; from then on each language owns its own. The trade-off is that later structural edits no longer propagate automatically to existing translations.

Numbers and currency now follow the requested language’s own conventions rather than the locale the page happens to be running in, so a German page shows 1.234,56 where an English one shows 1,234.56. Media is no longer offered as a translatable content type: PerfLocale never translated media by duplicating attachments – it stores per-language alt text, captions and descriptions on the same attachment – so the checkbox enabled nothing while language-scoping every front-end attachment query as a side effect. Media translation itself is unchanged.

On WordPress 6.9 and newer, four read-only AI-agent abilities (list languages, get a post’s translations, detect a post’s language, convert a URL between languages) now register by default; the two write abilities stay off. Both switches live under PerfLocale → Settings → Advanced → AI Agent Abilities.

Full notes: perflocale.com/changelog