We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 8037
    • 10 Posts
    The examples given in the link above are nice and the information comprehensive, but you can’t deny that the amount of customization is quite staggering certainly for a new users. You have to read quite a lot of dry material to start to make sense of what in essence looks like a simple snippit call. It can get quite frustrating.

    I have been reading on and off for a few days and I can’t say that I get it completely, for instance; where do the tags and/or parameters come from that replace [+wf.classes+], [+wf.linktext+], [+wf.link+], [+wf.id+], just to name a few?
      • 24414
      • 45 Posts
      Unfortunately with the flexibility of Wayfinder we also get complexity. You need to have a bit more of a stare at the parameters there, as all the infomation is there. It may be all be a bit much to swallow at first, but when it all clicks it will make a lot more sense.

      From:
      http://www.muddydogpaws.com/development/wayfinder/parameters.html

      [+wf.classes+]
      Look at the last-but-one section in the parameters page – ’Class names to be assigned’.

      [+wf.linktext+]
      Have a look at ’&textOfLinks’ in the initial parameters section.

      [+wf.link+]
      This is an automatically generated path to your page.

      [+wf.id+]
      Have a look at ’&rowIdPrefix’.
        • 22770
        • 285 Posts
        Drewster, you’re quite right, it is extremely complicated and hard to work out. Some of it’s because there’s simply a hell of a lot you can do with Wayfinder, and some of it is because the documentation isn’t massively clear. One thing I did was to mock up a comprehensive-as-I-possibly-could navigation, creating chunks wherever they could be created, classes wherever they could be created, and so on. I didn’t use real html. I did things like:

        <this is the rowTpl[+wf.id+][+wf.classes+]><a href="[+wf.link+]" title="[+wf.title+]" [+wf.attributes+]>[+wf.linktext+]</a>[+wf.wrapper+]</this is the rowTpl>

        for the &rowTpl, and

        &hereClass=`hereClass`

        and so on, until I’d defined everything I could. Then I printed out the resulting code and stared at it until I figured out how it fitted together. It didn’t tell me everything I needed to know, but it gave me some clues. When I came to create real navigation, I figured out the rest of it.
          • 7231
          • 4,205 Posts
          wayfinder rocks, and there is some good instructions on using it available. However, it does take some effort to understand it and the methodology is approached from a developers point of view.

          I am new to WodX and am amazed at how cool this is. I am almost finished with my first ModX site and used wayfinder a lot for verious menus so I have become very familiar with it, and can tell you first hand that it can do plenty very well. Once I figured it out it is really easy and powerful. The documentation on the developers site was great in helping me get over the knowledge barrier.

          I do think that their could be a menu builder interface or something less technical to aid in building menus for the less tech savvy. What might help is a wizard to create wf calls. This would not be too hard to do and may help those with lesser tech skills (this would be cool for ditto as well, the instructions for ditto look a bit scary). Just a thought.
            [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&#39;t know what it is.
            Do you, Mr. Jones? - [bob dylan]