I think this epitomizes why DotNetNuke has such a bad reputation.

I really don't get it - Why does the entire DNN core team consistently ignore common HTML standards and best practices? Do you just not care?

Block elements being put into inline elements for example.

The standard menu with its use of TABLES is another one.

Even the dotnetnuke.com site doesn't use its own menu solution, they use a Telerik RadMenu (for which there is no Provider inside the core... talk about fragmentation)

I fixed this by completely ditching the NavigationProvider concept. I created a custom SkinObject which renders a normal unordered list, works great with superfish.

For those of you who have had problems with DNN having the JS render changes, have you tried using the DownLevel property, instead of UnorderedList for the custom attributes on the DNNMenu? That, I believe, will force it to always only render the HTML and not use JS.

---

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions