Hi All,

I have a few issues with the default NAV menu that comes with DNN.

1) Is there a pure CSS version? Mine is using tables and that seems a little silly.

2) I have removed the small icon from the menu but there is still a space (ie table cell) where it is supposed to go. Is there a way to remove that table cell?

3) I have a site that is using the items on the main nav bar simply to access the submenu items (ie, the page shown in the main menu is disabled but the child pages are active).  When you mouseover the mainmenu item it works fine but when you click on a mainmenu item the submenu disappears. How can I keep it open when you click on it?   

I am facing the same as the 3^rd issue that Scott reported.

...

3) I have a site that is using the items on the main nav bar simply to access the submenu items (ie, the page shown in the main menu is disabled but the child pages are active).  When you mouseover the mainmenu item it works fine but when you click on a mainmenu item the submenu disappears. How can I keep it open when you click on it?   

...

I am using version 5.5.1

 

In index.ascx I have the lines:

<%@ Register TagPrefix="dnn" TagName="NAV" Src="~/Admin/Skins/Nav.ascx" %>

and

<dnn:NAV runat="server" id="dnnNAV"  ProviderName="DNNMenuNavigationProvider" IndicateChildren="false" ControlOrientation="Horizontal" CSSControl="mainMenu" />

What can I do?

Just a quick follow up to this Timo - and I hope this doesn't come across snarky - but can we possibly look forward to DDR or some similar system being integrated into the CE core? It seems this (lack of a 'pure CSS' and 'SEO Friendly' menu provider) has been a well known issue since the late days of SolPart and now with Telerik I'm having flashbacks of the Solpart days of wrestling with wrapper code.

It seems that DDR is always brought up as a solid alternative, and it's free which is a bonus, but as it's third party I'm a bit hesitant to implement it as widely since the use of 3rd party modules makes the upgrading process exponentially more difficult especially when that developer falls out of contact or changes their licensing terms / costs whereas if it's maintained as a community project we can at least track it or have new developers step in to keep it up to date.  I'm not trying to be lazy (really, I'm not) but it just seems like a solid, dynamic XHTML menu provider has been needed for quite some time.... and I'm tired of spending more time learning new menu providers than about all the new widgets and nifty features (ok, that part I'm probably being a bit lazy on).

---

Wells Doty Jr
Online Content Development