BuddyPress.org

That is what I would do.

But keep in mind, you’d also have to make the same changes to your BP member theme.

If you’re using the default BP member theme, that would be located here:

/wp-content/bp-themes/bpmember/header.php

I’m guessing from that statement that you don’t.

You’d probably want to make some changes in your theme’s header.php.

If you’re using the BuddyPress home theme, that file can be found here:

/wp-content/themes/bphome/header.php

The part you want to look for is:

<ul id="nav">

John could probably help you better.

Not sure why the Members link is lighting up… that should only light up when you go to domain.tld/members/.

I’m guessing you’re using the BuddyPress home theme.

Do you have a customized BP_MEMBERS_SLUG, per chance?

Goto your blog settings and assign the front page to be the page you made for home, and make the index/blog page the one you made for your blog.

In your WPMU admin area, go to “Settings > Reading”.

Select “A static page”

Then for the “Front page” that you created, select “Home”.

For your “Posts page” that you created, select “Blog”.

As enthusiastic as you are about WordPress, most of us are about BuddyPress, so without speaking for anyone else, my opinion is biased towards using BuddyPress for every website. My moms knitting website will use BuddyPress.

If you want users to be able to blog about their own stuff without moderation, then you want WordPressMU, because each user gets their own blog to talk about whatever they want; WHATEVER they want. That means even though your site is about fashion, that doesn’t stop them from talking about puppies.

If you want these users to be able to interact with each other, and have personalities, then you want BuddyPress.BP will allow your users to talk to each other privately, form groups to talk about things with each other, and comment on each others profiles.

The reasons NOT to use BuddyPress? At the moment there’s very little restrictive control over what people do. You can’t stop someone from putting profanity in their profile. You can’t block a user from messaging you or others. Also, the platform is still evolving as much as WordPress and bbPress are. That means that if you like to keep your website on the cutting edge, you’ll find it hard to install everything and leave it alone, as enhancements and improvements are coming through at least monthly, and so far upgrading isn’t a one click thing yet (almost though)

Those is my opinionses… Not sure how helpful they is, but if you like WordPress, you will probably see the potential of BuddyPress for what you want your website to be.

I’ve used this website before as an example and I hope he doesn’t mind, but check out leadpress.com as an example.

You’re not running BuddyPress in a sub directory, but actually just stopping it from taking over the root and /blog URLs, and instead using the normal WordPress way of assigning pages.

Rename home.php to community.php.

Use the Page Template method to name that page template “Community.”

In the blog admin, Make a page for your home, a page for your blog, and a page for your community, all with similar slugs.

The community page will use the “Community” page template.

Goto your blog settings and assign the front page to be the page you made for home, and make the index/blog page the one you made for your blog.

Then, you will want to install bbPress in a folder called “/community/forums/” and be sure to create a page with the slug “forums” as a sub page of “community”

That should do it?

Take a look at https://wordpress.org/showcase/ for examples of some of the best sites built on WordPress. WordPress itself is a stable and exciting for building sites and CMSs on, and the showcase which I’ve linked you to will let you browse the highlighted best.

The ‘biggest’ BuddyPress installation – other than this site – that I am aware of, is GigaOM Pro.

I’m not going to sell the idea of using BuddyPress to you but perhaps if you make a short list of the key features and ideas that are essential, and things you would like to have, we can all comment the feasibility.

Well, if you’ve already read this https://codex.buddypress.org/how-to-guides/modifying-the-buddypress-admin-bar/ and maybe this https://buddypress.org/forums/topic.php?id=2283, and do not understand, unless you are prepared to further your understanding of PHP and WordPress’ API, you need to find a developer to write the code for you.

I can see that you have cross-posted this over on the WPMU forums. You have a response from andrea_r, about an hour ago (as of time of posting), which you have replied to about 40 minutes ago.

This is definitely a WPMU question as this doesn’t involve BuddyPress, so you were right posting it there, but there was no need to post it here.

Sir

Please stop posting the same message. There is one lead developer on BuddyPress who works for Automattic, and he has a roadmap full of things to work on. The current target is BuddyPress v1.0.4 (a bugfix release) and as you can see from this thread, there are lots of known bugs to resolve to get v1.0.4 out the door, let alone implementation of any new features.

If for your website there are some priority features you require which haven’t been written yet, either learn to code/code them in yourself or hire someone to develop them for you.

