WordPress Update Plugin Issue
I have several plugins that are being flagged for update. However, when I press update it is asking for FTP information. I recently had to change permissions on my domains. So before the permission change the updates happened without ever asking for FTP details. Here is a screenshot of the ftp request screen.
https://gyazo.com/93bcb31a4ca9816d6b458baacef3048a
reading this blog post it seems my owner doesn't have apache privileges.
http://www.chrisabernethy.com/why-wordpress-asks-connection-info/
So how can I grant the owner those privileges? Currently this is a semblance my privilege setup. centos:apache. I am on a Centos 6.3 vps.
Please tell me how to get back to this happening automatically before the FTP request screen was shown.
Thanks,
Randal
https://gyazo.com/93bcb31a4ca9816d6b458baacef3048a
reading this blog post it seems my owner doesn't have apache privileges.
http://www.chrisabernethy.com/why-wordpress-asks-connection-info/
So how can I grant the owner those privileges? Currently this is a semblance my privilege setup. centos:apache. I am on a Centos 6.3 vps.
Please tell me how to get back to this happening automatically before the FTP request screen was shown.
Thanks,
Randal
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I suggest that you add "webmaster" to the "apache" group:
useradd -G apache webmasterASKER
Thanks for the new suggestion I get this message though when I try to use that command
useradd -G apache webmaster
useradd: user 'webmaster' already exists
I don't seen any error but digging deeper at this page http://blog.arithm.com/2010/04/03/get-wordpress-to-stop-asking-for-connection-information-when-upgrading-plugins/
I noticed the one plugin that does load automatically is chowned apache:apache I thought by adding webmaster to the apache group it would be equivalent to apache:apache? Does something else need to be done?
useradd -G apache webmaster
useradd: user 'webmaster' already exists
I don't seen any error but digging deeper at this page http://blog.arithm.com/2010/04/03/get-wordpress-to-stop-asking-for-connection-information-when-upgrading-plugins/
I noticed the one plugin that does load automatically is chowned apache:apache I thought by adding webmaster to the apache group it would be equivalent to apache:apache? Does something else need to be done?
Since the group exists:
usermod -a -G apache webmaster
usermod -a -G apache webmaster
ASKER
I made the change usermod -a -G apache webmaster
logged out of wordpress, cleared the browser cache but still get the connection screen just like the screenshot in the original question.
logged out of wordpress, cleared the browser cache but still get the connection screen just like the screenshot in the original question.
Did you
chown -R apache:apache /var/wwwASKER
No, I avoided doing that because of what I said earlier.
**************
I understand what you are suggesting but I also know to change all those permissions affects everything below var. Is there another option to make a change to only change the wp permissions that are incorrect since it seems there are only a few files and folders involved?
As it is now, with everything webmaster:apache I can log in as webmaster and make changes via SFTP without issues.
**************
Isn't there another way?
**************
I understand what you are suggesting but I also know to change all those permissions affects everything below var. Is there another option to make a change to only change the wp permissions that are incorrect since it seems there are only a few files and folders involved?
As it is now, with everything webmaster:apache I can log in as webmaster and make changes via SFTP without issues.
**************
Isn't there another way?
By making "webmaster" a member of the "apache" group, you will still be able to do the FTP thing. Which you should not, rather use SFTP.
ASKER
I am not following you. As you can see from my comment I am using sftp.
**************
I understand what you are suggesting but I also know to change all those permissions affects everything below var. Is there another option to make a change to only change the wp permissions that are incorrect since it seems there are only a few files and folders involved?
As it is now, with everything webmaster:apache I can log in as webmaster and make changes via SFTP without issues.
**************
**************
I understand what you are suggesting but I also know to change all those permissions affects everything below var. Is there another option to make a change to only change the wp permissions that are incorrect since it seems there are only a few files and folders involved?
As it is now, with everything webmaster:apache I can log in as webmaster and make changes via SFTP without issues.
**************
Cool, didn't spot that.
Set ownership to apache:apache, and make webmaster a member of the apache group.
That should work.
Set ownership to apache:apache, and make webmaster a member of the apache group.
That should work.
ASKER
I chowned one file as a test and tried to use webmaster to sftp to the file and change permissions on it and got this message
https://gyazo.com/a730ef93169919f82bd56afae2126972
https://gyazo.com/a730ef93169919f82bd56afae2126972
ASKER
the file was apache:apache 775 and I temporarily tried to change it to 777.
I am not sure that the rights of a group allow changing permissions, and in any event you wouldn't generally need to do that via SFTP anyway.
Try downloading a file, modify it a bit, and upload it, see how that goes. Also try uploading a new file - you will need to chown it afterwards to apache:apache, which you should be able to do as webmaster.
Try downloading a file, modify it a bit, and upload it, see how that goes. Also try uploading a new file - you will need to chown it afterwards to apache:apache, which you should be able to do as webmaster.
ASKER
Thanks for the help.
ASKER
As it is now, with everything webmaster:apache I can log in as webmaster and make changes via SFTP without issues.