[wp-hackers] pluggable functions

peter baylies pbaylies at semperfiwebdesign.com
Sat Oct 27 21:48:34 UTC 2012


Say you have a free and a pro version of the same plugin, and they share a
lot of code; and then someone upgrades to the pro version from the free
version, without first deactivating the free version. Or, similar scenario;
say someone else forks your plugin without changing all the function names
/ prefixes, and someone tries to install both your plugin and the forked


 -- Peter

On Sat, Oct 27, 2012 at 5:05 PM, Mike Schinkel <mike at newclarity.net> wrote:

> On Oct 27, 2012, at 4:57 PM, peter baylies <pbaylies at gmail.com> wrote:
> > This doesn't necessarily apply as much to core or to themes, but I find
> > pluggable functions to be very useful in plugin development, where you
> > might have a situation where your plugin gets forked, or different
> versions
> > or variants of the same plugin might end up getting installed on a site
> --
> > at the least, using pluggable functions means that this doesn't end up
> > breaking everything as soon as there's a naming conflict.
> Any chance you could provide a concrete example of what you are
> describing?  I'm having a hard time envisioning this.
> Thanks in advance.
> -Mike
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list