After upgrading wayfinder to 2.2.0 we got on every load of so far uncached pages the error "(ERROR @ /index.php) Could not load context:" in the error-log.
Does anybody know what is the reason for this or what we can do to avoid this error?
Letti
-
☆ A M B ☆
- 571 Posts
Hello,
i found out that adding the parameter &context=`*your context name key*` reduced the number of errors (but there are still some).
I guess that’s because of the introduction of new parameters.
Hi Romain,
do you nevertheless use the new wayfinder-version? Or do you think the errors in the error-log are not of relevance?
For now, just add this parameter to your call:
&contexts=`web`
I’ll have a patch out tomorrow morning. Thanks!
shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect |
github |
splittingred.com
This has been fixed and 2.2.0-pl has been released.
shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect |
github |
splittingred.com
The cache is automatically active, as &cacheResults is set to 1 by default. It generates a cache based a combination of your configuration and the Resource it shows on; so if you change a parameter on the Wayfinder call, it will cache it as a different file.
shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect |
github |
splittingred.com
Is there a way to clear the wayfinder-cache which is implemented in the new wayfinder-upgrade? When we add or remove resources we don´t see any changes in the menu even when we clear the global cash by ctrl+shift+u. Does anybody know how to clear the wayfinder-cache specifically?
Letti
-
MODX Staff
- 10,725 Posts
Just disable it if it’s not working for you. It’s redundant caching in most cases anyway.