BuddyPress.org

You need to talk to your web host and ask them.

1. Which version of WPMU are you running?

.wpmu 2.8.4

2. Did you install WPMU as a directory or subdomain install?

installed as directory

3. If a directory install, is it in root or in a subdirectory?

its a root directory

4. Did you upgraded from a previous version of WPMU? If so, from which version?

fresh installation from scratch

5. Was WPMU functioning properly before installing/upgrading BuddyPress?

yes it is

6. Which version of BuddyPress (BP) are you running?

version 1.0.3

7. Did you upgraded from a previous version of BP? If so, from which version?

its a fresh installation

8. Do you have any plugins other than BuddyPress installed and activated?

members only plugin

9. Are you using the standard BuddyPress themes or customized themes?

its the standard theme

10. Have you modified the core files in any way?

have never touched the core files

11. Do you have any custom functions in bp-custom.php?

nope

12. If running bbPress, which version?

hvnt install bbpress

13. Please provide a list of any errors in your server’s log files.

there isnt any

https://trac.buddypress.org/browser/tags/1.1-beta/bp-forums/bb-config.php

If you are not providing users direct access to your bbPress forums, then you can delete your bbPress files, if you are then leave them alone. You do not need the buddypress-enable.php file anymore.

I can’t speak for plugins, but if the forums in question are attached to private groups then they will not show up. They will remain hidden in the new directory when accessed through BuddyPress.

If you are not running a highly customized bbPress install, definitely consider using the new forums directory instead of a separate bbPress setup. The integration is seamless and requires no messing with cookies, integration settings/plugins.

Waclaw-

Are you aware of the Open Stack? Integration of the Open Stack is on the BuddyPress roadmap for sometime around version 1.4. It will do what you are proposing and more. If you want a real challenge, you can start working on integrating the Open Stack into BP!

@aero7

The first steps are to distill your install down to the lowest common denominator. That means disabling all plugins except BuddyPress and switching to the default theme framework that comes with BP. If the problem goes away, then it has something to do with your theme and/or plugins.

If that is the case, they the next step is to reactivating each plugin one at a time until the issue returns. If it does not return, then switch to your custom theme. If it returns, then there is an issue with your custom theme.

This was well discussed three days ago. Since this thread has not seen any action for a month until just now, I’m closing it as it is too out of date.

Another side note from Andy’s last paragraph, these BuddyPress extensions could come in just about any form; additional theme files to be added as a “plus pack” (remember those?!) or a plugin to override and replace existing files as a child theme, or included in the next version of the theme itself.

Also, if you’re paying attention the directory of the included parent theme is “bp-sn-parent.” It stands for “BuddyPress Social Network Parent” which insinuates that theme authors are encouraged to create their own parent themes for something other than social networking, and opens the door for other parent theme sets to be included in the core if they’re rad enough.

Say someone makes a sweet micro-blogging theme ala Twitter, that gives us “bp-mb-parent” to let you switch between totally different setups. Or say someone switches the emphasis away from blogs and users and shifts it to the discussion or support forums; that gives us “bp-df-parent” and “bp-sf-parent”

Andy’s right too. The majority of people so far interested in BuddyPress have been people that are also first being introduced to WPMU and starting a social network. Very few support questions come through asking how to port this existing theme to fit BuddyPress. The ones that do are typically answered by the theme author or the person is so devoted to making it work, that they convert the theme themselves.

I’m really not sure how much harder it is for existing themes to use BuddyPress; it’s just different, but in a better way in my opinion.

The situation can be summed up like this:

The BuddyPress 1.0 theme structure made it easy for existing WordPress sites to use BuddyPress out of the box (but only with the default theme which was never ideal). However, it made life very difficult for anyone designing a site from scratch with BuddyPress, and for 3rd party theme designers.

BuddyPress 1.1 makes it harder (but still very possible) for existing WordPress sites and themes to use BuddyPress, but makes it very easy for sites starting fresh and for 3rd party theme designers.

The number of people starting sites fresh using BuddyPress significantly outweighs the number of people trying to use BuddyPress within an existing WordPress setup. It is only logical to make the lives of the majority easier.

There will be more documentation on using BuddyPress with existing WordPress installations and themes once 1.1 is released. Let’s get it out there first.

