[wp-hackers] Child plugins (add-ons) (Dino Termini)
dino at duechiacchiere.it
Sat Feb 16 20:19:54 UTC 2013
David and Marko,
paid add-ons are exactly what I’m planning to do with my plugin. At first I
had taken the same route as David’s, but then I realized it was an awful
lot of code to write, both for the store and the management part, and
that’s when I started looking at existing solutions like CodeCanyon or
WpXtreme as the channels to distribute those premium add-ons. But I would
still like to have a way to alert premium users when a new version of a
given add-on is available on one of those platforms, and that’s where I
might be able to reuse portions of David’s code (see? APIs once again would
encourage collaboration!). Which, by the way, doesn't seem ‘weird’ to me at
I know this topic has been discussed many times, but maybe the time is ripe
to actually do something about it?
David, I will get in touch with you, thank you for sharing your thoughts!
*From:* Marko Heijnen <mailing at markoheijnen.nl>
*Sent:* February 16, 2013 2:46 PM
*To:* wp-hackers at lists.automattic.com
*Subject:* Re: [wp-hackers] Child plugins (add-ons) (Dino Termini)
Thats seems weird to me. I have the same plan for a plugin and I'm writing
the add-ons right now. I don't need to touch the free plugin on
WordPress.org since it has the right filters already.
When you need to change the main plugin to enable paid extensions then your
main plugin is wrong coded. In your case you don't even need to manipulate
the main plugin.
I could however understand that you would have a main paid plugin that
takes care username+password and the updates for the extension.
More information about the wp-hackers