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...Adding second language to siteAdding second language to site
Previous
 
Next
New Post
6/13/2011 5:49 PM
 
Hi,

I've read quite a few postings about adding multiple language support to my DNN site but I wanted to break it down to a simpler form if possible.

On one post I found this:

  1. Install DotNetNuke
  2. Setup your content for your default language
  3. From the Host/Host Settings page enable content localization
  4. From the Admin/Languages page add the two additional languages
  5. Enable Content Localization on the portal (from that admin/languages page)
  6. Edit the content for each of the languages, to provide the translated version.
  7. Mark each page/module for the languages as translated (from the page settings)
  8. Go to the admin/languages page and mark the additional languages as Published
Let's say I have an existing site with 40 pages of content and I want to add support for Spanish for all current pages (basically clone the site for the second language). I follow the above listed steps 3, 4, and 5. But, at step 6, what do I do to get Spanish versions of the existing pages so that when the Spanish flag is clicked, the Spanish pages "replace" the English versions? And how about the Home page? Does it need some sort of special treatment?

Also, how would I handle home page module(s) that have been assigned "to appear on all pages"? I would need the same sort of module behavior on a Spanish version of the module / pages.

Thanks for any information provided.

Jim
 
New Post
6/13/2011 7:10 PM
 
Do you have the language skin object embedded in your Skin so that you can switch between languages?

That's how you switch back and forth.

As for "display on all pages" in all of my testing that feature works fine in different languages, though the content is different based on the language you "translate" into the module.

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
6/13/2011 7:25 PM
 
Jim,
DNN 5.5 + Content Localization feature (AKA "Localized pages") creates copies of EVERY existing page when executing step 5 (unless the process times out, which might happen on larger sites). After you switched the language (visible by appended beautiful language key to the page names) you may translate page names, module titles and content. Some modules might not need to be translated or support multiple languages by itself, but DNN will ignore this.
Display on all pages should be avoided when using localized pages, otherwise you will get 3 copies of each module on each page.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/13/2011 7:44 PM
 
Thanks for the response.

I have a published, working site that I use for testing modules and such. I will backup the db for it and give the process a try and see what happens. Hopefully it will work as expected. I will need to do something with the "Display on all pages" feature, as I use it quite a lot on DNN sites I manage.

Thanks again!

Jim
 
New Post
6/13/2011 7:49 PM
 
If you need same content structure in all languages, using one of the existing ML solutions (EALO, Apollo or DSLocalizator) will be easier to use and provide better results, as long as you are using multilingual modules.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...Adding second language to siteAdding second language to site


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