Sorry for the misunderstanding. I am using DSLocalizator too. It does all I need and it is a great tool. But as you mention, support is lacking. Remember when DNN 5 was launched? How long did it take to have the beta released (which should not be used in a production environment) that could work with DNN 5? Months! Half a year?

The risk is that some upgrade of DNN will break it again. So, I am advocating to have its functionality included in the core DNN. That is happening now and it has my full support. Of course, the CL strategy is different, DSLocalizator has to "hack" the core of DNN.

The important issue is now that you can continue to use DSLocalizator (or any widly used CL solution) until you are ready to migrate.

---

____________________________________
The one-eyed in the land of the blind.

Mauricio? Is that Locopon's name? He has abandoned the forum in January 2010 and has not been heard of since. I can see Jaydee96 answer some postings but he is as much puzzled as anyone about the problem with DSLocaleSelector.

Did you get DSLocaleSelector to work properly?  There seems to be a dll missing. Now I installed the new (beta) release on DNN 5.0.1 and never had the version that worked for DNN 4.x. If you were using DSLocalizator before version 5.0 you might still have the old dlls and that may be why for you DSLocaleSelector works?

DSLocaleSelectorPA works, but that's the module version of the locale selector, not the skin object. So, I'm forced to use DNN's core language selector. That works too, but lacks all the options that Locopon had built into his locale selector :(

When I read your reply, I first of all went to check the forum (thank you for the link) to see if there was any change in the situation. Many users have questions about how to make the locale selector work. If there would be a work-around or a new (stable) version, I would be one of the first to play around with it.

Check out this thread http://dnn.tiendaboliviana.com/web/Su... and go to the end. Return one page and check the date of Locopon's last reply. Problem unsolved.

Go to the last page and follow Jaydee96's link. That is basically where we stand now. Of course, relying on free solutions involves risks. If you have any reassuring news that can persuade me DSLocalizator is not abandonware, I would be very very happy to learn it. But if things go wrong, I can only hope that the core of DNN will allow us, me and you (and the pay sites) a soft landing.

---

____________________________________
The one-eyed in the land of the blind.

Mauricio is the leader of the DNN FCKeditor Provider. He is so closely related to DNN, this man knows DNN. I always wondered why he didn't got involved into the core DNN localization. It's really damage that DSLocaleSelector and also hi's other modules seem to be more or less abandoned. I'm stucked with my websites containing DSLocale on DNN version 4.9.5.

When we heard some time ago that the core dynamic content localization is on the way, my hope was that the problem would be solved. But now we hear some comments about, which aren't just euphoric. I was about to install DNN 5.5 when I read this thread concerning the fundamental concept, which though didn't cause a great debate.

At the time it seams, that the long awaited happy end of this long long localization story is not yet achieved.