Error: Catalog images directory is not writeable:

[JRR]

OK, now this is irritating! I have CHMOD the images directory in my catalog to 777, double checked it, I can also view the contents of the image directory using my browser.

However when I run admin: Categories / Products I get repeating error lines stating:

Error: Catalog images directory is not writeable: /usr/www/users/xxxx/catalog/images/

Tried clearing and resetting the permissions, still get the same result. This is the only permission problem that I appear to have, reviewed all other admin functions and none complain...

Should this program be looking for images in the root /users/xxxx/catalog or should it be looking in /flippers/catalog? Perhaps a script error??

Where would I look to find this? In the Config.php files? I guess I should learn more about the underlying structure, but that takes time - and I don't have a lot of that.

I'm hoping someone can say "Oh, that's easy you simply need to..."

Google searches did not produce much decipherable help.

Thanks!

[ridexbuilder]

How about the subdirs of catalog/images - images_big & thumbs in particular?

[JRR]

Do those sub-directories (catalog/images - images_big & thumbs) also need to be '777'? Currently they are both '755'.
I do not recall that as required in previous versions....

OK, I set those to sub-directories (catalog/images - images_big & thumbs) to '777' and the error message went away.

Are they both SUPPOSED to be '777'? That should be in the installation docs if true...

Thanks,

John :-#)#

[ridexbuilder]

On su_php/Suhosin(/mod_php?) servers they don't need to be - so, a quirk of your setup. You may find that the other sub-dirs will require the same, for example categories/

[JRR]

Is there any security risk to having the directories @ 777? My PHP version is 5.0.67.

Thanks!

John :-#)#

[ridexbuilder]

Is there any security risk to having the directories @ 777?

In a word, yes (in theory). Ideally, you'd use some form of PHP hardening. [It's commonplace for other e-commerce packages to expect 777 on image directories.] You could reduce permission levels when not uploading images (through an FTP or rsh script, for examples), if you feel uncomfortable with "leaving the door wide open". Alternatively, uprate PHP.

[JRR]

Could it be the 'user' that has the problem? I'm finding all the .php files that I need to edit (using Admin) are complaining that they are not writeable - privacy, shipping, etc. Their permissions are all set to 755 though - which suggests that the 'user' can edit - and the 'user' name is the same as the log-in name.
I am using the same user name throughout the site, with different passwords depending on the area - admin directory access, OSCMax Admin opeartions, etc. I can open the Admin functions, and edits to the database work just fine (add/delete/edit items, etc.).
I've broken something...
John :-#(#

[ridexbuilder]

If re-installing be sure to check the wiki.