BuddyPress.org

Are you using deep integration?

There are several commercial plugins for WordPress. I assume they would work with wpmu and buddypress as well, since those are big potential markets for them.

Hello jdoe_,

Just to say I’m running WordPress MU 2.8.4a + BuddyPress 1.0.3. as well, and the activity is working well in the member profil.

I hope you’ll find an answer to your problem,

Gaetan

The way this works is actually really super easy and very, very awesome…

There are a few different variations of ways to do this, and I can see some really imaginative uses of this method doing some really fantastic and super awesome things, so if you’re not already, I suggest you get excited…

I think the way that most people will use this method is with the included BuddyPress Framework theme as a jumping off point. Think of it as the HTML and bare-bones styling to get your site’s root blog and BuddyPress profile/directory pages up and running. It includes all of the normal files you would expect from a typical WordPress theme (single.php, comments.php, page.php, index.php, home.php, attachments.php, etc…) plus it includes all of the theme files for BuddyPress registration pages and components in their own respective folders similar to what bp-member did.

Currently, parent/child template relationships do NOT include the parent template’s style.css, so if you’re making a child theme, you will need to manually include the style.css of your parent theme with an @import rule, but it takes 2 seconds to type in so no big deal.

So that means that your parent/child relationship is really only for .php files until you manually @import a CSS file from another directory.

To answer your question about multiple parent themes, yes and no.

Lets say we have three themes: bp-framework, bp-default, and bp-child.

Each theme/template can only name off one parent, but that doesn’t stop the parent theme/template from having its own parent also. Example: bp-child could name bp-default as its parent, and bp-default could name bp-framework as its parent, and they will recursively overrule each other down the parent/parent/child ladder with the current template winning at the end.

This works well in situations where you might not need a home.php for your child themes. Home.php is a WordPress file for hardcoding the landing page of your blog, and maybe child themes don’t need one. In that case, move home.php into a “bp-home” folder with a style.css that makes the bp-framework its parent and includes the parent style.css, assign bp-home as the theme for your root blog, and you’re done. This way the other blog themes won’t have a home.php for no reason.

Because of this, it’s possible to have themes inherit from multiple other themes if you plan ahead in such a way that allows for this. My experience with this idea and creating my own framework is that it takes a little pre-production planning, but it pays off big time later on.

The other crazy fluke is that parent themes don’t need to be active in the Site Admin area. This means that you could have child themes active for users to select without allowing them to select the parent theme, and still have the parent theme’s files be accessible to the child. This really gives you a better way to control the themes that users have access to and how they work with your custom framework to keep your header/footer/other files in sync.

I personally can’t wait to see what some of the more popular WordPress theme guru’s are able to pull off with the next version of BuddyPress.

Certainly not showing off – but I’d love some feedback. You can get the jist of what we’ve built here – really basic, but just trying to see if Buddypress can really solve our problems.

Our issues to-date are no way of validating users and ensuring we want them to successfully register. Second issue is the email that is sent to approve a group addition (links are broken). Third issue is a trying to find a way to prevent registered users (subscribers) from creating groups, while not preventing them from participating.

http://www.joefirstmanstreet.com

* Currently forcing people to login or register before they see anything.

Referring to this program/site: http://www.intensedebate.com/wordpress

I don’t know how it can be done but I know it can be done with this:

https://codex.buddypress.org/developer-docs/custom-buddypress-loops/the-profile-data-loop-bp_has_profile/

Okay, several issues to discuss here:

1. I created a new function in wpmu-functions.php

   Why modify a core WPMU file to be used in a BuddyPress theme file? Instead, create this function in your bp-custom.php file. That why, when you upgrade BP, your changes will not be lost–assuming that you do not delete your bp-custom.php file.

2. The user ID field does not contain string content. So:

   u.ID = %s

   should be

   u.ID = %d

3. What you are after is grabbing a member’s ID and then using that to pull their login name (username). I don’t think that the variable $username is available for the function call–at least not the way you are trying to reference it. I would use this instead:

   $bp->displayed_user->id

   You will need to declare bp as global in your members-loop.php file.

Do what gerikg said.

Login to your WPMU backend and navigate to “BuddyPress > Component Setup”.

Check “Disabled” for “bbPress forums” and you should be good to go!

*The one thing that probably has you confused is you need to login to your bbPress admin area and manually delete your existing group forums.

Why not cut off the link between BB forum & BP Groups.

DISABLE

bbPress Forums

Activates bbPress forum support within BuddyPress groups or any other custom component.

Hi Korhan,

In these thread the user states that some items failed to work:

https://buddypress.org/forums/topic/buddypress-103-with-wpmu-284a#post-22006

I just installed 2.8.4a and would like to install for the first time BP 1.0.3

Don’t want to install BP until make sure it will work. If I install BP and fails to work, could it be a problem to Deactivate it?

Thanks.

So far in my experience:

1. creating groups and appearing in the Forums, works.

2. I’m able to get the templates integrated to a point, avatars and PMs I’m working on now.

3. Avatars aren’t talking to each other. (there are three different locations to pick which avatar, they need to fix that)

Admin section -> Buddypress -> Component Setup -> Disabled ( Groups Let users create, join and participate in groups.)

Once version 1.1 of BuddyPress is released, the Skeleton Theme that is currently bundled with BuddyPress (up to version 1.0.3) will be discontinued. Instead, BuddyPress will adopt the parent/child theme architecture that WP 2.7 made possible.

Learn more about parent/child themes in WordPress.

It’s a bug. It might be https://trac.buddypress.org/ticket/909.

BuddyPress currently only runs on WPMU.

As far as your question:

…is there a way to convert my wordpress right now on my site to WordPress MU?

There are many resources on the WPMU site and threads in their forums that will help you in this regard.

When you run on the bleeding edge, you have to accept the changes!

The BP themes that WPMU DEV currently provide are are not designed with the parent/child architecture in mind. You need to talk with them to get support.

Details About the New Theme Architecture

With BuddyPress version 1.1–which will be officially released in the next several weeks–there will no longer be bhome and bpmember themes. Instead, BuddyPress will adopt the parent/child theme architecture that WP 2.7 makes possible.

Backwards compatibility will remain for a while for those that want/need to use the old theming architecture. To use the old theme architecture, you need to keep the /bp-themes/ directory. Place your old member themes in there. BuddyPress should override the new theme architecture in favor of the old one if you have a /bp-themes/ directory. However, please note that support for the old theme architecture will eventually be phased out. You will eventually need to update your themes to a parent/child architecture.

Learn more about parent/child themes in WordPress.