We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 11773
    • 54 Posts
    Sorry, my mistake...again! Does that look better...

    -------Parent (15)
    -------------Grand/Child 1 (12)
    -------------Grand/Child 2 (22)
    -------------Grand/Child 3 (14)
    -------------Grand/Child 4 (24)
    -------Parent (16)
    -------------Grand/Child 1 (17)
    -------------Grand/Child 2 (23)
    -------------Grand/Child 3 (18)
    -------------Grand/Child 4 (25)
      • 16183
      • 1,390 Posts
      Quote from: happyavocado at Nov 04, 2008, 10:44 AM

      Sorry, my mistake...again! Does that look better...

      -------Parent (15)
      -------------Grand/Child 1 (12)
      -------------Grand/Child 2 (22)
      -------------Grand/Child 3 (14)
      -------------Grand/Child 4 (24)
      -------Parent (16)
      -------------Grand/Child 1 (17)
      -------------Grand/Child 2 (23)
      -------------Grand/Child 3 (18)
      -------------Grand/Child 4 (25)

      I still don’t understand the question unfortunately. Let’s make this clearer. Let’s give the documents names like below and then please ask the question again... I think it is better that way (or you can attach a screenshot of your document tree and ask the question again)

      Here’s the mock document tree

      -------About us(15)
      -------------Members (12)
      -------------History (22)
      -------------Contact (14)
      -------------Partners (24)
      -------Products (16)
      -------------Nintendo (17)
      -------------Sony (23)
      -------------Xbox  (18)
      -------------Gphone (25)
      


      In the above scenario, which documents should be shown and which ones should be hidden and at what instances?

      Hope this time we understand each other... wink
        • 5340
        • 1,624 Posts
        &startId
        default: the current document id
        values: [ 0 | a document id | [*parent*] | [*id*] ]
        description: The startId parameter determines where Wayfinder should start processing the output. All documents contained within the startId will be processed. For a menu to start from the root of the site the startId should be set to 0.
          • 11773
          • 54 Posts
          Taking your example....

          -------About us (15)
          -------------Members (12)
          -------------History (22)
          -------------Contact (14)
          -------------Partners (24)
          -------Products (16)
          -------------Nintendo (17)
          -------------Sony (23)
          -------------Xbox (18)
          -------------Gphone (25)

          I have one horizontal menu that outputs the parents, in this case "About us" and "Products" and I have another menu in a horizontal line underneath this which shows only the children of that parent. So, for example, when on the Members page the submenu will only show Members, History, Contact and Partners, and when on, for example, Nintendo, the submenu will only show Nintendo, Sony, Xbox and Gphone.

          I originally tried to make this work by using the "&innerTp" parameter but couldn’t get it to work. I am going to have another play around with it now, but any help is much appreciated.

          I would love to attach a screenshot of my document tree but I am in the process of playing around with it before trnasfering my site over, and it just looks a mess with lots of pages named test1, test2 etc!

          Thanks again Kongondo for your help smiley Fingers crossed it makes sense this time.
            • 16183
            • 1,390 Posts
            OK, I think I get you now, hopefully...

            1) Will "About us" and "Products", i.e. the parents always be visible in the main horizontal menu?
            2) and do you want to hide the horizontal  sub-menus underneath, i.e. the children of these two parents ("About us" and "Products") and only show them, i.e. the children only when their parents are active?

            If this is the case, then you need to set the parameter hideSubMenus to true like so in your WF snippet call

            &hideSubMenus=`1`


            Hope I understood you this time. If you set this parameter to true as shown above, WF only displays the immediate children (if any) of the currently displayed page....meaning, there has to be a parent - child hierarchy to see the effect fully (I think?).

            What would happen is that if the menu "About us" is active, only its children ("member", "history", etc) will be visible in the second horizontal sub-menu but the children of the parent "Products" (i.e. "Nintendo", etc ) will not be visible until their parent "Products" is active. Did i get you right?
              • 20413
              • 2,877 Posts
              A cheap trick to above: I sometimes set up a folder tree with weblinks to choosen docs and folders!
                @hawproductions | http://mrhaw.com/

                Infograph: MODX Advanced Install in 7 steps:
                http://forums.modx.com/thread/96954/infograph-modx-advanced-install-in-7-steps

                Recap: Portland, OR (PDX) MODX CMS Meetup, Oct 6, 2015. US Bancorp Tower
                http://mrhaw.com/modx_portland_oregon_pdx_modx_cms_meetup_oct_2015_us_bancorp_tower
                • 16183
                • 1,390 Posts
                Quote from: mrhaw at Nov 04, 2008, 02:43 PM

                A cheap trick to above: I sometimes set up a folder tree with weblinks to choosen docs and folders!

                @mrhaw
                Don’t quite get you...please explain. I might need the trick in the future, thanks.

                  • 11773
                  • 54 Posts
                  Yes, it would be good to understand that trick more - it’s gone straight over my head!

                  Kongondo - I really appreciate your help with all of this!

                  Yes, all that you said in your las post is exactly what I am trying to achieve. My Wayfinder call looks like this now:

                  [[Wayfinder? &startId=`0` &level=`2` &hideSubMenus=`1` &fullLink=`1` &outerTpl=`outer` &innerTpl=`inner &rowTpl=`row` &outerClass=`navigation` &innerClass=`subnavig’]]

                  The problem I’m having is that my sub navigation (called "subnavig") is outputted inside my main naviagtion (called navigation) instead of below it. Is there a "fix" for this?

                  Many thanks again! smiley
                    • 22840
                    • 1,572 Posts
                    did you copy and paste the wayfinder call ??

                    if so there is a error in it that may be causing problems " &innerTpl=`inner &rowTpl=`row` " should be " &innerTpl=`inner` &rowTpl=`row` "
                      • 16183
                      • 1,390 Posts
                      Quote from: paulp at Nov 04, 2008, 03:14 PM

                      did you copy and paste the wayfinder call ??

                      if so there is a error in it that may be causing problems " &innerTpl=`inner &rowTpl=`row` " should be " &innerTpl=`inner` &rowTpl=`row` "

                      If this doesn’t solve it then paste your template chunks here too. Maybe you have placed a wrapper place holder in the wrong place or something?

                      hint: for better readability of your post, please wrap the WF calls, chunks, etc between code tags

                      cheers/f