/files/ and all items within (both files and directories) should be set to be readable and writable by the web server. That can be accomplished in the following ways, from best to worst:
If your server supports running as suexec/phpsuexec, the files should be owned by your user account, and set as 755 on all of them. That means that your web server process can do anything it likes to them, but nothing else can (although everyone can view them, which is expected.)
If 1 isn't possible, another good option is to set the apache user (either "apache" or "nobody") as having full rights to these files
If neither 1 or 2 are possible, chmod 777 to files/ and all items within (e.g. chmod -R 777 file/*)
This must include the cache_objects directory, or you're going to get all kinds of strange behavior with your site.
Hello
I've stuck my updates/ directory at 777 because my stupid host won't give me SSH access to give ownership to the web server. This is clearly a security risk. What's the alternative? The server has mod_suexec installed.
Help would be much appre…
This can be a security risk, so I need to know - 755 do you mean every single file? image files, php files, css, every single file?
And when it says cmod 'files' to 777 there are several dir called files - does this mean every occurrence of dir 'files…
Sign In?
You must have a user account and be signed to perform this action.
