what about bp-plugins?
-
we already have “plugins” which lead us to activate/deactivate any plugin on a specific blog, and we have “mu-plugins” which is supposed to automatically activate plugins thru the whole site… could it be possible, to avoid collision, to have a bp-plugins folder where all bp based plugins could be installed?…
that’s because logically these plugins are independant from wp and wpmu, and we could have a specific panel to handle these plugins, as we already have a specific panel to deal with BP setup.
as a developer, it would help me to make these plugins BP only, so people would not be able to install them on a non-BP site, avoiding us a lot of non-related support… it would also help coding site-wide plugins that are not per-blog permitted…
-
You can hide the plugins panel in the administration area from your users and you can use plugincommander to choose which plugins should be activated for users and which shouldnt be.
Personally I don’t see why you would make a plugin folder for a plugin. If every plugin started doing that, then we’d have a lot of plugin folders.
the difference is that BP have its own structure for functions, that does not work with other versions of WP…
but it’s just me, i like when things are well dressed…
It’s a good idea and one I’ve tossed around, but the problem is that it would need to exist outside of the wp-content/buddypress/ directory to avoid automatic update problems, and people wiping out the plugins folder on accident (if they do a manual upgrade for example.)
Something like this may still happen down the road, as BuddyPress grows and a need for specific methods to register plugins with BuddyPress increases. At the moment it isn’t necessary because BuddyPress plugins are actually just normal WordPress plugins that may take advantage of BuddyPress features and API’s. (At least, that’s how plugin authors should be writing them.)
What will need to happen for sure is a way for plugins to tell BuddyPress “hey I’m here and I want you to know this information.” It’s possible to alter the $bp global directly to do these things, but tighter integration into the platform makes sense.
My opinions are subject to change on this one, but today that’s how I’m feeling.
it’s a great feeling actually, John James… and it would take “some” coders to build a bunch of BP-only plugins to start the wave…
maybe if i start coding again i will punch out some of the tools i have to be working exclusively in closed operation inside BP, and would store them temporarly in the plugins dir but would definitively work better if in their own location…
would be possible to work that detection loop in 1.2 ????
- The topic ‘what about bp-plugins?’ is closed to new replies.
