[wp-hackers] Auto Update Plugins
scribu at gmail.com
Tue Feb 17 18:50:41 GMT 2009
A php file isn't detected as a plugin unless it has a plugin header with /*
Plugin Name etc. */ so there shouldn't be any problem.
You could even create a child plugin header to be parsed by the parent
Child Plugin Name: Spam Karma Extenden
Child Plugin Parent: Spam Karma
I think the best name would be /wp-content/plugin-data/ because dashes are
used everywhere instead of spaces or underscores.
On Tue, Feb 17, 2009 at 8:05 PM, Jess Planck <jess at funroe.net> wrote:
> I thought something like wp-content/plugin_data/ was more appropriate.
> Doesn't WordPress comb wp-content/plugins/ for sub-folder plugins? Wouldn't
> wp-content/plugins_data/plugins_data.php file be seen as as potential plugin
> and possible hazard?
> On Feb 17, 2009, at 11:53 AM, Stephen Rider wrote:
> Anyway, that's my two bits, and that's probably the way I'm going to start
>> doing my plugins until something significantly better comes along.
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers