Hi there,

A web publisher company made a fancy design for our website. Unfortunately all the layout stuff was done with CSS. They didn't use the skining features at all!!! While I was able to fix most of the other issues using the CMS, I have some serious troubles implementing the menu. Here is how the site looks:

As you can see for yourselves, the menu is realised in a rather special way. There are two panes containing the menu, as follows:

And this is how the code behind the menu looks:

<span class="productselect" id="carrierbg">
  <a class="firmen" href="/tabid/110/Default.aspx">Carrier</a>
  <a class="carrier" href="/tabid/109/Default.aspx">Company</a>
</span>
<span class="productnav" id="carriernav">
  <a href="/tabid/58/Default.aspx">IDE: CTMaker®</a>
  <a href="/tabid/57/Default.aspx">IUCS: Callisto</a>
  <a href="/tabid/59/Default.aspx">Vermittler: COC Express</a>
  <a href="/tabid/60/Default.aspx">Solutions</a>
  <span class="spacer"></span>
  <a href="/tabid/68/Default.aspx">Services</a>
  <a href="/tabid/79/Default.aspx">Support</a>
</span>

The first span tag marks the tabs on level 0: Enterprise (red) <-> Carrier (blue). The second span tag marks the menu items on level 1.

Now for my problem: I tried to implement the menu using the DNN TreeViewMenu, but then I don't seem to have any influence on how the menu is built (auto-generated xml structure). So I'm not able to decide when to apply specific CSS styles to certain menu elements...

Any help or samples... ?

I don't think you can do this with Nav. You need a module component that keeps the menu items on the second level open, you can realize this kind of behavior with any UL list menu (house or snapsis).

Peter

Thanks for your feedback!

Our main problem is that we aren't willing to have to handle the menu using static hyperlinks. As you surelly can guess, the work load would be increased heavely with every change.

Therefore we would like to use the site structure provided by the DNN framework. But now we are having the problem that the TreeViewMenu is built on the fly using a mish mash of ASP.NET code, JS code and XML data. This is the point where it gets too confusing for me... If I only could read the structure entries and decide wich CSS styles to apply...

If this isn't going to work , another way would be to provide the site structure using our own XML file.