Display a children menu not of the current asset

I want to have two menus appear on every page. One is the standard top level menu - no problems with that one.


The other menu will have different styling and is going to be a quicklaunch kind of menu. I have the assets for the quicklaunch items in a separate folder. How can I make a menu from these items so that it appears on every page? Is there any way of setting a children menu to start at a different asset from the current one? Do I need to nest this from somewhere else? Appreciate any suggestions…



Thanks,



Peter

You could use a nested asset listing to make it appear like a menu OR, if you can run 3.14, you can tell a menu to start at a particular asset.


Here is the feature announcement from the developer newsletter:


[quote]    EXPLICIT ROOT NODE IN NORMAL MENU

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

        Added to: 3.13.0 development



        The Normal Menu (or rather, menu_normal) design area now accepts an

        optional explicit root node. This removes the requirement for a

        workaround using, for example, nested asset listings to display a menu

        from a certain point. It also allows styling for current and hierarchy

        attributes, which was not readily possible previously (however, for this

        to work, the root node must be within the same site as the asset being

        displayed).



        The root node can be specified in a customised design area's Details

        screen, or through the parse file using the following code:



        <MySource_SET name="root_node" value="1234" />



        Where the value attribute specifies the asset ID of the root node.



        Please note that you must also set the "menu_level" parameter to "top"

        for this feature to work. Also please note that compared to a normal

        menu set-up, it will run slightly slower due to the requirement to find

        the current asset lineage based on URL. However, it may still be quicker

        than the aforementioned workaround.[/quote]

Great, thanks Greg. We're still in an early stage of development, so the 3.14 sound just like what I need.