[wp-hackers] Auto Update Plugins

Mike Schinkel mikeschinkel at newclarity.net
Thu Feb 19 17:28:32 GMT 2009

It's really sad to me that you discredit other use-cases besides your own.

However, let's assume your view is the ideal view and mine is just wrong. Here's where there is a REAL problem with the current situation: IF someone "stupidly" decides to attempt a plugin upgrade on a directory using Subversion as the plugin admin section so constantly urges them to do THEN it deletes the existing plugin but DOES NOT upgrade or even restore the old plugin, the plugin installer simply won't restore anything, and the site is broken.

Please understand that not everyone who uses a site is the one who built it and thus not everyone using uses a site will know not to upgrade a site that is using Subversion.

THIS SITUATION IS A BUG, not a feature and needs to be fixed somehow.

-Mike Schinkel

----- Original Message -----
From: "Matt Martz" <mdmartz at sivel.net>
To: wp-hackers at lists.automattic.com
Sent: Thursday, February 19, 2009 12:08:29 PM GMT -05:00 US/Canada Eastern
Subject: Re: [wp-hackers] Auto Update Plugins

On Thu, Feb 19, 2009 at 12:03 PM, Mike Schinkel
<mikeschinkel at newclarity.net> wrote:
> Can this also address failing plugin upgrade because of read-only .svn directories?
> -Mike Schinkel
> http://mikeschinkel.com/

I'll way in with my opinion again.

My feeling is that if you have a plugin that was installed with
subversion then you should not use the plugin updater to update but
should use subversion.  Or you should remove the .svn directories
after retrieving the plugin with subversion and before using the
plugin updater.

I just don't think this is a shortcoming of the plugin updater but in
your poor use of subversion to retrieve plugins.


Matt Martz
matt at sivel.net
wp-hackers mailing list
wp-hackers at lists.automattic.com

More information about the wp-hackers mailing list