Multilify 1.6.0
October 10, 2026
Routing, caching, lifecycle and admin accessibility fixes, with the ?lang= query variable retired in favor of the address.
Fixes
- A
comment-page-Naddress of a translated page returned a 404 under a prefix, and the same tail on an entry's original name was not redirected to its translated address /and the other typed feeds returned a 404 for a nested page and an empty feed for a flat one{lang}/ entry/ feed/ atom/ - The second page of a search under a prefix,
/, searched for "term/page/2" and found nothing, and a search feed came back as HTML{lang}/ search/ term/ page/ 2/ ?lang=in the query string overrode the language in the address, so a Turkish entry opened with?lang=dewas a 404. The address decides the language now, and the query variable is ignored- An oEmbed of a translated address named the entry in the default language and framed the default address
- On a subdirectory install, a nested translated path whose first letters spell the directory's name lost them while being routed
- The switcher on an attachment, a product or another post type the plugin does not translate linked every other language to a 404. It links to the language home now
- An excluded search term,
-word, was ignored when the word appeared only in the translation - A cookie left behind for a deleted language switched browser language detection off for a year
- A crawler's answer at the site root carried no
Varyheader, so a shared cache could hand it to every browser - The site locale was never switched for the default language, so a site run from a Turkish admin that publishes in English printed Turkish dates and "Bir yanıt yazın" under
lang="en" - Deactivating the plugin left its rewrite rules in place, so
/went on answering with the default text until the permalinks were savedtr/ - A network activation set up the main site only, and every other site 404ed on its language prefixes until an administrator opened its dashboard
- The rewrite rules a new version adds waited for an administrator to log in. They are rebuilt in the first request after an update
- A translated slug changed by WP-CLI, an importer or another plugin kept resolving to the old address for an hour on a persistent object cache, and an entry trashed, restored or published on schedule stayed in, or out of, the sitemap for as long
- The slug suggested from a translated title dropped every accented letter outside Turkish and German, so "España" became "espaa", and emptied a non-Latin title. It follows WordPress' own rules now, with German umlauts written out as ae, oe and ue
- The switcher marked its active link as the current page on archives, search results and 404s, where it points at the language home
Changed
- The default language's prefix,
/on an English site, redirects permanently to the address without it instead of serving the same page twiceen/ ... - A lookup for an address that does not exist is remembered for five minutes rather than an hour, so a flood of unknown addresses cannot push real entries out of a persistent object cache
- The lookup index is created from an administrator's own request only, never from an anonymous
admin-ajax.phpcall - Settings page: every button names its language for screen readers, each flag option is named by its emoji, the delete dialog makes the page behind it inert, the text fields meet the 3:1 contrast a control's edge needs, the selected flag keeps a visible focus ring and Space no longer clears it, forced-colors mode gets a system highlight, and the title and tally stack on a narrow screen. The stylesheet uses logical properties, so a right-to-left admin keeps its gutters
- Editor: each translation's content editor is named with its language, and the slug hint is read out with its field
- The unused
multilify_settings group was removed. The settings page never used it, and throughsettings options.phpit let an administrator store a default language that did not exist