We have a site built (DNN 5.6.2) that has translations into many (15+) other languages. This was all done with the built-in DNN tools. The English site was built, content localization enabled, all the other languages added, and then translations for each language was added. All versions of the site are identical except for the obvious translation differences.

The issue is that, during initial testing while adding the translated text, we could force the browser into another language mode and it displayed properly and without issue, allowing us to do some basic testing. During final testing, however, we're using machines with Windows installations running natively in other languages to better approximate someone's setup in another country. The language detection and display is behaving strangely in this case:

- browser cache is cleared, browser is closed
- browser is opened, homepage is input into the browser (domainname.com/dnn)
- homepage displays in English
- browser refresh/reload button is pressed
- homepage is displayed in the desired native language

This happens across most major browsers. Why doesn't DNN display in the correct alternate language the first time the homepage is entered? The OS and browser should be set to native Spanish or German versions, for example, by virtue of running German Windows. DNN browser language detection is enabled. The system and site default are US-en.

Ideas or suggestions? With so much time spent inputting 15+ languages of content across the entire site and the initial tests with manually specifying browser language working properly, it's very frustrating that the final tests are not behaving as expected.

Thanks, but it doesn't seem to be a cookie issue. Not only are we clearing cache and cookies between attempts, but I just tried on a totally new OS build that's never gone to this website before and it still displays the issue.

Homepage in IE (msn.com) immediately comes up in the foreign language, but the site we're testing then shows up in English. A reload of that page produces the desired foreign language.

Further thoughts?

Anyone have further thoughts on this? It's a major problem for the site we're building.

How does DNN do its browser detection? Shouldn't it happen as soon as the page is hit before content is displayed?