I have searched the forums at great lenght and read lots of posts about the various menu providers, css classes, menu properties and implementations.  Even logged into the Client API sections and read the blogs and downloaded all the release documents and still can't find the answer to my question, which I believe is very simple.

How do I configure the menu skin object to display only "hidden" pages and their respective children.  I think I am getting close, if I can use the "IsVisible" property somehow the way we do the "Dispaly =" property.

Can I simply do something like this, <dnn:MENU runat="server" id="dnnMENU" Display="Vertical" IsVisible="false"></dnn:MENU> ?

All I am trying to accomplish is to have two menus on the same page, one displaying normally and controlled by the Skin.css, and the other displaying ONLY the hidden pages/children and still controlled by the Skin.css

Am I close on this?

Clay

Thank you Leupold,

Is there a simple "work around" such as perhaps cloning the existing one and simply changing the objectqualifier or something to load only those pages marked hidden?

Clay

Hi Nina,

I have read and enjoyed a great many of your posts.  Learned a lot from them too I might add.  Great stuff!

What I was tryiing to acheive though is a more "consistent" way of doing this with hidden pages.  I have seen menu applications (designed a very simple one in classic .asp) whee pages could be "activated" or "deactivated" by selecting a checkbox in an edit view of the menu. 

Failing that, I wanted to the "look and feel" across both menus, with the flyouts, all driven by the Skin.css.  I may have to try cloniing the menu control, reworking the naming conventions in the code and then use that. 

I am familiar with the Inventua, and the House menus both of which are good, but add another level of "design" complexity in that neither (that I am aware of) will access the Skin.css for "look and feel."

I took a tip from some of your skinning comments and designed a "template" sking that any newbie could use to create a new "look" for a site simply by changing the images and colors accessed in the Skin.css.  With this I was looking to simply separate and view "normal" pages from "hidden" pages and still use he Skin.css so as to limit the time to "live" for a new skin. 

This way, if I wanted to then go with "vertical only" menus, they would appear to simply be one above the other in the skin, or the same for horizontal menus.  Leaving open the option to split the menus and still keep the same look and feel without needing to change two CSS files.

I'm not a strong programmer and much more of a "cut and paste" artist when it comes to getting things done.   In any event, I hope this all makes sense now.  

If I can't find a way to hack the menu skin object to achieve what I want, I will probably cave in to using Inventua or House menus.

Thanks again Nina,
Clay