We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 31902
    • 342 Posts
    Hey, folks.

    Probably just too easy for me to see, but I have a menu with a few dropdowns. On some of those, I need to have the top-level menu item NOT link to a page of any kind but still trigger the submenu it contains. What obvious thing am I missing?

    I’m using Revo 2.0.6 and Wayfinder 2.1.3. Menu works great...I just don’t know how to employ the above configuration.

    Thank you in advance.
      • 2894
      • 9 Posts
      First off, let me admit that I realize what I am about to say does not answer your question.

      Have you thought about having that top-level menu item go to a page that only contains links to the sub-menu items, possibly with a brief description of what they are? It seems like this would be helpful from a usability standpoint.
        • 31902
        • 342 Posts
        Quote from: bazzlevi at Jan 20, 2011, 12:19 PM

        ...Have you thought about having that top-level menu item go to a page that only contains links to the sub-menu items, possibly with a brief description of what they are? It seems like this would be helpful from a usability standpoint.

        I did...kinda, sorta. I originally had in mind some sort of intro area, anyway. It’s the client who is insisting on making the top level menu item dead like that. I’m stuck with that.
          • 2894
          • 9 Posts
          Quote from: waizen at Jan 20, 2011, 02:32 PM

          It’s the client

          GROANNNN....

          Again, not answering your question, but... how about making the top-level menu item a SYMLINK resource that points to the first sub-item. It’s still not completely dead, but at least it won’t go to some filler page...
            • 28042 ☆ A M B ☆
            • 24,524 Posts
            Here you go...
            &categoryFoldersTpl
            default: NULL
            values: name of template chunk
            description: The categoryFoldersTpl is used when the item is a folder, and either has the template set to
            blank or has rel="category" in the link attributes field. The children of the item must be displayed for this
            template to be used as well.
            available placeholders: Same as RowTpl.
              Studying MODX in the desert - http://sottwell.com
              Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
              Join the Slack Community - http://modx.org
              • 31902
              • 342 Posts
              Thank you, Susan, for responding.

              I’m new to ModX and I’m sorry for the stupidity, but how do I use the information below?

              Just to be clear, I do have other top-level menu items that I still want to go to pages, so I’m not looking for any solution that will render other top-level menu items to be made unlinkable. I need to have only a few top level menu items not go to pages because the client just doesn’t have content at this time for them.

              Quote from: sottwell at Jan 21, 2011, 02:21 AM

              Here you go...
              &categoryFoldersTpl
              default: NULL
              values: name of template chunk
              description: The categoryFoldersTpl is used when the item is a folder, and either has the template set to
              blank or has rel="category" in the link attributes field. The children of the item must be displayed for this
              template to be used as well.
              available placeholders: Same as RowTpl.
                • 31902
                • 342 Posts
                Okay, I found clarification for what Susan offered. Long story short, I found the answer in the Wayfinder E-book, starting on page 47. The e-book, by the way, can be downloaded here:

                http://modxcms.com/forums/index.php?action=dlattach;topic=34176.0;attach=9315

                BTW: if you use that e-book, please note that it seems to have been written for Evo...change tag formatting accordingly for Revo tags.

                Thank you to all who responded.
                  • 31902
                  • 342 Posts
                  Sorry to whine again, but I just ran into another small snag:

                  Yes, the main menu is working great...just how I want it, but I just noticed a problem with a second menu I have in the footer of the site. That menu is supposed to feature ONLY the top-level menu items...no submenu dropdowns. However, the top-level menu item in the footer menu is still linking to the page. I would like it to still be a dead link, just not have any dropdowns.

                  So, in my Wayfinder call within my footer chunk, I have this:

                  [[Wayfinder? &startId=`0` &level=`1` &categoryFoldersTpl=`catHeadings` &hideSubMenus=`TRUE`]]


                  This results in the top-level menu item in question still linking to a page.

                  Then, I change the call to:
                  [[Wayfinder? &startId=`0` &level=`2` &categoryFoldersTpl=`catHeadings` &hideSubMenus=`TRUE`]]


                  (notice the level change)

                  This makes that footer top-level menu item work fine (makes it into a dead link, like in main nav at top of page) but results in submenu items to permanently appear (not hide).

                  I played with different combinations of level numbers and TRUE or FALSE settings.

                  What am I missing?

                  BTW: It probably doesn’t matter, but the Wayfinder call for my upper navigation, which is working great, is:

                  [[Wayfinder? &startId=`0` &level=`3` &parentRowTpl=`cssplay_revParentRow` &cssTpl=`cssplay_ultdrop` &categoryFoldersTpl=`catHeadings`]]
                    • 28042 ☆ A M B ☆
                    • 24,524 Posts
                    description: The categoryFoldersTpl is used when the item is a folder, and either has the template set to
                    blank or has rel="category" in the link attributes field. The children of the item must be displayed for this
                    template to be used as well.
                    I would leave the footer menu with a level=2, then use CSS to permanently hide the children.
                      Studying MODX in the desert - http://sottwell.com
                      Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                      Join the Slack Community - http://modx.org