[wp-hackers] Auto Update Plugins

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

That would not be ideal (in my view) but it would fix the current bug that exists that blows away the existing plugin.

Maybe a better approach along those lines would be to look in the directory to see if there are any read-only files or directories and if so give a notice to that effect.  It's not Subversion per-se that is the problem but the fact that Subversion sets files & directories to read-only.

-Mike Schinkel

----- Original Message -----
From: "Stephen Rider" <wp-hackers at striderweb.com>
To: wp-hackers at lists.automattic.com
Sent: Thursday, February 19, 2009 12:37:24 PM GMT -05:00 US/Canada Eastern
Subject: Re: [wp-hackers] Auto Update Plugins

A new topic basically, but this seems like it might be a pretty easy  

Perhaps the plugin autp-upgrade script should simply check the  
directory for an .svn directory, and if it's there, don't upgrade?   
(With requisite notice of course!)


On Feb 19, 2009, at 11:28 AM, Mike Schinkel wrote:

> 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.

wp-hackers mailing list
wp-hackers at lists.automattic.com

More information about the wp-hackers mailing list