Skip to:
Content

Opened 16 months ago

Last modified 8 days ago

#4732 new enhancement

BuddyPress MU

Reported by: sooskriszta Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 1.6
Component: Core Keywords: 2nd-opinion dev-feedback
Cc: mercijavier@…, modemlooper@…

Description

Like WP MU enables networks of blogs, perhaps BP MU could consider powering networks of communities:

  • multiple communities on same install of BuddyPress
  • shared or partitioned user base
  • each community decides separately and independently which BuddyPress features to use (one may use profiles and activities only, other may use profiles and groups and forums, etc)
  • profile fields can be different for each community
  • each community can be on a separate subdomain
  • each community could use a different theme

Change History (8)

comment:1 follow-up: mercime16 months ago

  • Cc mercijavier@… added

There are already two free BuddyPress MultiNetwork plugins in the market.

  1. http://wordpress.org/extend/plugins/bp-multi-network/ - shared user base

and

  1. http://buddydev.com/plugins/buddypress-multi-network/ - separate user base

comment:2 DJPaul16 months ago

  • Keywords 2nd-opinion added

comment:3 in reply to: ↑ 1 sooskriszta16 months ago

Replying to mercime:

  1. http://wordpress.org/extend/plugins/bp-multi-network/ - shared user base
  2. http://buddydev.com/plugins/buddypress-multi-network/ - separate user base

Based on the description http://buddydev.com/plugins/buddypress-multi-network/ seems pretty close.

This is a very useful functionality.

However, this is one of those functions, for which one finds it very difficult to trust plugins. It is a "mission critical" application, so to say. If a plugin is abandoned, or breaks on updates, it brings down the whole site from ground up.

Hence core enhancement, from my perspective.

comment:4 DJPaul15 months ago

  • Keywords dev-feedback added

comment:5 boonebgorges14 months ago

  • Milestone changed from Awaiting Review to Future Release

However, this is one of those functions, for which one finds it very difficult to trust plugins. It is a "mission critical" application, so to say. If a plugin is abandoned, or breaks on updates, it brings down the whole site from ground up.

We have to make decisions about what goes into BuddyPress core based not only on what some people think (rightly or wrongly) is "mission critical", but also on what will have the broadest impact. BP MU is a neat idea, but it almost surely would only be used by a very small percentage of BP installations.

That said, over the last few versions, some key BP functionality (such as bp_get_user_meta()) has been abstracted in such a way that it would be easy to do a true BPMU (as opposed to multi-network) with a plugin. There's nothing wrong with the current multi-network solutions, but they're not user-friendly, and they introduce a little more overhead than one might like.

I'm putting this into Future Release because I think it's worth having a continuing conversation about the further steps that BP has to take to be easily converted to multisite-mode (even if we never expose it in the UI).

comment:6 sooskriszta8 weeks ago

Just to clarify, by "mission critical" I don't mean necessarily important for everyone. What I mean is that if someone is using this function then it is at the core of their site. They can't abandon just this function and expect to use the rest of the site properly. Removing this function would kill the site. So, a plugin is a VERY risky bet. If a plugin is abandoned, or breaks on updates, it brings down the whole site from its foundation.

If a significant minority of BuddyPress users use this function, then it's probably worth including it in core.

comment:7 sooskriszta3 weeks ago

P.S. Since WPMU is part of the WP core, we should think about including BPMU in BP core, for parity reasons as well.

comment:8 modemlooper8 days ago

  • Cc modemlooper@… added
Note: See TracTickets for help on using tickets.