[wp-hackers] Child plugins (add-ons)

David Anderson david at wordshell.net
Mon Feb 18 07:58:57 UTC 2013

On 17/02/13 12:00, wp-hackers-request at lists.automattic.com wrote:
> However, as Marko pointed out, his scheme is too complex as well as
> being completely unnecessary. The "base" plugin can easily be the free
> one, not violate any guidelines of any sort, and still leave action
> and filter hooks in it for the secondary, paid, add-ons to be sold
> elsewhere (ie. not on wp.org). And as was pointed out earlier, it's
> possible for a plugin to check for its own updates from anywhere.
> Those add-on plugins can check for updates from wherever they're
> hosted, while the free-base remains on wp.org.
I explained in an earlier message that the base plugin does leave action 
and filter hooks for the secondary, paid add-ons, and that the point of 
the scheme was not for that reason. The point of the scheme included to 
integrate with a shop that sells multiple add-ons, and provide the user 
with a console that showed them the other purchases that they could 
make, and have them only install an extra add-on *once*, instead of a 
new one each time they made a purchase. The scheme also provides, 
optionally, for plugin updates to be made available through the update 
mechanism on a per-site basis, instead of a 
buy-once-install-infinite-times model.


More information about the wp-hackers mailing list