Hi there,

At my work they made me responsible for all the websites of our companies but I am completely new to DNN and asp so I have a lot to learn :). I do have experience with Joomla CMS based websites.

One of the first thing I need to learn is how to make a website muli-language. In the release notes of version 05.06.02 and other articles I read that this version supports multi language. Therefore I have installed on a test website the 05.06.02 version but then I am lost how the multi language works. I came across this article but this is from 2009 and with that solution you need to install a couple of things. Google could not help me either and also I could not find any clear documentation on this.

Hopefully somebody can show me how this works or point me in the right direction.

Thanks,

Ewoud

What you've done is correct. The workflow is generally to either add a 2nd language (or install a language pack which will also add the 2nd language), and then if you want to do content localization you enable that option. What this does is take the default language as the master language and offer you the option to publish new pages that match the master language. These initially are not visible, giving you a chance to edit the content and when you're ready you publish at which point the permissions of the master page are applied (e.g. if the master has "view" permissions for all, then the child language pages get that - but equally if the master only had permissions for a different group they are applied - note: translated pages automatically get edit permissions for a language specific translators security role that you can add people to e.g. translations DE for german etc.)

Once content is published, the system records that the translated content is in sync with the master page - if the master page is edited the system then detects this and flags that the related pages need to be updated - which you can then do and publish.

As for apollo, it and other solutions (such as ealo) are alternative versions of localization - the core uses a page model so each translation if a new page and contains the same modules as the master language page. Apollo/ealo use a different model where individual modules understand localization so only 1 page and 1 module needs to exist and the module is clever enough to show the relevant language. This is a very efficent way to do things but does mean each module needs to support this model, whereas the core version covers all modules. Each solution has it fan's and I recommend putting together a test portal and playing with them until you settle on the one that suits.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

Looks like I found it. On the top there is a control bar with: Admin, Host, Modules, Pages, Tools. Clicking Pages and then Page settings and then Permissions, brought me to a(nother) page where permissions should be set apparently.

I also found something similar on the Module Settings but there the Read Permissions were already activated for all roles.

There is probably some logic behind all of this but I can imagine this is a little confusing for people who are new to DNN.