Skip to content
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

Closed
marktaylor46 opened this issue Jun 17, 2015 · 22 comments
Closed

"cache path not defined for compiled files" #478

marktaylor46 opened this issue Jun 17, 2015 · 22 comments
Assignees
Labels

Comments

@marktaylor46
Copy link

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.

fatal

@mahagr mahagr added the bug label Jun 17, 2015
@mahagr mahagr added this to the Release Candidate 4 milestone Jun 17, 2015
@mahagr
Copy link
Member

mahagr commented Jun 17, 2015

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.

@igor-gp
Copy link
Contributor

igor-gp commented Jun 20, 2015

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 :(

@hiddenmagic
Copy link

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.

@mahagr
Copy link
Member

mahagr commented Jun 22, 2015

Can you guys try something for me before I'm going to make more radical change to fix this?

https://github.com/gantry/gantry5/blob/develop/src/classes/Gantry/Component/File/CompiledYamlFile.php#L23

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

@igor-gp
Copy link
Contributor

igor-gp commented Jun 22, 2015

I'm trying that now and will report back with results soon

@hiddenmagic
Copy link

Just tried it, no luck here. Thanks for the effort.

@hiddenmagic
Copy link

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!

@igor-gp
Copy link
Contributor

igor-gp commented Jun 22, 2015

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.

@mahagr
Copy link
Member

mahagr commented Jun 22, 2015

@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

@hiddenmagic
Copy link

Curious. Well, it's a mystery to us, but we're in good hands for sure.

mahagr added a commit that referenced this issue Jun 22, 2015
@mahagr
Copy link
Member

mahagr commented Jun 22, 2015

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.

@mahagr mahagr closed this as completed Jun 22, 2015
@igor-gp
Copy link
Contributor

igor-gp commented Jun 22, 2015

Awesome thanks @mahagr

@igor-gp
Copy link
Contributor

igor-gp commented Jun 22, 2015

crikey there was an error
Its back again however slightly different now, as discussed with @mahagr

@mahagr
Copy link
Member

mahagr commented Jun 22, 2015

@hiddenmagic Your second issue seems to be related to cart clearing up all directories in /cache on every page load. Because of that the directory gets created before component gets rendered, but is being removed before Gantry 5 tries to use it.

So it's likely a misconfiguration -- not issue in G5. I'm adding a bit better error message to point to the issue, though.

@Christianlocal
Copy link

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

I have the issue that was raised by #478 can someone explain how to fix this? Thanks!

@w00fz
Copy link
Member

w00fz commented Jun 23, 2015

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)

@Christianlocal
Copy link

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.

@mahagr
Copy link
Member

mahagr commented Jun 23, 2015

@Christianlocal

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.

@igor-gp
Copy link
Contributor

igor-gp commented Jun 23, 2015

This is another error i got.
crikey there was an error3

@mahagr mahagr closed this as completed in 22560ee Jun 23, 2015
@mahagr
Copy link
Member

mahagr commented Jun 23, 2015

There is still some bug causing first load to fail for some people.

@mahagr mahagr reopened this Jun 23, 2015
@mahagr
Copy link
Member

mahagr commented Jun 27, 2015

@mahagr mahagr reopened this Jun 27, 2015
@w00fz w00fz modified the milestones: Release (5.0.0), Release Candidate 4 Jul 6, 2015
@mahagr
Copy link
Member

mahagr commented Jul 9, 2015

Looks like this one was wrong alarm: user reported that he fixed the issue by reinstall.

@mahagr mahagr closed this as completed Jul 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants