Comments on: Warnings Upgrading WordPress Plugins : NearlyFreeSpeech.net

By: Patrick

Patrick — Mon, 28 Mar 2011 07:45:55 +0000

Works fine for me – only issue I didn’t realise (when using the “Automatic update” which uses FTP or SFTP) is that within the NFSN console, you *must* enable FTP for the profile (i.e. ‘username’) AND the site (i.e. ‘mysite1′).

So username for FTP would be username_mysite1.

Make sure FTP is enabled for the profile and the site – without both the authentication will be blocked for username_*.

By: Rob

Rob — Mon, 17 Aug 2009 05:50:22 +0000

I upgraded from 2.7 to 2.8 automatically via the dashboard, but as a precaution I disabled every single plugin before the upgrade. It worked fine, and then I manually re-enabled all the plugins.

Then I recently upgraded from 2.8 to 2.8.4 without disabling any plugins, and that worked fine. Although, the All-In-One SEO plugin was already disabled, as I disabled that to troubleshoot performance problems. (I’m still not sure if thats the culprit though)

By: Raj

Raj — Sat, 15 Aug 2009 18:54:20 +0000

I faced a similar problem while trying to update a plugin automatically. I had to manually deactivate, copy the files and then activate the plugin to get rid of the warning.

Have you tried upgrading wordpress automatically on NFS. Did it work? I haven’t attempted it yet. I am a little scared.