We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 10867
    • 5 Posts
    I downloaded and installed Wayfinder 2.1 via the package installed on a new MODx Revolution install (2.0.0-beta-5 rev6224) and I am having issues getting it to work.

    I have placed the following in my template:

    [[Wayfinder? &startId=`0` ]]


    and I get "error: Wayfinder class not found"

    I have also tried placing the same code in a chunk (called Header) and tried calling that in the template (as [[$Header]]) and I get the same error.

    I’m new to MODx and I am having a hard time debugging the issue. Any ideas?
      • 10867
      • 5 Posts
      Ok... I fixed the problem. The error logs show that the expected directory for wayfinder was /core/components/wayfinder

      The wayfinder install from the package manager was in /core/packages/wayfinder-2.1.1-beta4/modSnippet/somecrazyhash/0/wayfinder

      I copied the wayfinder directory from the packages directory into a newly created components directory and everything works...

      So - does that mean that the package installer didn’t actually install anything? Obviously it downloaded it... but should the path really be /core/packages/wayfinder instead of /core/components?

      I’m a bit confused and I feel like a bug report needs to be filed - just not sure if it’s a revolution bug or a wayfinder bug...
        • 1331
        • 129 Posts
        I went and created a folder at /core/components and set it to 777 before installing and it worked. I still got an error message during install, but the Wayfinder class worked without my having to manually move anything.
          • 3749
          • 24,544 Posts
          It looks like you solved it. FYI, no working components will be installed in the core/packages directory. It’s only for packages, and preserved previous versions of packages. Stuff gets put there sometimes during installation before being moved to it’s official spot. That’s what the crazy hash was (actually, I think it’s just a unique identifier to make sure different versions of the same package files don’t get mixed up).

          Those files should have been copied to the "official" location. Usually, some parts of the package will go to core/components/packagename, others to assets/componenents/packagename, so both need to be writable or you will have trouble with other packages.
            Did I help you? Buy me a beer
            Get my Book: MODX:The Official Guide
            MODX info for everyone: http://bobsguides.com/modx.html
            My MODX Extras
            Bob's Guides is now hosted at A2 MODX Hosting