BuddyPress.org

@ John

I know Burt hasn’t updated the group blogs plugin in a while…

I believe that jeff is talking about this plugin and not Burt’s Community Blogs plugin.

Here is a plugin that should do what you want. Although I don’t know if it is tested on 1.1

https://wordpress.org/extend/plugins/limit-blogs-per-user/

@wordpressfan, you will want to make sure that wp-contents/plugins/buddypress/bp-forums/bbpress/ contains all of the files that come with bbPress.

When you use the auto-install functionality of BuddyPress forums, it will create a bb-config.php file at the root of your WordPress MU installation.

There appears to be some confusion (at least in my mind) on the steps needed to enable forums in the beta.

1. Do I place the bbpress files in bp-forums or not?

2. The forums “one-click” setup mentions placing the generated code in the “root WordPress directory.” Is that domain.com, bp-forums, or where?

Thanks.

@wordpressfan

You have several threads with various issues floating around the forums so I cannot possibly remember all the answers that you’ve already provided to our questions.

So, more questions/suggestions:

• Do you have any plugins other than BP installed? If so, deactivate them and see what happens. Make sure that you are using the default theme and that you have reselected it.
• Are there any errors in your server’s log files? I mean ANY. Do not try to decide which errors are relevant to this issue. We will decided.
• I believe that you are running BP trunk. So this is a test site as you should not be running the bleeding-edge version on a production site. Do a clean install and see if the problem persists. This means deleting everything–all BP, WPMU, and DB files. You need to start from scratch. Don’t install any plugins other than BP, only use the default theme. What happens when you do that?

As DJPaul, said, you should talk to your web host whenever you are having server issues. This WordPress codex article may help, if it does not, talking with your web host is the next option.

Yes. But any wordpress theme used on a buddypress site will have to include extra files that come with the BP theme. I.e copy them.

@John James Jacoby – is it ready what you described here 3 months ago?

I am searching for solution to make buddypress multilingual, but only in interface: theme and admin area should has multi language texts. ost dont have to be translated.

Just something like is at wordpress.com: user register and choose language. Then he see all interface in local language, write in any language he want.

Hi !

Seems to have good new functionnalities !

I have one problem though :

I use a fresh install (WPMU 2.8.4 + BuddyPress 1.1 Beta); no plugins;

I moved /bp-default and /bp-sn-parent to /themes;

and I get

Not Found

The requested URL …./wordpress-mu/blog was not found on this server.

Then I did copy my old .htaccess file to the fresh WPMU installation; and now I have

Page Not Found

The page you were looking for was not found.

What is the problem ?

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

In one word: no.

In BP 1.1, themes will work more like regular wordpress themes. I suggest you wait until then or develop your custom theme from a development version.

Closing this thread as gerikg’s taken it off topic.

I miss my nextgen plugin (doesn’t work well with MU)

I think Mark Jaquith recently said that the WP/MU convergence was expected to be completed by 3.0 or 3.1, so, that would be in either 3 or 6 months time.

Not really so very far away, I think.

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.

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.