Sign In  |  Register
 
 
DotNetNuke Support Forums
Multi-language portal problem
Last Post 18 Mar 2008 03:36 AM by patrick1010. 2 Replies.
Printer Friendly
Sort:
PrevPrevNextNext
Please Register to post a reply.
Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.
AuthorMessages
patrick1010
New Member
New Member
Send Private Message
Posts:42

--
20 Feb 2008 10:55 AM  

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

John Mitchell
Administrator
Veteran Member
Veteran Member
Send Private Message
Posts:4350
Avatar

--
28 Feb 2008 10:24 AM  
Hi Patrick,
I don't know of any way to have the Announcements module do dynamic translation.

PageBlaster does cache each user language that you specify separately.
The next version could also be used to do some dynamic translation.
PageBlaster could also remove the language cookie or you could do it with Javascript, but I didn't think DNN put the cookie in there if you had the settings for disabling browser detection. I could be wrong there though.

I have to admit I am not really up to speed on using DNN with multiple languages.
patrick1010
New Member
New Member
Send Private Message
Posts:42

--
18 Mar 2008 03:36 AM  

Hi John

Thank you for the suggestions. I put the inline code into my skin and it's working great now:


Private Sub Page_Init(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Init
    if Not Request.IsAuthenticated then Response.Cookies("language").Value = ""
End Sub

 

thanks,
Patrick

Please Register to post a reply.
Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.


Active Forums 4.1
Visit our Store for great DotNetNuke Modules and Skins
DotNetNuke CSS Menu 3.4.6 (single use)

Item codeCSSNM33SU
AuthorJohn Mitchell
Base Price$39.00
Product Information 
DotNetNuke CSS NavMenu 3.4.6 (Developers)

Item codeCSSNM33DEV
Base Price$149.00
Product Information 
DotNetNuke Performance Caching & Compression - PageBlaster 3.4.5 - Professional Edition

AuthorJohn Mitchell
Base Price$59.00
Product Information