Of course John is correct. I failed to notice that you were running BuddyPress hence my “This is truly a question for the WPMU forums” comment.

There is a constant set in bp-core.php (line 15) that allows you to set the blog ID on which BuddyPress will run. But as the trac ticket John referenced in his post indicates, setting it to anything other than “1” will currently cause issues.

Also, this ticket applies: https://trac.buddypress.org/ticket/775

Point 1 – No one has tackled this yet.

Point 3 – http://manojkumar.org/bppicture-album-plugin-for-buddypress/

As DJPaul has said, this is a 3rd party plugin, which isn’t an official BuddyPress component, but does a good job. An official BuddyPress album plugin is in the works.

John:

I have been having the same problem since moving my bp install from id1 to id30.

I tried all the ‘suggestions’ on the forums and patched the files, but bp still seems to save all files like avatars, photo album plugin pics etc in id1 instead of id30…

Looking at the ticket, it looks like it’s assigned to 1.0.4… is this the case?

If so I am guessing that it would be best for me to wait for 1.0.4 to come out instead of trying to hack it together to fix it?

It seems really strange to me that buddypress only works on the primary blog. What I don’t understand is why this would be the case. Buddypress is so far away from what I would call ‘production’ ready status, that it makes no sense to me to run it on my primary mu blog. Isn’t buddypress in it’s current state better to keep in the background, away from others until it’s more stable?

not ranting here, luv buddypress, I just can’t use it as primary but do want it running ‘in the background’ so I can keep adding features and testing etc…

btw

(gave up on trying to update to 2.8 series.. never did stop spitting out errors, so prob just going to wait for 1.0.4 anyhow.. thanks for your time answering emails on it)

This is actually more tricky that it sounds, because BuddyPress by default stores most of its information in the blog ID = 1, and it will ignore most other constant settings. If you are installing BuddyPress for the first time, and change any of the BP_ROOT_BLOG or BLOGID_CURRENT_SITE or SITE_ID_CURRENT_SITE variables, BuddyPress still saves most of its information in blod ID = 1.

https://trac.buddypress.org/ticket/823 references this issue, and I’ve included a patch for the instances where this occurs.

lynnallan, I’m afraid there isn’t a core solution for what you want to do yet, but the patch in the trac ticket *should* better prepare BuddyPress for this type of installation.

My only other suggestion, would be to think of it as WHERE the data is in the database doesn’t REALLY matter, unless you’re trying to split server load up across multiple database servers. That being said, you can install your corporate theme on your root blog, and then install the bphome theme on another blog, and then use the WordPress page template ability to recreate the look and feel of a BuddyPress on a blog other than the root. This is kind-of how http://leadpress.com/ has their site setup, if you need an example.

Rename the buddypress directory to something else. That will force it to deactivate and you can trouble shoot your installation from there.

Taken care of with patch for potential fix.

https://trac.buddypress.org/ticket/875

You’ve got it, Decisionc!

That, or until this is fixed in the source.

Submit a ticket (login with the same username and password as on buddypress.org) for this to hopefully see its inclusion in the next release of BP.

Okay, let’s start with the basics. Please answer these questions.

You’ve already provided the version of WPMU and BP that you’re running, so you can skip those questions.

@Julient

It sounds like a different issue. I assume that you are not getting the WSOD?

If that is the case–that you are not receiving the WSOD–then you should create a new thread as this one is resolved.

I don’t know if it has something to do with the issue, but members who register and don’t create a blog are automatically assigned as subscribers on the root blog. This means that there are hundreds of users assigned to this blog. May this be a problem with buddypress ?

This is normal WPMU behavior. It has nothing to do with BuddyPress.

Hi Jeff,

Looks like I’m facing the same problem : I can’t login as the Site admin, but the other users have access to their backoffice and see the buddypress Admin bar (meaning Buddypress is active).

I tried to switch to the default BP theme for the home page, but the issue remains.

I don’t know if it has something to do with the issue, but members who register and don’t create a blog are automatically assigned as subscribers on the root blog. This means that there are hundreds of users assigned to this blog. May this be a problem with buddypress ?

Do you see where the problem may come from ?

Thanks in advance for your help

Julien

The NextGen Gallery plugin is a vary powerful and popular tool for WP bloggers. I suggest contacting the developers and asking them if / when they plan to support BuddyPress. Also, perhaps they will have some insight into this issue.

Whether this plugin is causing your particular issue is yet to be determined.