Wordpress Issue: Installing/Upgrading Plugins From Site

What version of WordPress are you using?

2.7.1 is the latest version, with 2.8 due out soon.

Since 2.7 the automatic updates are part of standard WordPress (so you shouldn't need the WPAU plugin).

WordPress will ask you for your FTP details if the file permisisons mean that PHP can't modify the files.

James

I'm using 2.7.1 - and I actually used the built-in upgrade method on the last update (thanks for reminding me!). I liked this method because it was quicker, but WPAU let me download copies of my files and the DB along the way.

I actually just upgraded my total install of Ubuntu (with success!) and still nothing. Not that I expected this to work, but worth a try since I was due to patch for security holes anyways.

The plug-in install/update page still reads: "Username/Password incorrect for *"

Somehow though I've lost the FTP option and now I can only select FTPS.

I'm also having the same problem, and would love to hear the solution !

I remember having this problem a long time ago after migrating a blog over. IIRC, it's an ownership issue. Make sure your webserver owns the directory for the wordpress plugins, or it won't be able to write to it and throw a weird error (which is why I remember!)

edit: Looks like James beat me to the punch in his last line :) !

I had a similar problem when I recently migrated a Wordpress blog to Linode. As others have said, it is a permissions problem. Not only does the wp-content/plugins directory have to be owned by the webserver id/group, but the individual directories for each plugin within the plugin directory have to be owned the same.

Len

As for the permission issue, I don't have this problem with my WordPress blog installed on the Linode I have in London.

When I installed WordPress, I did this:

chown -R www-data:www-data /space/web/neonnero.com/www

Where both the user name and the group name Apache runs under is named "www-data" (Debian default, I assume), and "/space/web/neonnero.com/www" is the server path of the WordPress install directory. The "-R" changes the ownership recursively in all files and subpaths.

I did that as well, didn't fix the problem….

@NeonNero:

As for the permission issue, I don't have this problem with my WordPress blog installed on the Linode I have in London.

When I installed WordPress, I did this:

chown -R www-data:www-data /space/web/neonnero.com/www

Where both the user name and the group name Apache runs under is named "www-data" (Debian default, I assume), and "/space/web/neonnero.com/www" is the server path of the WordPress install directory. The "-R" changes the ownership recursively in all files and subpaths.

Thanks for the tips! I am using CentOS, so I changed the ownership of my wordpress files to apache.apache and it works. :D

cd /www-root-directory/

chown -R apache.apache *

I am not sure this will cause security issue or not, but you can change the ownership back after you finish the installation.

Ive been using the Fix Plugin Update plugin from the following source.

http://yoast.com/fix-automatic-plugin-update/

Works great on all current versions of Wordpress.