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...
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.
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.