It seems its doable based on this http://nbstore.codeplex.com/discussions/277432 but after I applied this and I look atthe products it seems none will display now... I have re-save thed module settings, but still no dice!

Anyone ever experienced this?

Hi,

I'am experimenting now with some setting on DNN6 with content localization enabled and some multi-language modules.
None of the multilanguage modules will work at this moment with DNN 6 and content localization enabled.
Maybe in the future.
Read this on the DNN Forum
http://www.dotnetnuke.com/Resources/Forums/forumid/77/threadid/453772/scope/posts.aspx

Apollo is dead at the moment, no signs it will be living anymore on the forums.
So DS-Localization is the last module capable to translate everything on a website without using content localization enabled in DNN6*
However, there is a warning, DS-Localization is seems to be a dying module also.
No activity on this form either.

I use DS-localization together with the toolbar of Oliver Hine.
This combination workst fine on DNN6.1.5.

Regards, Ton

Thanks ton, I am using DNN5 - I havent made the full transition to 6 for many of my clients, there are some thing I am not keen on re-training my clients on in 6.

I am diving into the DS now, think I used this one some years ago now. Thanks for the quick response.

Hi,

I use DSLocalizator on DNN6 without and major problems, however we only use modules that deal with localization on our websites.  We got so frustrated with modules not dealing with localization correctly, we decided to stop using them.  Fortunatly for us, this was possible, because we have developed a suite of in-house modules to deal with all the situations we come across.  So really we only have to deal with page/menu name, title meta data situations, whcih DSLocalizator does fine in DNN6.

I've played about with DNN localization and even tried a community module created by Sacha Trauwean, which actually make DNN localization understandable.  But I still can;t get away from the problem that DNN localization concept of creating seperate pages for each langauge is simply too much work and too time consuming to be a real answer for our company.

Erik from Apollo did tell me that he has made his module source available on codeplex and you can find them here...

http://pagelocalization.codeplex.com/

I've not looked at the source yet, but one of my ideas was to take this and see if it matches our needs, just difficult to find the time.

In summary, I do feel DNN localization is somewhat over kill for 95% of the world, I would like to see a 3 level system included into the DNN localization, 1 - No localization, 2 - localization on page names/titles (like DSLocalizator),3 - the full tab localization to deal with all situations.  But I do feel the level3 localization wil only be useful for large organisations who have teams of people to update lanagues, even international companies dealing with the lanaguges in each respective country....and hence I think it's an oppertunity missed by DNN corps to only add advanced page localization to the Pro version of DNN.

Still, the localization of DNN is an issue, and I often think it could be the downfall of DNN in Europe unless some easy/quick method is created.

Regards,

Dave.