Hi John
We are using 4 different languages for our website. Each language has been creates as an own parent portal. Four different language packs has been installed as well.
The Portal Settings is always set to the specific portal language and the browser detecion is disabled.
When a user gets to our website he is directed to the corresponding language portal. This is done by a browser detection start script. As soon he enters the language portal DotNetNuke stores the language into the cookie file. When an English user goes to our News page, he will read the [more] token of the announcement modul for example as "more...". This is working fine as it should.
Problem:
When the English user later enters the German portal News page the [more] token will be still displayed as "more..." instead of "weiter..." (german translation).
Is there a way where you can force the [more] token (of the announcement modul) and all other translated items to always be displayed in the portal language setting?
Or is there a way where you can force the language cookie not to be used? In my case it isn't useful at all. Another question:
What happens with PageBlaster? For example if different users (with different language settings in their browser) get to the German News page. Does the same German News page gets cached in many different language versions?
thanks,
Patrick |