- This topic has 7 replies, 3 voices, and was last updated 10 years, 8 months ago by
.
-
Posts
-
Since going live with my site, I cannot write to the functions or CSS files. The file permissions on the folders are set to 755 and files 644 as expected, but I can't write to them without changing the file permissions on the files to 775 or 777, and occasionally that doesn't even work.
Has anyone had this problem before? Is there something in the Genesis settings that I'm missing? I am logged in as Administrator.
Many thanks,
Danielle
I can't say what exactly is going wrong, but when I switched to a VPS I had a TON o file permission errors. Most were related to the user / group needing www-data, since that's what the server used to execute PHP. Again, I have no idea if that's of any help, but check your group / owner settings, not the actual permissions.
That depends on who your host is, an dhow you upload files. So:
Who is your host?
Do you have Shared hosting, or do you run a VPS (virtual private server)?
Do you use FTP to transfer files, or cPanel / some alternative?
When you view your files on the server, it should show the group / user, as well as permissions. You can change them by command line, but that's a bit more advanced, and may not even apply.
Thank you for your response Porter. The site is hosted at sherweb.com (multi-domain, web hosting) which uses Plesk panel. I checked the permissions on the server and they are ok. I need to change the permissions to 777 on the functions.php and style files (not folders) in order to update them using the WP editor.
I contacted Sherweb. They don't think that the problem is at their end, and since this is the first time this problem occurs and I have other WP sites hosted there, I suspect they are right. I went through all the other tests: deactivating all the plugins, switching to the WP 2014 theme, but none of it made a difference.
Danielle
Trying grabbing a clean wp-config file, and simply copy / paste the crucial info over from your current wp-config file to the fresh one (it'll be a quick section, database name, user, password, etc, the stuff you configure when you first set it up). I'm not sure what would have caused it, but wp-config is where you COULD put code that would mess this up. For instance, my VPS requires that I specify a port, username, etc, which is all additional code, and my WordPress can't update without that information. Given you don't need that, I suspect there's something else lingering in your wp-config that doesn't belong, so a fresh copy (with your crucial information copied over to it) may do the trick.
The permissions mask that you have to change to indicated a user, group or other ownership problem, and this may be on the parent directory as well. It is probably group membership issue.
I think Porter is on the correct track with file and directory ownership. Typically in hosting panels you won't see ownership or expanded ACL info; just file masks (644, 755, etc).
Basically, the directories and files need to be owned by whomever the httpd that serves WP. The host should know, and you may have to ask them to chown -R to the webserver owner (or whatever they recommend).
How did you migrate this onto to the host? I've seen this a few times with some plugins that fail with some wp population and fail back to less graceful methods, sometimes leaving ownership not set properly.
Hi coralseait,
I didn't upload the site to the server myself. I use the Serverpress service. I'm a little confused by all this and wouldn't know how to create a clean wp-config file. I think I'll put Serverpress and my hosting company in touch and let them figure it out.
Many thanks for your help.
Danielle
- The forum ‘General Discussion’ is closed to new topics and replies.