Multilify 1.4.0
September 26, 2026
An entry given a custom slug in the default language now answers on that address alone.
Changed
- Its WordPress slug returns a permanent redirect to the custom one, the way WordPress answers any renamed entry, and page numbers, feeds and embeds are carried across. Both addresses used to return 200, and inconsistently: the paged form already redirected, because WordPress only runs its canonical check on a request carrying a page number.
- An entry with no custom slug in the default language is untouched, and so is every prefixed language, which has one address already.
Browsers cache a permanent redirect, so clearing such a slug later can leave earlier visitors on the old address for a while.