WordPress.org

Ideas

Child Plugins

  1. cromermusic
    Member

    Been stumbling on this problem aswell. I don't want to change the orininal php in the pplugin since that will be erased with an upgrade of the plugin.

    Posted: 1 year ago #
  2. Ian Dunn
    Member

    12345

    Three years after starting this thread, I have to admit that it was a horrible idea. Like ucfknight10 said in the first reply, the proper way to do this is with hooks.

    If anyone's interested, I wrote a post with more details about best practices for customizing and extending plugins at http://iandunn.name/the-right-way-to-customize-a-wordpress-plugin/

    Posted: 1 year ago #
  3. webbrewers
    Member

    12345

    I was thinking of a "child plug in" in the broadest sense - a structured and consistent way of separating customization from core - blessed by wp.org, rather than the nuts and bolts of how a plug in's code is actually customized.
    Ian's outlined various ways we can keep customizations separate - I'd just like to see some sort of standardization in same way child themes have been standardized.

    Posted: 1 year ago #
  4. DaltonKey
    Member

    I may be wrong, I don't have much experience with hooks; but I think this is a great idea. I would love to see child plugins, and something similar for editing core functions also. I have been looking for something similar to this for the longest time, and I haven't had any luck.

    Posted: 6 months ago #
  5. I would like to put my own approach to child plugins into discussion: http://www.hinnerk-altenburg.de/weblog/child-plugins-for-wordpress-child-theme-for-plugins/
    I am looking forward to your feedback about my code on GitHub!

    Thanks!
    Hinnerk

    Posted: 4 months ago #
  6. Ipstenu (Mika Epstein)
    Half-Elf Support Rogue, Volunteer Forum Mod & Plugin Referee

    Hinnerk - Having themes 'require' plugins for additional features is not exactly what we mean here. We mean a plugin that has a child, much like a theme has a child theme. The child plugin cannot run without it's parent, and allows you to safely hook into the parent.

    For what you're talking about, we recommend using http://tgmpluginactivation.com/ in your theme :) Have it recommend and helpfully install the required plugins.

    Posted: 4 months ago #
  7. Hi Mika,

    thanks a lot for your reply!

    I might haven't made my point, clearly enough. The things you are talking about are not at all connected to what I am trying to show in my article or my code on GitHub!

    What I am showing there (https://github.com/hinnerk-a/wp-plugintheming):
    1) A "parent" plugin with a custom post type 'movie'. This "parent" plugin contains template files for displaying 'movie' posts.
    2) A "child" plugin containing little frontend modifications that override the "parent"'s templates, CSS and functions - like you might have seen from WooCommerce. It does not add any functionality (although it could do, but that's not the intention, here!).
    3) It's not at all about required plugins or additional features!

    We mean a plugin that has a child, much like a theme has a child theme. The child plugin cannot run without it's parent, and allows you to safely hook into the parent.

    I still think I'm exactly talking about your topic!

    I'd like to hear your opinion about my code, again. My example plugins on GitHub are running out-of-the-box and you can play around.
    I hope you'll get my point better, then!

    Thanks!
    Hinnerk

    Posted: 4 months ago #
  8. JohnRepairs
    Member

    Child plugins - although a good idea, make it much easier for a new developer to alter (and make better) an existing plugin.

    Great for the end user. Bad for the original plugin developer.

    Posted: 3 months ago #

RSS feed for this topic

Reply

You must log in to post.

  • Rating

    12345
    47 Votes
  • Status

    Sorry, not right now