I use HTML/XML using tokens to skin DNN pages. Will HouseMenu 2.x work using the HTML/XML method? If so, how? Or am I SOL? I've been using HouseMenu 1.x and love it!

I've made a little progress with this (woo-hoo!). I can get the HouseMenu to show up on my skin, but I still haven't figured out how to get the custom attributes to work. I'd appreciate any help anyone can give me with this.

The NAV in my XML file looks like this (I took out the opening brackets):

  Object>
        Token>[NAV]
        Settings>
            Setting>
                Name>ProviderName
                Value>HouseMenuNavigationProvider
              /Setting>
        /Settings>
        CustomAttributes>
            CustomAttribute>
                Name>CssClass
                Value>HouseMenuNav2
            /CustomAttribute>
            CustomAttribute>
                Name>MaxDepth
                Value>-1
            /CustomAttribute>
            CustomAttribute>
                Name>RootDepth
                Value>-1
            /CustomAttribute>
        /CustomAttributes>
    /Object>

The ASCX generated by DNN when I upload the skin looks like this:

dnn:NAV runat="server"
id="dnnNAV"
ProviderName="HouseMenuNavigationProvider"
CssClass="HouseMenuNav2"
MaxDepth="-1"
RootDepth="-1"

However, the generated HTML does not pick up the custom attributes:

ul id=”DefaultCssMenu” class=”AvastoneCssMenu”>
!-- Depth: 0 -->
li id=”EVENTS_item”>
li id=”MEMBERS_item”>
li id=”Admin_item”>
li id=”Host_item”>
/ul>

Sue,

Good progress! Honestly, I don't know how to specify those custom attributes in the XML so that they will work correctly.

Actually, yours might be working. I believe the HTML that is rendered will always specify depth 0 for the root. When you use -1 for MaxDepth and RootDepth, you're telling the menu to render everything. Try setting MaxDepth to 0 and let me know the results. You should lose the submenu dropdowns....

Tim