[wp-hackers] Child plugins (add-ons) (Dino Termini)
mike at newclarity.net
Sat Feb 16 22:32:45 UTC 2013
On Feb 16, 2013, at 5:09 PM, David Anderson <david at wordshell.net> wrote:
>>> >it's to allow users to receive their add-ons via the normal WordPress updating mechanism, to do so without breaching wordpress.org rules on remote code
>> Interesting conversation. Would you mind elaborating on those specifics? I'm trying to envision what code is need for what you are saying.
> The specifics of the updating mechanism?
Wow, thanks for all the details.
I now realize I should have been more clear what I was asking. I was specifically interested in know what you meant about "without breaching wordpress.org rules on remote code" and what you did to stay within the rules?
That also implies a question as to what the rules actually are? I haven't seen anything listed on any of these links:
> It was far more code + complexity than I realised when I started!
Lol! Isn't it always? I have a project where my hindsight was similar. :)
More information about the wp-hackers