BuddyPress.org

Rohan, think before you type.

A private community would want their pages and content private.

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.

There have been several threads about this, including some useful code, but also lots of loose ends and confusion:

Securing components from non logged in users

Make access members/groups sections members-only

Plugin to show components to registered Users only

Apparently a “full-featured privacy (authorization) component for BuddyPress” is in the works for a future release.

Did you find a way to do this?

You can’t. It’s private for this site only, mainly because BuddyPress’ lead developer, Andy Peatling, doesn’t want every site to look like the official BuddyPress site.

This has been asked and answered several times on this forum before; doing a search before posting your question doesn’t hurt!

This is a private cookie used for the signup process. It is checked and cleared on any other page than the signup pages.

Report a bug please.

Yes, I’d like more group functionality and this is obviously a big one! These plugins could be starting points:

Private Files

File Uploader 1.0 Beta

Custom Upload Dir

Haven’t looked into any of these in detail…

Always upgrade themes when upgrading bp they are part and package. The themes are the front end to new and fixed features.

Someone reporting email issues with groups as well: https://buddypress.org/forums/topic.php?id=3183

All this talk about cookies is making me hungry.

Initially it sounded similar to the multi-messaging bug that we discovered 4 weeks ago. But that bug did still successfully send the messages to all the email recipients. It was just that the contents of the email were blank depending on whether you were the first person on the recipients’ list or the second.

This is different since the email is simply not sent to the second person.

We don’t even know if cookies are the issue.

His cookie domain info was set to “”. It’s not that it wasn’t set. It was set to null. So if wp gets to a spot where it wants to set it to a sane default value, it detects that it’s already set and doesn’t. Probably. The empty string is a value.

They would get loaded after the WPMU ones, so if there’s no check for them pre-existing, then they obviously overwrite them.

I currently don’t have a cookie_domain setup in wp-config.php either and everything works fine. It should get assigned by WPMU in wp-settings.php if it isn’t in the config.

In the wp-config.php file, verify:

$base = '/';

define('DOMAIN_CURRENT_SITE', 'domain.com' );

define('PATH_CURRENT_SITE', '/' );

define('SITE_ID_CURRENT_SITE', 1);

define('BLOGID_CURRENT_SITE', '1' );

…where domain.com is obviously your domain. If you are using any settings unlike what I posted above, paste them here please.

I wonder if the messaging system uses cookies?

It doesn’t sound really like the issue the 3 of us found. Does it? I just got finished working with somebody yesterday. His problem was that creating one group after another on the same computer caused the 2nd group to adopt the group id of the 1st group.

The underlying issue and solution was that he didn’t have any cookie domains set in wp-config.php

https://buddypress.org/forums/topic.php?id=3452

These cookie issues are tough to debug. We do the ‘works for me’ thing because our wpmu instances are different. Right now bp relies on the wpmu instance supplying the cookie path and domain. Perhaps to cover such situations bp should specify it’s path and domain. Would that bypass the wpmu credentials? Would it matter?

Here we go again. Burt, Jeff, man your battle stations.

We’ll take a look at it.

Right now on testbp.org it looks like it’s working correctly. Was this an upgrade from a previous BuddyPress install, and if so, did you upgrade your member theme files also?

Ilya is correct about not having the ability to delegate.admin powers to a moderator. This is a very crucial issue. In a large community, people come and go. Their interests and time change. So say someone creates a group. They by default become an administrator. That means they are the only one to have the following powers in a group:

• Group Settings
  Group Avatar
  Manage Members (i.e. bump them to moderators)
  Delete Group

So if we play out this scenario, and the administrator has fallen off the radar, the group settings from public to private to hidden cannot be changed except by the Buddypress site admin. The Buddypress site admin can elevate members to moderators but they CANNOT add an adminstrator, as far as I can determine. The Buddypress site admin can delete the group but the only way to “delegate” administrator powers would be to follow this scenario:
Appoint a moderator willing to take over. Have them create a new group, and then do a mass invite to join that new group via a news post or a friends invite.

Can a administrator be changed at the db level? Not sure.

What about asking the group administrator to exercise their option to ‘leave a group?’ I have no idea what that would do to the db and the Buddypress system. I’m hoping Andy or Jeff might chime in here on this odd possible outcome.

Cheers,
Brian