0.13.27 — an account under a prefix

A second language version can live under a path prefix, such as `/en`. The router knows routes without the prefix and adds it itself to every link it renders. The trouble is with addresses that bypass the router: plain links and redirect headers the browser reads directly.

That was the case with accounts. The button in the wall inviting readers to create an account was a plain link and led to `/account` — an address of the default version, which has no such page, so the reader got a 404, and in the other language at that. The return address lost its prefix too. And after signing in with the email link, the server redirected to the bare account path or to `/`, again in the default version.

Since 0.13.27 every engine address that bypasses the router gets the current version's prefix: the wall's link, the account page in post-login redirects — by email link and via external providers — and the home page. The return address is treated as a browser address, with the prefix, so after clicking the email the reader lands exactly on the entry they started from.

A version at the root of the domain behaves as before — its prefix is empty.