Multilify 1.7.1
October 22, 2026
Fixes the language home on sites with a static front page and keeps searches in the language they were made in, with admin improvements for phones and screen readers.
Fixed
- On a site whose front page is a static page,
/listed the latest posts instead of that page, and the switcher and hreflang tags sent every language to the page's slug. The language home now shows the front page, its translated title and content included, and{lang}/ /redirects to{lang}/ <front-page-slug>/ /{lang}/ - A search form on a language page searched the default language. Classic search forms and the Search block now submit to the language home
/and other addresses carrying the default language's prefix lost their query string on the redirect to the bare addressen/ ?s=term - Rewrite rules were rebuilt before themes and plugins registered their post types on
init, so those types' addresses could 404 until the next rebuild - A translated slug removed with
delete_and no value, as WP-CLI does, kept resolving from a persistent object cache for up to an hourpost_ meta() - A private page's translated address returned a 404 to editors who can read it
Admin
- The Languages column marks a missing translation with a dashed badge and a translated one with a solid border, so the state no longer rests on color alone
- Inputs on the settings screen and in the editor panel are 40px tall with 16px text on phones, which also stops iOS from zooming in on focus
- The Copy buttons announce "Copied" through a status region screen readers pick up
- Labels under 12px were raised to 12px, and the edit form uses the same input size as the add form
- Code examples read left to right in a right-to-left admin, and the arrow keys in the flag picker follow the reading direction
- A flags-only switcher,
show_, underlines the current language's flagname="false"