This project has moved and is read-only. For the latest updates, please go here.

Enable Browser Language Detection not working

Feb 3, 2014 at 10:46 AM
after I've installed url rewriter it seems that Enable Browser Language Detection is not more working. Every users receives the home page localized with default language.

Is a bug or a problem of my environment that I can solve?

Feb 6, 2014 at 9:09 AM

I have try to setup a installation to reproduce the Detection problem.

But, i can simulate a good redirection from with the browser language detection in DNN 7.2 without openurlrewriter.

Is it succesfully work for you without the openurlrewriter ?

If yes, on which version ?

Feb 6, 2014 at 9:18 AM
yes: it worked before installing openurlwriter

My version is 07.00.06

Feb 16, 2014 at 9:41 PM
I have ad it to v.1.1.5

Marked as answer by sachatrauwaen on 2/16/2014 at 1:41 PM
Feb 17, 2014 at 8:22 AM
Thank you!
But if I try to install it reports "The module being installed is not compatible with this version of DotNetNuke. An upgrade to version 7.1.0 is required."

So you have changed requirements and it's now mandatory upgrade from 7.0.6?
Feb 17, 2014 at 9:05 AM

I will make version of openurl rewriter available for dnn < 7.1 shortly.

Feb 18, 2014 at 4:26 PM
Just upgraded DNN to 7.2 and openurlrewriter to 1.1.5: a disaster!!!

Websites with multiple languages don't work anymore! Url are generated with wrong path (missing /language/ part in url), and if I call pages (with or without /language) I always get 404 error.
Feb 18, 2014 at 6:42 PM

In DNN > 7.1 you need to create 1 site alias for each language.
And the alias must contain the language.

This is not a openurlrewriter thing. It's standard DNN.

for en :
for fr :

Feb 20, 2014 at 5:26 PM
In fact I did create the alias, but I think is not necessary because with urlFormat="advanced" DNN will do this.

However, I've restored the last version than upgraded an other time all from scratch.
Now I have dnn 7.2.1 and openurlwriter 1.1.5 online.

I've found that the main problem was that I use SiteAlias Mapping Mode=redirect to redirect from to (primary alias). I've changed it to "canonical" and now at least generated urls work. However now doesn't redirect and this is not SEO good. Can I fix?

However, still now if I enter the home page using a non english browser (english is portal default language), I'm not redirect to the specific language home page.
I've created a brand new DNN, installed openurlwriter, on Azure, and it works. So I think that there is something with an old dnn updated that is the problem (DNN is ALWAYS AN HELL). Any idea?

Feb 20, 2014 at 5:38 PM
update: it started. Now home page is localized based on browser language.

I don't know why. After a lot of test, it started. Maybe just DNN cache (but I've restarted the app many times before...), browser cache (but I've cleared that also...), maybe.... boh!
Feb 20, 2014 at 5:39 PM

Normally on a new install with urlFormat="advanced" (on core urlrewriter and with with openurlrewriter)
when you add languages, dnn automatically add a site alias for each new language.

But, i know that when you upgrade, this not happen automatically.
You have to create them in addition to a default alias without the language.

The browser language detection works only with 1 alias / language.
Be sure to remove the language cookie when you test this.
And it works only on the default url ( without a language in it.

The redirection works only when redirection is selected.

Is it accessible over the internet ? Then i can have a look.