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...Translated pages not going to German site - Help!Translated pages not going to German site - Help!
Previous
 
Next
New Post
5/31/2012 11:27 PM
 

Hi all,
When I translate a site to German, I don’t know where the translated pages have gone to.
When my client’s site was set up, the ISP (a well-known DNN ISP) set up the English (GB) site as default in blue, as well as a German site. The German site has just one page in a different colour (brown) to distinguish it. DNN Version is 06.01.04.
I’ve followed the instructions in the online manual, as well as 2 others I downloaded – Dotnetnuke 6.1.4 User Manual.pdf and Dotnetnuke 6.1.4 Super User Manual.pdf.
The Home Page address for the English site is www.[SiteName].com/en-gb/home/aspx. The Home Page address for the German site is www.[SiteName].com/de/home/aspx.
This is what I have done:
Install language pack – ISP guys did that for me at setup time.
Allow content localisation: http://hive.dotnetnuke.com/Default.as... done.
Enabling Localised content: http://hive.dotnetnuke.com/Default.as...  Done.
Translating a page: http://hive.dotnetnuke.com/Default.as...  Done.
Setting a page as Translated: http://hive.dotnetnuke.com/Default.as...  Done. NOTE this page of the online manual ends unexpectedly like this: Next Step: If this page is now ready to publish live on your site, (???Nothing more...?????)

So I went back to the DNN614 User Manual.PDF, which says "Publishing localised content" (page 1211), navigate to Admin > Languages. In the Culture grid, go to the Content Localization - Publish column.
Click the Publish Pages button. This displays the message "All translated pages in the German - Germany language have been published."
I get the above message allright - but again, when I click the German flag, all I get is the crappy brown page again.
The pages are there somewhere – If I follow the e-mail link (Pages ready for Translation), I do get to the pages and I am able to edit them.

Obviously I've missed something... Could one of you guys perhaps help with a bit of advice?

The ISP Support says: “One of our operations team looked into this for you and has confirmed that the German content needs to be in the German child portal and not on the English site. The German child portal was set up for you during the initial setup of the site including the flag link to it. The reason why it’s brown was to distinguish between the sites for you.”
This confirms my suspicions, but doesn’t provide a solution.

Could this be something to do with the difference between de and de-de? I'm suspecting the German site is at ../de/.. but the translated pages are being sent to .../de-de/... Does that make sense or am I blowing smoke? Where is the destination of translated pages set?

Regards,
Ernie

 
New Post
6/1/2012 7:56 PM
 
If your host created a site at www.[SiteName].com/en-gb/home/aspx and a page at www.[SiteName].com/de/home/aspx, most likely he created two separate child websites, each for a language, allowing you to create individual structure and content per language.
If contrarily, you prefer to use core language specific pages (aka content localization), you need to enter settings of the original page and in localization section, you specify, which modules are ready for translation.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/4/2012 2:21 AM
 

Hi Sebastian,

Thanks for the reply. Yes it looks like takayaking.com has been set up as you say. So this confuses me. What is the point of setting up a child portal as well as installing a language-pack? I think it would have been nice if the ISP had told me installing the language pack is a waste of time/money because it doesn't put the translated site into the child portal. It seems like a case of using one method OR the other, but not both. Is this correct?

So now I'm also confused about the way forward. If I use the language pack features, the German site is contained within the English site - will I be able to translate EVERYTHING, including page headers, module titles etc., or will there be some stuff I can't translate? Also I'll have to change the German flag to point to the translated "site", How do I do that?

The other option is to duplicate the entire site in the child portal, but there will be a heap of stuff I won't be able to translate - such as Login, Logout, date, time etc. How do I do all of that?

Any advice will be welcome.  Regards, ernieb

 
New Post
6/4/2012 3:58 AM
 
there are different alternatives to setup a site in multiple languages. one is using dedicates child portals, each with the appropriate language pack enabled and the proper localized (which does not necessarily means directly translated) content provided. If you would prefer a single user base and translation of content within the module, you may either use language specific pages of DotNetNuke core or multilingual solutions from Apollo, Loclopon or EALO.

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...Translated pages not going to German site - Help!Translated pages not going to German site - Help!


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