I think I can shed some light on this, sorry to keep you waiting so long. Obviously, no, that's not how it's intended to work. I think what happened, is that the session locale from the backend (when you translated the page) was re-used on the frontend, as there was no locale provided in the URL. The globalize2 extension does not look up your locale by means of browser settings or IP, merely by the request URI.
I'm not sure which version you were using, but it's definitely outdated by now; the extension has been a bit buggy since Radiant itself is multilingual, and would very often clash with other extensions.. It has recently been refactored, and is much more robust now. Please try again with https://github.com/jomz/radiant-globalize2-extension (or gem install radiant-globalize2-extension ), and let me know if you still encounter problems. On Mar 4, 7:58 pm, wlai <will....@gmail.com> wrote: > I have an radiant installation with Globalize2 setup. The default is > set to be en-us, and have a bunch of other european languages enabled. > > Repro: > - The problem I run into is that I'd create a new page, and save it as > the default language (en-us). I visit the URL (http://example.com/ > test) and see the page as expected > - I'd then go back in admin, click on the Spanish flag to create the > spanish version of the page, and saves it. > - Now when I visit the URL again, I'd see Spanish page, even though my > browser settings is all en-us, and I'm browsing from an US ip address. > > Is that how Globalize work? The last saved page is the one > displayed? That would seem to me to defeat the purpose of a "default" > page, no? > > Any help appreciated. Thanks.