Hi, it's been a long time since my last post, which means your Localizator is working great... until now =P

I had a website installed with DNN 4.7.0 and your DSLocalizator, all was going perfect and smooth, until the web admin decided to change the Performance Settings from the Host Settings Menu.

He changed the settings to:
- Performance Setting: Heavy Caching
- Authenticated Cacheability: Server
- Compression Setting: GZip Compression

He swears he didn't change anything else, and I'm not sure about this, but I trust him. The results I'm getting is that, although I have the Skin.xml and the .ascx from the skin set to use the LocaleSelector as a link, it sometimes shows itself as Select combo box. This happens when we "launch" a .Net 2.0 application in an IFrame that has update panels, iframes, ajax and some more stuff, but it was like that before the "error" started to happen, and before the change in the Performance Settings.

I have tried to setup the performance in the same way in other websites with the same application going on them and nothing has happened this far, it's still working allright.

I'm really sorry that I can't provide you any other information apart from this, but maybe you know something that could be causing the LocaleSelector to behave that way.

Even if nothing of this rings a bell, let me know it.

Thanks in advance =)

Sorry for the late reply, but I've been on holydays =)

Well, back to the matter. I'm sorry to tell you I can't be more specific than what I was on my first post. We had a site installed, your module was installed, hacked and all that. We had it setup to show links and worked perfect. Then my boss changed the Performance settings and it started showing the combobox instead of the links.

As a side note, the combo is empty.

Javier, I also had a lot of problem with many other modules when changing the page state to memory. Also, when the site grows and there are many visits per day, the memory could be eat by this option. So that is the reason DSLocalizator includes an option to keep the page state in the SQL server.

The viewstate in SQL is not necessary for localization. It is just one of the optimization features included in the module.