Closed (fixed)
Project:
Boost
Version:
7.x-1.0-beta1
Component:
Installation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
5 Jul 2012 at 10:14 UTC
Updated:
3 Oct 2014 at 21:25 UTC
Jump to comment: Most recent
Comments
Comment #1
bgm commentedYou need to set permissions on the folder so that the user of the web server can write to it (www-data or httpd, depending on your setup/distribution).
Usually I set group ownership to www-data, and 0775 with g+suid:
http://en.wikipedia.org/wiki/Setuid#setuid_and_setgid_on_directories
Comment #3
asistentweb commentedI had the same problem. The simple solution was to just delete the cache folder and run the cron.
A new cache folder was created and everything is good now.
Comment #4
bgm commentedPlease update the handbook if you think something is missing.
Keep in mind that 6.x-1.x and 7.x-1.x are very different code bases, do not change the version of the issue.
Comment #5
blogers commentedYes the #3
work for me thanks
Comment #6
Anonymous (not verified) commentedIt doesn't solve "the problem" which is that there is no flaw in boost, only in the understanding of your VPS and file permissions. Check the new permissions and file ownership which will point you in the right direction.
Comment #7
socialnicheguru commentedThe permissions are 750.
In my case both owner and group had to be www-data on an ubuntu 14.04 system.
I had it as a-user:www-data but being part of the group is not enough.