Skip to content

Multilify 1.5.0

October 3, 2026

Closes a security hole that served password-protected entries in other languages without the password, and fixes the routing, SEO and translation gaps an audit found.

Fixed

  • A password-protected entry served its full translation in every other language without asking for the password. The password form now stands in every language, and a translated title keeps the "Protected:" prefix the original shows
  • A translated slug could take another entry's own address under a prefix, which left that entry unreachable in the language. Another entry's own name now counts as taken, and the slug is numbered instead
  • A page, or an entry of a custom post type, with no translation in a language returned a 404 under that language's prefix, although the settings screen promises the default text there
  • A post type the plugin does not translate, such as a WooCommerce product left out of multilify_post_types, lost its base in links on translated pages and pointed at a 404
  • Translated content ran after WordPress' own formatting, so paragraphs written in the editor came out joined and blocks and embeds did not render
  • The template tag switcher on the blog index, an archive or search results linked every language to the first post in the loop instead of the language homes
  • A prefixed language still answered on an entry's original slug beside its translated one. That address now redirects permanently, as the default language's has since 1.4.0
  • Embeds, comment pages and trackbacks of a translated entry returned a 404, and its oEmbed link was refused as an invalid URL
  • A search under a language prefix only matched the original title and content
  • An item in /{lang}/feed/ paired a translated title with the original content
  • The bundled Turkish and German translations never loaded on WordPress 5.8 to 6.7
  • wp_title() and single_post_title() kept the original title on a translated page
  • Renaming an entry through Quick Edit, the REST API or WP-CLI left its translated addresses pointing at the old name in a persistent object cache
  • An array in ?name= or ?pagename= raised a PHP warning
  • The copy buttons on the settings page dropped keyboard focus to the top of the page, the flag grid ran off a phone screen, and the page's intro squeezed into a narrow column beside the tally

Changed

  • hreflang tags are printed only on an entry and on the language homes, and only for languages the entry has text in. A language with no text of its own points its canonical at the default address
  • WordPress switches to the installed locale of the language being viewed, so its own strings, dates and the comment form follow the address. Return the site locale from multilify_locale to keep a language on it
  • A visitor at the site root is sent to the language they picked from the switcher before, ahead of their browser's preference. Logged-in users and crawlers are never redirected, and the answer is no longer kept by a shared cache for the next visitor
  • The switcher's stylesheet is printed inline, and its script loads only on a page that shows a switcher
  • Focus rings on the settings page follow the admin color scheme
  • Index creation and the first rewrite flush after an update run once, from the admin, instead of on every request until they succeeded

Added

  • A sitemap for every language other than the default, listing its home and each entry with text in that language
  • The multilify_is_crawler filter
Release History