Multilify 1.1.0
August 22, 2026
Language routing fixes, hreflang output, browser detection, and a rebuilt settings screen.
Fixed
- Language detection now works when WordPress is installed in a subdirectory; the install path is no longer mistaken for a language code
/and{lang}/ page/ 2/ /return content instead of a 404; paged entries, entry feeds and search under a language prefix now route correctly{lang}/ feed/ - Child pages keep their parent path in translated URLs, so
/resolves instead of 404ing{lang}/ parent/ child/ - The document title on the front page and on archives is no longer overwritten with a post title from the loop
- Translation panels no longer save on revisions or on post types they were never added to
- Meta box fields no longer inherit the inline editor's layout, which shrank their labels and clipped their inputs
Added
rel="alternate"hreflang tags, includingx-default, in<head><html lang>and aContent-Languageheader that follow the language being viewed- Browser language detection for first-time visitors, remembered per visitor and overridable with the
multilify_filterenable_ browser_ detection - Translation progress per language on the settings page
- A flag picker in place of the free text emoji field
- Custom post type support through the
multilify_filterpost_ types - Filters:
multilify_,translated_ title multilify_,translated_ content multilify_,flag_ choices multilify_locale
Changed
- Rebuilt the settings screen: language entries read as a list with their code, name, default state and progress
- Corrected readme claims that the code did not support