We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 19329
    • 12 Posts
    I have one directory on my site that has heaps of pages in it, and it will get a lot more in the future.

    Using Wayfinder, I have the side navigation set up:
    http://www.granitenet.com.au/groups

    But it’s a little unwieldy already, and will just get more so in the end. Any tips on making this a bit easier to navigate?

    I was thinking to put some pages in further subdirectories, but I can see that will just cause so many headaches in the future.

    I was wondering if there was a way to not show the sister/same level pages in this directory only. So the groups would be listed in the main content of that page, but not show up in the side navigation.

    And then when you click on one of the groups, then it would just show it’s parents and it’s own children in the menu, but not the other sister/same level pages.

    Is this possible?

    Thanks,

    Michelle
      • 7231
      • 4,205 Posts
      You can set a level parameter to limit how deep Wayfinder goes into the menu:
      &level
      default: 0
      values: [ 0 | number ]
      description: The level parameter determines how deep into the tree structure Wayfinder will process. If set to 0, Wayfinder will process all levels of the document tree.

        [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

        Something is happening here, but you don't know what it is.
        Do you, Mr. Jones? - [bob dylan]
        • 19329
        • 12 Posts
        Quote from: dev_cw at Dec 07, 2008, 05:53 AM

        You can set a level parameter to limit how deep Wayfinder goes into the menu:
        &level
        default: 0
        values: [ 0 | number ]
        description: The level parameter determines how deep into the tree structure Wayfinder will process. If set to 0, Wayfinder will process all levels of the document tree.



        thanks, but I do still need the menus at this level, just not all the other pages listed.
          • 7231
          • 4,205 Posts
          Then I do not understand the question.

          You can turn off the "Show in menu" option for the documents you wish to hide.
            [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

            Something is happening here, but you don't know what it is.
            Do you, Mr. Jones? - [bob dylan]
            • 19329
            • 12 Posts
            I guess I haven’t made myself clear.

            I do still want other pages to show menus, so I don’t want them turned off forever, just within this one directory I don’t want all the other menu options showing, as it’s really long already and will get even longer.

            I guess it can’t be fixed and will have to think up other ways to tackle it.

            Michelle
              • 20413
              • 2,877 Posts
              In order to hide parents you can make weblink documents "out in the free"
              to call.
                @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
                Michelle,

                I didn’t really understand your question but have you tried using the wayfinder parameters &excludeDocs or &includeDocs ? The former

                &excludeDocs
                Use this if there are certain documents you don’t want listed under any condition, then you can list them in this parameter and WayFinder will exclude them from its output. The startId is still required

                &includeDocs
                Acts as a filter and will limit the output to only the documents specified in this parameter. The startId is still required. So, if you want, for instance, to have only documents with IDs 1, 5, and 10 shown in your menu, you would specify in your Wayfinder Snippet call &includeDocs=`1,5,10`

                I suppose knowing which one to use is the question. I would use the one that would require the least typing wink It is a good idea to note the document ids of the files you have excluded/included and the reasons why you have done this. This will help you down the line when you come back to look at your code...

                Hope this is what you are looking for and it is helpful.....

                cheers/k
                  • 19329
                  • 12 Posts
                  What does ’out in the free’ mean?

                  I’ll try to explain my question a bit clearer.

                  Currently the website has this setup
                  Root
                  -Home
                  -About
                  -Groups
                  -etc..

                  When on the home page that’s all that needs to be shown, hence I’m using &hidesubmenus=`true` and &startid=`[*parent*]

                  When you click on Groups you get the following
                  Groups
                  -Group1
                  -Group2
                  -Group3
                  ...
                  -Group55

                  Some of these groups have submenus and some don’t. The desired result is that when you click on a group you get only the menu for that group.

                  So the current problem is that when you click on a sub group, you get

                  Groups
                  -Group1
                  -Group2
                  -Group3
                  --Group3Item1
                  --Group3Item2
                  --Group3Item3
                  -Group4
                  ...
                  -Group 55

                  What I want is

                  -Group3
                  --Group3Item1
                  --Group3Item2
                  --Group3Item3

                  Which I have achieved by setting &startid=`[*id*]`

                  However, this now means that when a user clicks on Group3Item2 for example, they get no menu at all, so now I would need to set &startid=`[*parent*]`

                  And now I’m back to the original problem of *all* the groups being displayed, described above.

                  So now I have a situation where I have to either manually specify a startid for each individual page or live with the problem.

                  Ideally, I would like some way to determine what is the level of the current page and have the startid change accordingly. ie. if level 2 (ie, Group3) then startid=id else startid=parent.

                  I hope that makes more sense.

                  Michelle
                    • 16183
                    • 1,390 Posts
                    I’m having three quick random untested initial thoughts:

                    1. use the snippet ultimate parent. I think it would work in this case?

                    2. use javascript accordion menu - e.g. some jQuery menu...

                    3. use PHx

                    There’s probably another way...if I think of anything else will post here..

                    /k
                      • 20413
                      • 2,877 Posts
                      I dunno to help you with your approach other then suggest you to use different templates and
                      have the wayfinder call inside of them. So you can remain some kind of control.

                      With weblinks you can design a menu inside a tree. Have a folder(startId) with additional some folders and in all these folders
                      "create weblink here" to existing docs.

                      If I were you I would grab a pencil and draw what I want, and draw what different solutions do...
                        @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