Latest Changelog
Polylang Pro 3.9.1 – October 21, 2026
Release-note summary from the official changelog.
- Corrects the country flags used for the Central African Republic, Honduras and Ukraine.
Download details: The available download is now Polylang Pro 3.9.1. Only the main Pro plugin is included; Polylang for WooCommerce and a vendor license remain separate.
What This Update Means
This maintenance release corrects a visible detail in the language selector rather than introducing another translation engine. A wrong flag can confuse readers even when the destination language is correct. Check each affected language on desktop and mobile before approving the update. Sites moving from the older 3.8 branch should also review the wider 3.9 requirements. That release line raises the minimum WordPress version to 6.8. Existing glossary and translator-permission settings still deserve a separate check. An updated flag does not demonstrate that every translated page has been reviewed. Keep the previous configuration available until navigation and editorial access behave as intended.
Polylang’s 3.8 release gave multilingual editorial teams a more specific answer to a familiar question: who is allowed to change which language? In its release announcement, the developer describes language-level editing permissions, alongside controls over automatic translation and DeepL glossary selection.
The permissions feature works with the separate User Role Editor plugin. An editor assigned to French content can be prevented from changing another language, rather than receiving broad access to every translation. That is a more useful distinction for a distributed publishing team than simply making every translator a WordPress editor.
Terminology has an owner, too
The same release line introduced selection of a particular DeepL glossary. A business that uses one preferred translation for a product name can apply that terminology consistently instead of correcting the same phrase on every page. It still needs a review process: a glossary decision cannot tell whether a translated offer is appropriate for a particular market.
A practical handover should therefore include two things: the languages each person can edit, and the terminology they are expected to preserve. Test those permissions with a translator account, not only with an administrator account that can bypass the restrictions.
Only the main Polylang Pro plugin is supplied. A nulled label does not grant a vendor account or translation-service access.
