We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 1212
    • 4 Posts
    Hi all,
    So far I used wayfinder in some installations, and it worked like a charm, even when separating top- and subnavigation, and connecting the later to the active element in the topnavigation with the help of ultimateparent.

    However, for the first time I try to render a more simple navigation, that is my two navigation levels in a navigationbox at the left, all levels and subnavigations expanded. I thought this was a simple task, and added this for building the navigation in the template:

    [[!Wayfinder? &startId=`0` &level=`2` &hereClass=`currSelected`]]
    


    This works partially wonderful. However, I observed, that the navigation tree doesn’t get updated after inserting a new resource document. But if I click on "preview" the correct navigation tree is shown, but after moving to another navigation entry the "old" navigation tree without the node related to the newly inserted document is shown. Only on very rare occassions the navigation will remain correct after moving to another nav entry, but I couldn’t see any pattern. Emptying the cache doesn’t help, but looking at the website six hours later (after the night, with a possible server restart?) the navigation tree is shown correctly in all cases.

    I have this type of navigation rendered in a box at the left:
    Home
    page a
      page a2
    page b
      page b2
    


    After guessing obviously wrong that the root cause might be a broken installation I even reinstalled modx, but the behaviour didn’t change at all.

    Any help would be greatly appreciated. I must have overseen something (no?).

    Regards
    almo
      • 18463
      • 121 Posts
      Martijn van Turnhout Reply #2, 15 years, 5 months ago
      Hi alom,

      which version of MODx are you using? A lot of people are having trouble with Wayfinder and MODx Revo RC3. See https://github.com/splittingred/Wayfinder/issues/27
        • 1212
        • 4 Posts
        Sorry, forgot that: modx 2.0.8pl and wayfinder 2.3.0 Apr 30 2011.
          • 18463
          • 121 Posts
          Martijn van Turnhout Reply #4, 15 years, 5 months ago
          You could add a comment to the issue above. Perhaps the whole caching bug gets fixed then. I’ve got the same problem.
            • 1212
            • 4 Posts
            Well, it seems there is simple "fix" or "workaround", at least. I added a wayfinder-call combined with UltimateParent to the template:

            [[!Wayfinder? &startId=`[[UltimateParent?topLevel=`2`]]`]]
            


            I could put this in a zero-dimensioned div, and as modx will not evaluate visibility, it should workd. Now, once I invoke a page the menu gets refreshed faster, possibly after a second call.