Skip to:

Sub-plugins (plugins that extend other plugins) architecture

  • Greg


    [this is probably directed more at JJJ and Pete than anyone else]

    With BuddyPress and now bbPress as plugin, does WordPress have an architectural direction for plugins that extend other plugins.

    Or perhaps the right way to think about this is plugin dependencies. I see this discussion in WP trac where the consensus seems to be that plugin dependencies should be handled by sub-plugin developers with the neat approach Mark Jaquith suggests there.

    This is beautiful in its simplicity, but a little unfriendly to the ordinary user installing a bbPress plugin without bbPress-as-plugin installed and activated.

    Is Mark’s approach the plan for bbPress as plugin, or has the thinking evolved since this discussion 6 months ago?

Viewing 2 replies - 1 through 2 (of 2 total)

  • Gautam Gupta


    One can easily do a check on activation if BBP_VERSION is defined and optionally a version_compare check too, and if it doesn’t satisfy the condition, then the plugin should deactivate itself.



    I guess one could also use the check on BBP_VERSION (or equivalent) to print an error message when the plugin refuses to activate.

    But a user would still need to install the plugin or look in the code (or read the README if the plugin author was good enough to mention the dependency).

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.
Skip to toolbar