On a side note – I’d really love to see existing WordPress theme designers coming out with BuddyPress theme extensions for their WordPress themes. This for me is the ideal scenario, let the top theme designers provide support for BuddyPress, rather than the end users trying to force a square peg in a round hole.

@crocgo

As I said above, we do not have the information necessary to help you. Please answer the questions DJPaul linked to.

I’d like to delve into this more deeply, but for now, even using the child themes there is an additional complication. It’s reasonable to expect someone to be integrating BP with an extant site using an advanced WP theme, and simply setting this theme to be a child of the bp-sn-framework doesn’t suffice. I’m working in one such setup, where a theme uses several include() statements in a functions.php file, and setting this as a child of the BP framework b0rks the whole deal. Now, I know what to do here, at least in the simplest case: just amend the functions.php calls. That won’t necessarily persist as the theme is updated, so maybe, instead, this can be done via a plugin.

The point here is that there are easily found examples where existing WordPress installations aren’t set up to so trivially extend to include BP. This one has a straightforward solution, but some will not. And as WP theme developers continue to do ever-more-amazing things with WordPress, and as you and other developers continue to make WordPress and BuddyPress more powerful, this sort of nonlinear theme infrastructure will likely become the norm. I don’t think these are quite edge cases, either; the theme I’m testing with is a free Woo theme, so not quite off the beaten path.

I don’t want to add to the confusion. Rather, I wonder if I could help flesh out some use cases, which might later get wrapped into the documentation (if it’s helpful). For instance, there is the site that purports only to offer social networking, without long-form blogging intentions. In that case, Using bp-default with customizations is pretty straightforward–well, as straightforward as the styling for the site needs to be.

However, for folks who have an existing WP site to which the BP functionality will be at most equal in priority, their branding and existing structure may be complicated enough that simply setting their existing theme to be a child of the BP framework doesn’t work by itself (styling issues aside–there will always need to be style adjustments; this is about structure and objects). Again, as my example demonstrates, this complexity is closer to the norm than some might expect, especially among the crowd using WPMu and extending it with BP. In this case, there’s more to document.

I don’t intend to suggest, as some have, that BP developers need to rethink or revise BP’s scope and structure. That’ll probably happen anyway, as things start merging more, but it’s not necessary. I only mean that the adaptation of BP to an extant site is a nontrivial use case, and while there is forthcoming documentation as to how best to manage this, maybe the forum users and devs can spec out some general use cases and work on how best to develop their solutions.

catinw12, you shouldn’t need to create any new profiles anywhere. All of the .org sites should provide you a unified login/password combo to use on wordpress.org, bbpress.org, buddypress.org, and all of their respective trac’s.

I have no idea what will work for you. I was just detailing what I needed to do.

If your WPMU and server environment were setup properly to begin with, and you followed the instructions in BuddyPress’ readme.txt file, you should have no issues upgrading. But, for me, I had unknown issues in my original setup environment that caused problems. So, I had to go through the process I tried. It may or may not work for you.

To do a clean WPMu reinstall, you will want to delete the WPMU install completely–this means everything including the folders. Once reinstalled, you can go grab the most recent BP trunk and manually install before reactivating it.

Okay, so everything is standard issue.

I had a similar problem when I upgraded one of my development sites to pre1.1. I ended up reinstalling from scratch–both WPMU 2.8.4a and BP trunk. I did a clean install–sort of. First, I deactivated BuddyPress since I planned on using the same DB.

Then I dragged my wp-config.php and .htaccess files out of the root directory before deleting everything else in the root directory. I reinstalled WPMU just by copying the files back into the empty root. I then put back the wp-config and .htaccess files, logged into WPMU as Site Admin, and reactivated BP and reselected the BP themes.

My problem went away.

By the way, if you are running WPMU in a development environment and you selected the subdomain install option for blogs, you will have an issue if you have not set up a wildcard DNS record and have more than the main blog. I had this issue with one of my dev sites.

What happened was that it threw an error when I upgraded Mu form 2.7.1 to 2.8.4a. It could not properly upgrade any of the test blogs (other than Blog ID 1) since it could not resolve the subdomains. I had not set up a wildcard record for that dev site.