[wp-hackers] Auto Update Plugins

[Chris Williams]

But the last thing I would want is a plugin (or anything for that matter)
dropping unexpected things into my theme directory...

To get back up to the original question, the point was to have a way to
insure that a plugin update wouldn't trash customized content.  This example
(below) seems like a great one.  And it seems like the /plugin-data
(wherever its root turns out to be) is a pretty good idea.  Analogous to the
wp-content tree, "don't trash me on an update".


> From: scribu <scribu at gmail.com>
> Reply-To: <wp-hackers at lists.automattic.com>
> Date: Wed, 18 Feb 2009 00:57:21 +0200
> To: <wp-hackers at lists.automattic.com>
> Subject: Re: [wp-hackers] Auto Update Plugins
> 
> On Wed, Feb 18, 2009 at 12:44 AM, Otto <otto at ottodestruct.com> wrote:
> 
>> Can we come up with some specific use cases here before deciding how
>> to implement it? What is this "plugin-data"? The main case I was
>> thinking of was plugins that have customizable CSS files or IMG files
>> which affect the output of the plugin.
>> 
> 
> I have a plugin that generates a skinable carousel. The user's CSS file
> could be stored in wp-content/plugins-data/my-plugin/ but it would actualy
> make more sense in the current theme directory, since the ideea would be to
> make it blend with the rest of the site.
> 
> -- 
> http://scribu.net
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers