I saw the Buddypress link describing different ways to activate Buddypress on Multisite networks. Is there a definitive set of “best practices” for deploying Commons in a Box & Buddypress on Multisite, specifying which plugins should be network activated and which could be sub-site activated?
When run a performance profiler on our network sub-sites, it reports that a lot of plugin overhead is caused by Buddypress. If we deactivate Buddypress at the network level and only activate it at the top-level site, would it have a detrimental effect on Commons-in-a-Box? Can I also activate C-Box at the top-level sub-site rather than at the network level?
I’ve seen this post describing how to disable BBPress on sub-sites. Could the same work for disabling Buddypress or other network activated plugins on sub-sites, or would that break things?
We use several Buddypress-related plugins at the network level, including:
- BP Group Organizer
- BG Groupblog
- Buddydrive
- BuddyPress Activity Privacy
- BuddyPress Group Email Subscription
.. and several others. If we were to activate BuddyPress only at the top-level sub-site, can we activate these associated plugins at the top-level site as well, or if they can only be activated at the network level, is there a way to prevent them from loading on other sub-sites? My apologies if this message is convoluted, or if the network vs. local plugin issue was already addressed elsewhere. Any guidance you can offer would be most appreciated. Thank you
.
