All issues with the core implementation will be solved in the new release (soon). There may be an issue with the OH control panel (in relation to language selection), but I have not tested that out yet. Besides that, all functions correctly. The current version 3.0.5 has 3 issues:

• Skin objects in the HTML file do not translate into objects in the ascx file (Though can be used when implemented correctly in the ascx file
• Localized default containers from portal and tab localization are not used
• There was a problem with the breadcrumbs, but I cannot reproduce it with the code I received.

All issues are resolved in the upcoming release 3.0.6 (I guess by the end of the week, the corrections are with Mauricio now who wants to add some features of his own)

As soon as there is a beta of 5.6.2, I will do tests on that too. I need to keep DSL going. As soon as something fails in a new DNN release, it is imperative that I solve it before updating my portals. In my development configuration, DNN 5.6.1, DNN and DSL 3.0.6 are a perfect match.

---

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

I will. Let me first delve into the issue so that I have an idea of what goes wrong. DSLocalizator has a lot of options that I have not tried out yet, like the possibility to define your own language detection rules, that risk conflicting with new language features. When I understand what happens, I will let you know.

---

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

Hi Marc, thanks for the clarification. Advanced Contropl Panel has an extra detection for UI language, but AFAIK in DNN this might differ from content language only, when content localization is turned on.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN