True BP compatibility with Multisite
.i would like to have the main site with a theme (doesn’t need to support buddypress) and for the network sites, i would like to enable the default buddypress colour childthemes and simply update the headers for each (or any other buddypress theme)….but this method, while simple, seems to be a major issue for buddypress
are there any plans to truly make buddypress fully leverage multisite?
@jeffsayre – thanks Jeff
Ok, I’ve found several threads on this feature ranging from inquiries to requests and everything in between…
it looks like this may be slated for BP 1.3 which is scheduled for a Jan 1 release. Can anyone confirm that this feature will be available in BP 1.3?
I don’t think anyone will confirm one way or another but I would personally doubt very much that this will figure in 1.3 but I’ve said all that on one of the other many threads you have posted on this subject, in all honesty continually posting about this isn’t going to make it happen.
I predict that this won’t be in 1.3. Although, as some of the other threads mention, the basis for being able to do this has been added and could be added in 1.3. I would bet this project is going to need to be done by someone outside of the core developers to make it happen soon.
@hnla the goal is not to continually post on a topic or subject. I started a project with the assumption that this was doable with buddypress and multisite, so a lot of my initial posts were to find answers to try and solve issues, now it’s obvious that this isn’t possible and thus the post in the “requests and feedback” group. I would imagine as with any dev group, the most requested feature would be the next priority, and it seems a few people have been requesting this feature for a while
Just added this at the bottom of Codex FAQ page http://codex.buddypress.org/getting-started/faqs/
Feel free to improve wording
Can I run multiple instances of BuddyPress in a WP Multisite installation?
No. BuddyPress can only be activated once in either the main site or a secondary blog of a WP Multisite installation .
The most requested feature doesn’t always get next on the list in most open source projects. I’d say the code that the user community wants to deliver is the most likely to happen next. So, if you and the group of people that want that feature want to support having a coder become motivated to develop this feature, then I bet it will get a much higher priority.
@techguy trying to round up the troops now and hopefully there will be enough interest
@aweathers; this might help… http://bp-tricks.com/featured/new-theme-bp-default-member-blog-multisite-communties/. Not sure if you want this specifically, but it allows you to have matching themes across your blogs in your install.. you can’t run BuddyPress on them though..
@Bowromir thanks for the tip, at first glance, it doesn’t look like what i’m going for, but i’ll check it out on the site (when available again)
@Bowromir – nope not what i need…need true BP MS compatibility
I, too, would love to have this. I settled on WP because of BPs promise to run in wpmu. That promise was inconsistent with the reason for installing wpmu and thus was misleading.
I would hope that the description of bp be changed or the capability to respect the site_id of a multisite install would be reflected in bp some day.
Until then, I am stuck with projects that cannot reach their vision because of limitations “built into” bp. And I am not a strong enough programmer to make the change myself.
Something that could help organized a large community is group hierarchy. Meaning large communities are made up of smaller communities and those are a community of groups and those are groups of even smaller groups.
Using Boy Scouts as a metaphor, Boy Scouts of America is divided into Coucils; Councils are divided into Districts; Districts divided into Sponsor Organizations; Sponsor Orgs sponsor Troops, Packs, Ships, Crews, etc. Troops are divided into Patrols, Packs into Dens, etc.
Members of one of the lowest level groups can move among groups at the same level and as the members age they will move into the next level, etc. Members can also be members of multiple groups, but not the same level unless they transfer to one at the same level.
I also wonder if you couldn’t write the code to respect the site_id similarly to code that enforces security. Where as in security you don’t show something if the user does not have access to it, you could do the same while checking the site_id a user is viewing; if the content does not belong to the site_id I am viewing then it would not be part of the query results, etc.
This functionality is currently being developed by @wpmuguru, but I don’t know that there has been any timeline published as far as a plugin release or it being included in core.
Most? all? of the core patches suggested by wpmuguru have made it into trunk (v1.3). I think there’s one patch still to look at. I don’t know what else would be required beyond this point. Boone and John have made a number of changes as to where we store data in certain multisite situations, so we should be much closer to supporting this now.
You must be logged in to reply to this topic.