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

vqmod fails without issuing any warning #32

Closed
lorenzo-rovigatti opened this issue Apr 7, 2015 · 4 comments
Closed

vqmod fails without issuing any warning #32

lorenzo-rovigatti opened this issue Apr 7, 2015 · 4 comments

Comments

@lorenzo-rovigatti
Copy link

I use an svn repo to version my opencart website. I don't keep the vqcache/* and mods.cache files under versioning because they would constantly conflict with local versions. The last time I did a fresh checkout I first changed the permissions of the whole vqmod folder and then created the mods.cache file and then changed its permissions. Vqmod then stopped working without giving any log error whatsoever. It took me the best part of a hour to realise that the if statement in line 245 of the vqmod.php was leading to the "return" which prevented vqmod from working.
What I did was probably not good practice (since I don't really need to change permissions for the whole vqmod folder), but nevertheless I think that vqmod should either issue a warning or write something in the logfile when the mods.cache file should not be empty but it is.

@JAY6390
Copy link
Contributor

JAY6390 commented Apr 7, 2015

Hi

You shouldn't be creating the mods.cache file. This is why the vqmod folder itself needs to be writable. The same for checked.cache, and also so that the software can generate the necessary folders for logs/cache files

Kind regards
Jay

@JAY6390 JAY6390 closed this as completed Apr 7, 2015
@lorenzo-rovigatti
Copy link
Author

Fair enough. While I think that no codes should silently fail without issuing any warning, I see why I shouldn't create those files myself. thank you!

@JAY6390
Copy link
Contributor

JAY6390 commented Apr 8, 2015

Yes I understand what you are saying, it should do something at that point, though I'm not sure an error message is the best option. Perhaps it would be best to add in some code to disregard the cache file completely, and overwrite it. I think that was the original intention of the code there actually

Kind regards
Jay

@lorenzo-rovigatti
Copy link
Author

Yes, I think that could work. I know it's a very minor point, but I think that it may save other people from wasting time on it :-)
Thanks again!

best,
Lorenzo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants