[wp-hackers] Child plugins (add-ons)
kevinjohngallagher at hotmail.com
Sat Feb 16 17:03:54 UTC 2013
Child plugins are absolutely the way forward.Turning on/off options in a single plugin isn't an overhead really, but it means that every time there is a bug-fix for a single feature the whole plugin must be updated.
I know we've stopped using Yoast's wonderful SEO plugin due to this.
We hit a stage where we had 4 updates in 1 week to fix a bug in a feature that we didn't have on, as it had nothing to do with SEO.
It's awesome that plugins are so well maintained, but there comes a point were we have to think of the non-dev/non-techie user first.
> From: almog.baku at gmail.com
> Date: Sat, 16 Feb 2013 13:19:21 +0200
> To: wp-hackers at lists.automattic.com
> Subject: Re: [wp-hackers] Child plugins (add-ons)
> By my opinion the properly solution is to implement a *Dependency system*.
> and and the ability to plugin requiring another pluging.
> On Fri, Feb 15, 2013 at 9:26 PM, Dino Termini <dino at duechiacchiere.it>wrote:
> > Hi Marko,
> > WP SlimStat already includes a number of actions and hooks that allow
> > third-party developers to extend its functionality. A "separate plugin that
> > needs the main..." is just one way of looking at things. If we apply your
> > reasoning to Child Themes, then that naming is "wrong" as well, as they are
> > usually extensions or customizations of existing themes, and not separate
> > themes relying on their parents ;) But naming conventions aside, I believe
> > it would be great to expand the Plugins Management interface to group
> > (accordions?) plugins based on their relationships. I haven't looked at the
> > way BuddyPress implements it, but it could be a good starting point.
> > Cheers,
> > Dino.
> > On 2/15/2013 2:14 PM, Marko Heijnen wrote:
> >> Hey Dino,
> >> If it is a part of your plugin then delete doesn't make sense. Just an
> >> option to make it active or not. The word 'Child plugin' would be wrong for
> >> this.
> >> A 'Child plugin' for me would be a separate plugin that needs the main
> >> plugin because it uses the hook the main plugin has. Like a random
> >> BuddyPress plugin that obviously need BuddyPress.
> >> So I guess you should look into your plugin and see if there are places
> >> where it make sense to add an action or a filter.
> >> Marko
> > ______________________________**_________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.**com <wp-hackers at lists.automattic.com>
> > http://lists.automattic.com/**mailman/listinfo/wp-hackers<http://lists.automattic.com/mailman/listinfo/wp-hackers>
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers