We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 20765
    • 90 Posts
    myfriendscallmebill Reply #1, 18 years ago
    Here’s my setup:
    o MacOS X, v10.5.5
    o Safari 3.1.2
    o MODx 2.0.0 a5
    o Wayfinder 2.0-beta

    I’ve created a trivial template:
    <html><head></head><body>
    [[*content]]
    <hr />
    [[wayfinder? &startId=`10` &debug=`TRUE`]]
    </body></html>

    I’ve created a simple website where all the resources are published:
    web
    firstcontainer (10)
    firstpage (1)
    secondpage (2)
    thirdpage (3)

    The content of firstpage is:
    <p>Hello, my ID is [[*id]]</p>

    When I access the website firstpage displayed. It contains:

    o The opening message (Hello, my ID is 1)
    o The horizontal rule
    o An error string from wayfinder in red "No documents found for menu."
    o All the wayfinder debug readouts.

    Whether I set startId to 1 or 10 I get the same results. I’d expected to see a list of page titles using wayfinder’s default templates. I’ve cleared the cache between trial runs.

    Can anyone tell me what I’m missing?
      • 22303 MODX Staff
      • 10,725 Posts
      Are you sure you don’t have the Resource with the cacheable Wayfinder call set to cached?
        • 20765
        • 90 Posts
        myfriendscallmebill Reply #3, 18 years ago
        Quote from: OpenGeek at Oct 12, 2008, 02:41 PM

        Are you sure you don’t have the Resource with the cacheable Wayfinder call set to cached?

        topcontainer, firstpage, secondpage and thirdpage all had their "cacheable" checkboxes checked. I unchecked them. The Wayfinder call in my template is...
        [[wayfinder? &startId=`10` &debug=`TRUE`]]
        ...which I don’t think is the cacheable form of a snippet call, is it? (by the way, what’s the new syntax for making a snippet call cacheable?) Did I miss anything?
          • 7923
          • 4,213 Posts
          Quote from: myfriendscallmebill at Oct 12, 2008, 03:08 PM

          The Wayfinder call in my template is...
          [[wayfinder? &startId=`10` &debug=`TRUE`]]
          ...which I don’t think is the cacheable form of a snippet call, is it? (by the way, what’s the new syntax for making a snippet call cacheable?) Did I miss anything?
          That is a cached snippet call. Use exclamation mark after opening revolution tag to make any tag uncached, eg:

          [[!wayfinder? &startId=`10` &debug=`TRUE`]]

          or:

          [[!$chunk]] or [[!*templatevar]] or [[!+placeholder]]... etc.


            "He can have a lollipop any time he wants to. That's what it means to be a programmer."
            • 20765
            • 90 Posts
            myfriendscallmebill Reply #5, 18 years ago
            Quote from: doze at Oct 12, 2008, 03:33 PM

            Use exclamation mark after opening revolution tag to make any tag uncached, eg:

            [[!wayfinder? &startId=`10` &debug=`TRUE`]]

            or:

            [[!$chunk]] or [[!*templatevar]] or [[!+placeholder]]... etc.

            Thanks for telling me the syntax for un-caching. I tried it, but it still doesn’t work. I also tried eliminating the ampersand before startID ( [[!wayfinder? startId=`10` &debug=`TRUE`]] ) and that didn’t help. Any other suggestions...?
              • 22303 MODX Staff
              • 10,725 Posts
              Quote from: myfriendscallmebill at Oct 12, 2008, 04:55 PM

              Any other suggestions...?
              Did you clear the site cache?
                • 20765
                • 90 Posts
                myfriendscallmebill Reply #7, 18 years ago
                Quote from: OpenGeek at Oct 12, 2008, 05:55 PM

                Did you clear the site cache?

                Yes, I always clear the site cache after every change. I also refresh the page two or three times in the Safari browser to clear the browser cache.
                  • 28215
                  • 4,149 Posts
                  splittingred Reply #8, 18 years ago
                  As a test, try setting: &level=`1`

                  If that doesn’t work, can you verify that the resources don’t have the ’Hide from Menus’ checkbox checked?
                    shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                    • 20765
                    • 90 Posts
                    myfriendscallmebill Reply #9, 18 years ago
                    Quote from: splittingred at Oct 12, 2008, 11:47 PM

                    As a test, try setting: &level=`1`

                    That made it work! Then I did an experiment -- I created a three-level hierarchy of resources and set ’&level’ to different values:

                    &level=`0` --> Got the "No documents found for menu." message.
                    &level=`1` --> The first level of the hierarchy was shown.
                    &level=`2` --> The first two levels of the hierarchy was shown.
                    &level=`3` --> The first three levels of the hierarchy was shown.
                    &level=`99` --> The first three levels of the hierarchy was shown.

                    So it looks like (at least at present) you absolutely have to assign a value to this parameter, and it has to be at least as big as the number of levels you need to display.

                    Thanks!


                      • 6038
                      • 228 Posts
                      thanks - this worked for me also.

                      Setting level=`0` produces nothing, but setting to a positive value will give results.
                      I assume this is a bug which is being fixed?