Jamie McGrory

Ah this now makes sense. Thank you for explaining.

Nice site, I can’t seem to find an issue however (can always access any lang version of any page)…

Sounds like exactly what I had going on, do you also get an issue when setting a static homepage where after setting one for one language, setting one for another overwrites the others?

My process:

1) Make sure wp core/plugin are up to date
2) Make sure your homepage has all the required translations
3) Change Settings to:

Default Lang: ‘en’,
Detect browser language: Deactivated,
URL Mods > Language set from content: false,
URL Mods > Language set from directory name in pretty permalinks: true,
URL Mods > Language set from subdomain: false,
URL Mods > Language set from diff domains: false,
URL Mods > Hide URL lang info for default: true,
URL Mods > Remove /language/ in permalinks: true,
URL Mods > Keep /language/ in permalinks: false,
URL Mods > Front page url contains lang code instead of page name/id: true

4) Set static front/news pages on default language only
5) Deleted all my cookies since the plugin was implemented

Yes actually, by completely clearing my browser cookies AFTER changing settings it seems like Polylang actually starts paying attention to the default language.

I think it’s maybe that when the Detect browser language is enabled it might create an overriding setting in the cookies for the homepage (???) or at least pages with no ‘/xyz/’ following urls to hook onto.

It would maybe explain why deactivating it did nothing (the cookie was already presently set for the homepage) and why clearing cookies before changing my Polylang settings did nothing, just make sure all your settings are set to how you want it before you clear your browser cookies (default language/static homepage set/browser lang detect deactivated) and hopefully you get the same results.