BuddyPress.org

I’m using bpGroups and first of all you should follow the instructions properly.

Make sure your files are in the right directories.

/wp-content/mu-plugins/oci_bp_group_forums.php

/YOUR BBPRESS INSTALL DIRECTORY/my-plugins/oci_bb_group_forums.php

—

Also, because you’re using deep integration, you’ll need to make the following changes:

In oci_bp_group_forums.php, around line 30 change:

require_once(ABSPATH . WPINC . '/class-IXR.php');

to this:

if (!defined(BBDB_NAME))

require_once(ABSPATH . WPINC . '/class-IXR.php');

In oci_bb_group_forums.php, around line 30 change:

require_once( BACKPRESS_PATH . '/class.ixr.php' );

to this:

if (defined(BACKPRESS_PATH))

require_once( BACKPRESS_PATH . '/class.ixr.php' );

I have had this issue three times and all the time the only thing that has worked is a new install. That is, wipe clean the wp-admin, wp-content and wp-includes and all files for Mu , rename existing ones to something like wp-admin_old (that’s what I do).

Then:

1. Finish the WP MU installation/upgrade first. Make sure it does work before you go to the next step.
2. Install buddypress plugin first and activate it
3. Reupload the blogs.dir files to the wp-content from your backup manually.

This is guaranteed to work. So far, buddypress doesn’t seem to have any other magic solution to this issue.

1)

I do have BP-version 1.0.1 running on a site and have made a few customizations so far (just CSS-changes and some images).

So with the new template-structure: should I delete the current install completely and get the BP-version 1.1 installed ? I mean: what is the best way to upgrade to the 1.1-version when it will be released in the next few weeks ? I definitely want to have the new template-structure, so I guess I would need to set-up my website from scratch, right ?

And: I am running the site in german-language only.

2)

will this new template-structure also make it easier to design a custom-template for the user-blogs ?

Like I would like to have the user-blogs having the same CSS-style as my main pages ?

I still have not been able to figure how to do this. I would like the user-blogs to have the same design in order to have a consistent website.

Why is this not already the case at http://www.testbp.org ? Why is it still the original WordPress-design ? Is there a chance you create a plugin or something at which the Admin is able to select to chosse the design of the “User-Blogs” like choosing from “WordPress original design” or “TestBP.org design” ?

3)

is there a chance to have a “package install” which will have ONE package which will include all latest software: WordPress 2.8.x, BuddyPress 1.1 and BBPress ?

I read many post where I see people having troubles integrating the BBPress-software into the system (even an experienced BP-expert had troubles).

Is there a chance you will create a 1 Package download which will make it very easy for people to have a full website (like http://www.testbp.org) installed ?

So literally 1 click-download will create a ready-made website, same like testbp.org ?

4)

a user-request to get invited into a “Private Group” is not possible being accepted. This does not work yet at my installation and I think this is a general bug.

5)

the wording of “Blog” and “Blogs” is confusing. In both english and german language.

Many thanks,

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.