Hello there,

I told you I would discuss this issue in my prior post but decided it was in depth enough with that issue in hand that it warranted a new thread to address this DDR issue.

In this case I have been playing with the DDRMenuProvider using the NAV skin object as outlined in an earlier randition of tutorials done by Lee Sykes.  I have tried to use the attribute of Level=child for the DDRMenu Provider but in vein. I have been using the superfish template and practicing with this for my athetics trying to also invoke the slide animation on both a skin object level and a modular level with the DDR Menu module.

In any case on both of these levels as Lee Sykes suggested I tried to use the Level Attribute in the DNN:NAV object with the DDRnavigationalprovider but it is not seeming to work as I imagined it would.  In fact it is not merely showing just the child nodes of hte immediate parent but basically displaying a duplicate of what is seen in my horizontal menu. 

I am trying to create a vertical menu int he content area of my website that displays only the child and sub children of what ever node was selected and this worked beutifully using DNN:NAV with the DNNNavigational provider but is greatly lacking in the DDRNavigationalprovider do you or any others have any insight into this as to why this might be the case.

I also tested this by using the method found in the add to skin area as pasted in the txt file and I will paste also here but think that some of this code will be stripped out by your active forum module

--------------------------------------------------------------------------------------------------------

<%@ Register TagPrefix="ddr" TagName="MENU" src="~/DesktopModules/DDRMenu/Menu.ascx" %>
 <%@ Register TagPrefix="ddr" Namespace="DNNDoneRight.DDRMenu" Assembly="DNNDoneRight.DDRMenu" %>
 to the list of Register tags at the start of the skin.
◦Use the following format for the menu control in your skin file:
<ddr:MENU MenuStyle="..." NodeXmlPath="..." IncludeNodes="..." ExcludeNodes="..." NodeSelector="..." NodeManipulator="..." runat="server">
<TemplateArguments>
<ddr:TemplateArgument Name="..." Value="..." />
 ...
 </TemplateArguments>
<ClientOptions>
<ddr:ClientString Name="..." Value="..." />
 <ddr:ClientNumber Name="..." Value="..." />
 <ddr:ClientBoolean Name="..." Value="true|false" />
 ...
 </ClientOptions> </ddr:MENU> Only the MenuStyle parameter is required, all others are optional.
◦Set the MenuStyle parameter to the name of the folder containing your menu template (e.g. Classic, Mega1, Treeview, etc).
----------------------------------------------------------------------------------------------------------------------

I know this is not the way Lee Sykes said to do things but rather to navigate to DNN Menu>Pre-built Templates>Standard DNN Menu and coping the register tags from there which are not tag maned DDR but NAV as opposed to the way I was doing it after trying Lee Sykes method.  As you know the method as shown above between the dotted lines or in the txt file included in this thread as the case may be was to go to DNN Menu>Getting Started>Add to Skin. But the registration info using this method did not to work at all so I am sure Lee Sykes method is the right one to use.

Bottom line is how can I display Child elements of parents using the attribute Level-child or a new way of doing this as was done easily with the DNNmenunavigational provider using the skin object NAV and not DDR. (actually it appears you are not suppose to use a DDR skin object in the DNN Garden case either just change the DNN provider name to its appropriate name).

I researched this a bit and only could find some information about it being doable but not a simple configuration but rather a tweaking of some js stuff or programatically somehow.  Anyway can you guys let me know if this is possible.

Last thing I wanted to mention is trying to use the DDR Menu I was trying to create the slide animation within the client options area of the menu via the use of animation={width:200} but while this key/value combination did not blow up the module with a mssql database error as what happened when I simply tride animation:width=200 in this field still I couldn't see that any sliding effect or other effect was implemented so wanted your input about what I might potentially be doing wrong here in the DDR Module opposed to doing this via the skin object.

In Lee Sykes last video on DNN Garden DDR menu he explained briefly the module configuration focusing mainly on the name in regards to how to use a given template superfish, megamenu, etc... opposed to examples of how to use the rest of the fields within the DDR Menu module. I thought I had to make these special effects work by putting the appropriate information in either the template arguments or Client Options field but since Lee never really gave examples of how to implement these effects at the modular level but rather only at the skin object level I guess I was doing something wrong in the module and so couldn't get it to work properly.

Could you give me some examples of how I might use the following fields of this module:

NODE XML Path:
Node Selection expression:
Nodes to Include:
Nodes to Exclude:
Node Manipulator Type:
Include Context in XML
Include Hidden Nodes:
Template Arguments:
Client Options:

Lastly one thing Lee Sykes said at the end of this tutorial and something that is important to me as well is how one might be able to show the child element of a parent from a given menu provider on a vertical level and not show it in another instace of the object on a horizontal level.

I know Lee wondered the same thing but didn't know if he had shared any updates or you guys got any more information in this regard.  For example I know you can hide nodes from the menu provider but of course this would also hide them from the side menu that you wanted to invoke with the Level=child attribute as well. If you opted to display child nodes in main menu that it apparrently would display on both instances of the skin object and I am assuming would interact similarly with one instantiating being in the skin and one being on a modular level since both pull from the same structural engine. 

So I guess in closing my question do you know or have you guys heard of any way to achieve this where you can some how set an attribute either in the skin declaration of the menu system or the modular whereby you can opt to hide all child nodes only in a particular instance where as they will show in another instance so you could hover over a horizontal root node without a pull down showing of the child nodes click on it and either in a skin object or a module set to display child nodes and subchild nodes only of parent in the vertical layout where as in the horizontal layout no pull down will show.

Ok that is a load and a half I know but certainly something I am wondering about.

Thanks,

Bo