no, shouldnt be needed…

take a look at wp-content and get its permissions… sp-resources should be the same (as well as sub dirs)…  also, look at the uid/gid and do a comparison…

on rare occasions, based on server settings, when the sp-resources directory is created, the wrong permissions and/or uid/gid get assigned…

Permissions are 755, which should be fine, but even if I try to change to 777, the permission for the subfolders under /sp-resources can’t be changed; they are stuck.

I tried different FTP clients, and got the same result.

Some hosts wont allow 777, with good reason, and 775 folders is as it should be. Mr Papa could well be right that this is a conflict in the UID/GID which are the ownerships of the sp-resources folder and then hence it’s child folders.

A decent ftp client should be able to tell you what the UID and GID are set to and once again – they should be the same as the parent wp-content folder. If they are not set to allow you ownership then you wont be able to change the permissions on them or – probably – write to them.

Personally this is what I would be asking my host to check and if they find either are incorrect, ask them to not only correct them but ensure you can create other folders in the future if needed. Quite a few WP plugins will add stuff to the wp-content folder – it is what it is for of course.

Problem is solved. The host did uncover some issues on their end (unspecified) and corrected them. That allowed me to access FTP normally and change permissions. The next problem was that during a “major update” to their OS, my plan was reset to the lowest disk quota, and transfers were blocked because I was deemed out of space. My plan was set back to where it should be, disk quota restored, and it appears all is well again.

The reason it appeared only the in SP directory is that is where I was focusing my attention. But in the end it wasn’t an SP problem. (Which makes sense.)

Thanks.

Excellent news, glad everything is OK!

OK new wrinkle, related to the same. You mentioned setting permissions to 775, but that’s throwing warnings in the Storage Locations interface, which reports them as not writeable. Setting them to 777 fixes the issue, but is that safe?

Just out of interest what are the permissions on the wp-content folder? If they are 777 and a sub folder is 775 I could see that might cause problems, although folder permissions are not my strong point!

wp-contents is 755, sp-resources is 775, and the subs under that are all manually set to 777. I think I’m opening myself up to a security issue??

The site isn’t live yet, so I am still playing around. Not too worried about security yet.

ideally, wp-content, sp-resources and sub dirs under there should all be the same permission… if you have to use different, that likely means the ownership is wrong so check the uid/gid… again, they should match wp-content…