We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 41295
    • 1 Posts
    Hi, I need help with wayfinder menu in revo.

    I want to make this kind of menu with non-clickable categories

    Category1:
    -resource_1
    -resource_2
    -etc-

    Cateogry2:
    -resource_a
    -resource_b
    -etc.

    Caterogy3:
    -etc...

    Categories are parent resources of my resources.

    Could someone give me code needed. I just can't get it work on my own. smiley
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      1. In the parent resource's Link Attribute field, put
      rel="category"


      2. Create a new chunk with the structure you want for these items, for example:
      <li[+wf.classes+]><span> [+wf.linktext+]</span>[+wf.wrapper+]
      </li>

        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
        • 8822
        • 203 Posts
        Hi Susan, how does this work in touch devices such as ipads/iphones - if the parent menu item is not clickable how can it display the child menu items in ipads/iphones, where the parent menu item must be clicked in order for the sub menu items to be displayed. I am currently using &parentRowTpl referencing the chunk
        <li class="nonlinkitems">[[+wf.linktext]][[+wf.wrapper]]</li>
        but have a problem on the iphone/ipad......
          • 42562
          • 1,145 Posts
          @Susan Does this work in Revo, rel="category"?

          Never seen it before now. Probably the one feature I bat hovered.
          I am going to try it out.

          I have been using weblinks as my menu parent, and for organisational purposes in the resource tree.
          Now I am going to try the rel="category"

          weblink1 (href="#")
          -Resource One
          -Resource two

          weblink2 (href="#")
          -Resource three
          -Resource four

          @Emily Won't this work?
          <li class="[[+wf.classnames]]"><a href="#">[[+wf.linktext]]</a>[[+wf.wrapper]]</li>
          //or <a href="javascript:void(0)"> or better still using unobtrusive javascript
          It is a clickable link, even in IPAD, but it won't go anywhere.
            TinymceWrapper: Complete back/frontend content solution.
            Harden your MODX site by passwording your three main folders: core, manager, connectors and renaming your assets (thank me later!)
            5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
            • 8822
            • 203 Posts
            Thanks for responding... tried:

            <li class="[[+wf.classnames]]"><a href="#">[[+wf.linktext]]</a>[[+wf.wrapper]]</li>


            but that provides a link back to the home page? I thought <a href="#"> was supposed to do nothing?
              • 42562
              • 1,145 Posts
              Yup, it is supposed to do nothing...sometimes it fails according to how your setup is....
              use <a href="javascript:void(0)"> to kill it altogether
                TinymceWrapper: Complete back/frontend content solution.
                Harden your MODX site by passwording your three main folders: core, manager, connectors and renaming your assets (thank me later!)
                5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
                • 8822
                • 203 Posts
                Great - thanks! javascript did the trick smiley
                  • 42562
                  • 1,145 Posts
                  I just tested this rel="category" thing, it does work.
                  So now I can use a resource as just a parent...only major drawback seems to be that although I set the template to empty the resource still exists...so if someone were to find the correct url to that empty resource, the empty page would show. up...bad bad bad!

                  So I am stuck with using weblinks instead of something better.

                  It would be cool if MODx had:
                  1. Document
                  2. Weblink
                  3. Symlink
                  4. Static Resource
                  5. Category resource
                    TinymceWrapper: Complete back/frontend content solution.
                    Harden your MODX site by passwording your three main folders: core, manager, connectors and renaming your assets (thank me later!)
                    5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
                    • 28042 ☆ A M B ☆
                    • 24,524 Posts
                    I don't see why that's so "bad" - if somebody is fiddling around with manually entering URLs and stumbles on it, then they deserve whatever they get. Besides, you could always put a redirect snippet in its content to ship the snoopy user off to some other page.
                      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