I've reported a couple of times in this forum about my experiences with DSLocalizator. It seems Locopon has had some trouble with his webhost but now is very much back online.

The problem with the DSLocaleSelector has been solved and the secret is revealed why it worked for some and not for others. The proper way to install the skin object is this:

• You install a LocaleSelector module in a test page and configure it like you want it in your skin
• You look at the bottom of the configuration page and click the link "Generate Sample Code for ASCX Skin". This opens a Notepad editor with the text for both the header and the skin object
• You copy/paste that into your skin on the right place.

Dead easy if you ask me. Problem was that the text for the skin object was not correct. I had already noticed a missing forward slash at the end of the object, but I had failed to see that the runat="server" was not there. Fore skins with the correct code it worked, but new skins could no longer rely on the code that was generated by the LocaleSelector module.

03.00.05 solves that and is now no longer a beta version. We've beta-tested it long enough, some of us in production environment because it is so versatile and nothing remotely compares to it. I personally like to combine it with the magic content module (also free).

---

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

The bug in DSLocalizator 03.00.04 was not the only one, if I may have left that impression. Adding runat="server" did not suffice to make the skin object work. Another bug made the DSLocalizator 03.00.04 a defective version. So, without installing 03.00.05 you cannot make DSLocaleSelector skin object work on DNN 05.x

---

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