BuddyPress.org

First, before doing anything, always read the readme.txt file that comes with the install package–this includes the WPMU and the BuddyPress packages. It has important information–especially about what you need to do with the theme files.

Since BuddyPress resides in its own directory, I would suggest deleting the old install. You should not have any issues if you do this. Why? Because any of the plugins, themes, or custom code that you may be using should exist outside of the BuddyPress directory. Before deleting the BP directory, you need to make sure that you deactivate it in WPMU’s backend.

Furthermore, just in case, it is always prudent to have recent backups of your custom themes and your plugins before deleting anything. You want to be absolutely sure that if you accidentally delete the wrong files or directories, that it will not be a big issue since you can simply copy them back. I also suggest that you have a recent copy of your wp-config.php file and even the .htaccess file (assuming that you have plugins installed that may have altered the default congifg).

Since this is a fresh install, I would also suggest starting over with a new DB. If you already have data that you wish to keep in the DB–because you’ve been running WPMU for awhile in a production environment–then your only option is to manually delete the BP tables in the DB before reinstalling BP.

Also, since you are having specific issues with the activity tables, you will need to follow my advice in this post to get the activity tables to reinstall.

As always, before doing anything that affects the DB, please back it up. This also includes backing up your DB before each and every upgrade.

FYI:

https://codex.wordpress.org/Backing_Up_Your_Database

https://codex.wordpress.org/Restoring_Your_Database_From_Backup

As JasonG states, WPMU is really setup to work with a single domain. However, as he also points out, Donncha has an early-stage plugin that allows the mapping of a domain to a specific blog on a Mu install. It is called the WordPress MU Domain Mapping plugin.

Concerning getting the multi-site plugin to work with BuddyPress, there is a ticket in Trac that addresses a potential way to allow it to work with BP.

Yes, a media library / manager makes more sense… with wire integration and bulk uploading hopefully. Now… if a user has not just a BP Profile but also a Blog… they would then have two media libraries… their WordPress Media Library and their BuddyPress Media Library. But I guess that makes sense. The Blog is almost like another world. Right?

I actually have the same problem.

I’ve tried this patch https://trac.buddypress.org/attachment/ticket/909/909-jjj.patch but it still doesn’t work: I can’t say yes or no, there’s no button, just the question. Is it still working with your BP install JJJ?

Thanks!

I’m running WordPress MU 2.8.4a + BuddyPress 1.0.3

I think if you find a basic but good Paypal plugin for WordPress, that’s half the battle. The API is a bit awkward to work with (in my experience).

Have you talked to the WP e-commerce guys (http://twitter.com/danmilward) about bringing e-commerce into BuddyPress as a group plugin? I saw Dan present at Wordcamp UK and he seems quite a friendly chappy.

I think the only way you could have a 1-click option would be if… at some point… there were a buddypress.com like wordpress.com. That said… all of these projects are auttomatic projects… so maybe at some point in the future they will all merge into one product? Who knows.

Provided you have wildcard subdomains allowed in your installation, then yes this could be possible with some modification to both BP and your .htaccess rules. Similar to how http://support.wordpress.com/ works with the forum as a subdomain in addition to user blogs being subdomains too.

I’m using a plugin called WP Hide Dashboard on the primary blog:

https://wordpress.org/extend/plugins/wp-hide-dashboard/

This hides mostly everything from a subscriber.

Hope that helps!

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,

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.

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