-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"cache path not defined for compiled files" #478
Comments
I'm able to reproduce this in users sites (by clearing cache or just by waiting long enough), but not in my local environment. Not sure what is causing this, but it has already happened for at least 3 people. |
Its happening to only one of my sites too, but not to the other 4 i have on g5. Really strange, not sure what the difference between them is :( |
We have the same issue as well with one of our client sites. Let me know if you would like me to make it available to you. We can spin up a server with a copy of the site, and give you full access if need be. We're entirely baffled by this bug. |
Can you guys try something for me before I'm going to make more radical change to fix this? Can you move this line 2 lines up to be the first thing in the class? Not sure if it fixes the issue, but for some reason that variable cannot be found and it may be because of the wrong ordering... |
I'm trying that now and will report back with results soon |
Just tried it, no luck here. Thanks for the effort. |
Also, a strange addition to this, which is something I noticed much by accident when it started. At least in my case, when the error appears. If I refresh the page the error appears again. However, if I hold the F5 button for about 3-4 seconds and refresh rapidly. The page will appear without error. I'm not joking, and I have no idea what to make of that. @GospelPowered try it on your end, I'm curious if that's specific to my issue. Thanks! |
Hey @hiddenmagic that is strange. For me it works just fine when i refresh it again, the error page only appears when i first go to the site and then on refresh the site loads fine for a while. I don't need to hold F5 or refresh multiple times. |
@hiddenmagic We are just talking on this in Gitter chat (private one). If you want to join, we can continue in https://gitter.im/gantry/gantry5 |
Curious. Well, it's a mystery to us, but we're in good hands for sure. |
Looks like the issue has been fixed. @hiddenmagic has also another issue, which I'm looking now. Closing the issue, be free to reopen if the above issue gets back. |
Awesome thanks @mahagr |
|
@hiddenmagic Your second issue seems to be related to cart clearing up all directories in So it's likely a misconfiguration -- not issue in G5. I'm adding a bit better error message to point to the issue, though. |
"Looks like the issue has been fixed. @hiddenmagic has also another issue, which I'm looking now. I have the issue that was raised by #478 can someone explain how to fix this? Thanks! |
Try installing the CI Builds, you can find more details about what they are and how to use them here: http://gantry.org/blog/gantry5-ci-builds You can find the packages in the Downloads section under CI Builds (http://gantry.org/downloads#ci-builds) |
i downloaded the latest and installed. I received a different error this time. An exception has been thrown during the rendering of a template ("Who just removed Gantry 5 cache folder? Try reloading the page if it fixes the issue") in "@nucleus/content/spacer.html.twig" at line 1. |
Yup, you have the same error as @hiddenmagic, some extension keeps removing every extra folder in your Joomla cache directory. Check if you have K2 Store component. This was the offending line for him: /components/com_k2store/controllers/mycart.php Line 46: K2StoreUtilities::cleanCache(); Gantry 5 relies on compiling most files into PHP, so component or plugin doing this would make the site to load slow even if I worked around the issue. |
There is still some bug causing first load to fail for some people. |
User is now reporting following issue instead: |
Looks like this one was wrong alarm: user reported that he fixed the issue by reinstall. |
A number of members on RT forum are reporting that they are getting the above fatal error on the front-end of their sites. Usually clearing cache makes the error go away only for it to return again later.
I have discussed this at length with @mahagr and he has all the details of member sites to investigate further. As yet neither of us can reproduce this issue on our local systems.
The text was updated successfully, but these errors were encountered: