Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...DotNetNuke 5.5 Localization - language parameters not working?DotNetNuke 5.5 Localization - language parameters not working?
Previous
 
Next
New Post
9/3/2010 9:58 AM
 
I think they just tested it with us_en and uk_en and it looked good ;)
 
New Post
9/6/2010 5:05 AM
 
Thx a 1.000.000. Both for fixing my language problem (mentioned in the first post) and for Adv. Control Panel - what a gem that is!
 
New Post
9/13/2010 8:02 PM
 
Kivi Com wrote:
Sebastian Leupold wrote:
Bruce, please be aware that in DNN 5.5.0 localization of static elements is no longer controlled by language parameter and language selector but by user preferred language or for unauthenticated users by browser settings or portal default language only. This might change in future versions.

 Sorry, but this is just one of the stupidest things DNN team ever did!

 Amen.

I tried to post to Gemini, but the post never completes :(

It's actually messier than that, so probably broken

Assume you have en-US and id-ID cultures.
And you have id-ID in the URL

CurrentCulture = id-ID  CurrentUICulture = en-US
Formerly they were the same (id-ID).

EVEN WHEN THE AUTHENTICATED USER has a preferred locale of id-ID and the portal default language is id-ID

The result is that the current page will localize (somewhat) but the URLs in the menu will revert you to en-US on the next page anyway.



 
New Post
9/14/2010 4:33 AM
 
In DNN 5.5.0, qs param Language drives currentLocalue (content language only), CurrentUICulture (static localization) is derived from user profile (registered users) or browser settings (anonymous users). There as plans for modifications in 5.5.1, synchronizing static language with content language for most of the cases.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/14/2010 9:58 PM
 
WTF?
Why would it ever be a good idea to separate the static and content localization?

And that still doesn't explain why (if it is the case) my browser en-NZ settings forces a default en-US langauage instead of the portal default, or the preferred locale that I have set for my logged in user account.  Makes it pretty much impossible to do testing.

Guess I'll go hunt through PageBase.PageCulture
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...DotNetNuke 5.5 Localization - language parameters not working?DotNetNuke 5.5 Localization - language parameters not working?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out