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...HTML module doesnHTML module doesn't work, while localization-settings seem correct
Previous
 
Next
New Post
4/13/2012 9:16 AM
 

I've made a custom login-page, consisting of a HTML-module and the Module "Account Login".

It's in two languages, English and Dutch. After I finished the page in the Default Language, I clicked 'Ready for Translation'.

The second language page is correct for the Account Login-module. Username is translated into the Dutch "Gebruikersnaam".

So the localization works.

However, the HTML-module does not display both languages. The settings of the module are correct as well, Culture is EN resp. NL.

And even when I'm editing the text in Dutch, the Edit-screen shows the Master Language above the editing-box.

So it seems everything is installed correctly. Then how is it possible that the text is changed in both pages, no matter in which one I change it?!

 
New Post
4/15/2012 4:35 PM
 

Hi Joost,

You have to check on the "Localization" tab of the "page settings", if the the Dutch module is reference default language.

If it is so, detache the module, to make the content independant for each language.

 
New Post
4/16/2012 7:27 AM
 
Hi Sacha,

Thanks for answering.

I checked the localization settings. What I see is this:

The Dutch version of the HTML Module is NOT Detached and NOT translated.
These settings are the same for two other modules on the page. However, they work correctly.

What could be wrong here, and what should I do?!

And, what does "Reference Default Culture" actually mean??
 
New Post
4/16/2012 2:22 PM
 

Hi Joost,

"Reference Default Culture" = not "Detached" = the content of the module on the localized page is the same as the content of the module on default language page

It meed the module content will not be translated.
It this case the "Translated"  status is not applicable.

So if you want to translate the content (to have a different content in each language), you have to "Detach from default culture".

 

 
New Post
4/17/2012 3:29 AM
 
Ok, I've tried, but unfortunately:

The button "Detach from Default Culture" does not work. It does not respond, I can click it (it's not disabled), but nothing happens.
How can this be possible? And what can I do about it?

Futurama-version is 5.6.3.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...HTML module doesnHTML module doesn't work, while localization-settings seem correct


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