We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

wayfinder and parent

    • 3719
    • 13 Posts
    Bobby D Reply #1, 17 years, 7 months ago
    This one’s got me stumped - I must be missing something incredibly obvious but:

    Using Wayfinder to build a simple sub menu, I use the following snippet call:
    [[Wayfinder? &startId=`[*parent*]` &level=`1` &firstClass=`first`]]

    No menu is built and using the debug parameter I get "no documents found for menu". If I subsitute a document number instead of [*parent*], it’s fine, and using [[UltimateParent]] snippet as startId also works.

    So what am I doing wrong in my use of `[*parent*]` for the startId parameter? I’ve used it before on other modx builds just fine....

    Grateful for any suggestions!
      • 7231
      • 4,205 Posts
      dev_cw Reply #2, 17 years, 7 months ago
      It should work. As a test check to see if [*parent*] is outputting a value.
        [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]
        • 3719
        • 13 Posts
        Bobby D Reply #3, 17 years, 7 months ago
        parent is outputting the correct value.

        Could it be an issue with this version of modx? The site I have the issue with is running 0.9.6.3 and the site where it’s working OK is running 0.9.6.1p2
          • 36592
          • 970 Posts
          tkfm Reply #4, 17 years, 7 months ago
          I’m not sure but why don’t you chage the type of snippet call from [[...]] to [!...!] ?
            • 3719
            • 13 Posts
            Bobby D Reply #5, 17 years, 7 months ago
            That’s done it! I was tearing my hair out - clearing the cache manually hadn’t worked but that has it sorted.

            Thank you very much! smiley