BuddyPress.org

See https://buddypress.org/forums/topic/faq-how-to-code-snippets-and-solutions, “How to hide selected profile fields” and “How to show secondary profile fields while hiding the “Base” profile fields in a user profile”.

These should get you started and this has been discussed elsewhere on the forums, so do a search.

I have “WordPress Failure Notice” error you are getting, webatease with BP v1.0.3. I haven’t spent any time investigating it further yet tho.

Can someone confirm whether this is a known with no current fix in the existing version or plugins?

I am getting the emails appropriately, but when I click on the link to approve/accept the group add, it gives me a website with “WordPress Failure Notice” at the browser title, and it asks “Are you sure you want to do this?” But it has no option for me to select yes, or check anything to actually approve. So this is still in the queue.

Similarly, I cannot reject the request – and if I click on the link in the email that says to view the request, it takes me to the user’s profile – but the request is not listed. In fact, in his of groups, it lists (1) as the number of groups (assuming because he requested), but then underneath it says he “hasn’t joined any groups yet.”

This does look useful to me, at least! But I want to confirm before I make the change.

My line 267 in bp-blogs-classes.php currently reads

if ( !(int)$wpdb->get_var( $wpdb->prepare( "SELECT DISTINCT public FROM {$wpdb->base_prefix}blogs WHERE blog_id = %d", $blog_id ) ) )

So you’re saying I should just replace

$wpdb->get_var( $wpdb->prepare( "SELECT DISTINCT public FROM {$wpdb->base_prefix}blogs WHERE blog_id = %d", $blog_id ) ) )

within that line? Or the whole line?

I haven’t updated bpgroup to be compatible with trunk bp yet. There’s a trac ticket by me whining about the lack of wp actions on group creation with the new group creation stuff.

I experienced a similar problem as well.

Did you edit a BuddyPress core file using a bpGroups function?

You should let Burt Adsit know of your fix, so maybe he can provide a cleaner solution using his plugin instead of editing the core:

https://buddypress.org/developers/burtadsit

—

Try adding this to line 161 of /wp-content/mu-plugins/oci_bp_group_forums.php

add_action( 'groups_create_group_step2_save', 'oci_bb_group_updated', 10, 1 );

See if that does the same thing.

bbPress does not have any native ways to hide forums that should be hidden. You can do as I have done – installing a “blank” theme that redirects users to your main site, limiting users to use the built-in group forums functionality only – or you could install a bbPress plugin that hides forums from those that are not allowed to view them. There is such a plugin, intended specifically for buddypress users, but I can’t remember what it is called.

It’s important to note that BuddyPress is an opensource project, just like all of the other WordPress related ones. That being said, if you find something isn’t working up to your expectations you are free to develop or contribute to the project to make it work how you wish. As it stands today, BuddyPress does a good job of keeping tidy and cleaning up after itself; better than most plugins in my opinion. The signups table is specific to MU and is a new addition, so you can expect it’s functionality to be misunderstood. When a user is deleted, the idea is that their signup remain in the signups table as proof of their previous registration. One could even argue that removing all user data is a bad idea in the event someone ever needs it later, say for law enforcement purposes.

Regarding blocking spam registrations, read some articles about Twitter. Some analysts have said that nearly 50% of all registrations on Twitter are spammers. Crazy eh? There just isn’t a fool proof way to prevent it from happening unfortunately.

Also, while none of the moderators are directly employed by Automattic, it’s about the best internship I think anyone in our respective businesses can hope for. We all do our best to represent Automattic and are here to help to the best of our abilities.

If you can find a specific bug or flaw in how users are currently managed between BuddyPress and WordPress, you’re welcome to respond here or file ticket in the trac. If you feel your opinion warrants more attention you can message me privately if you’d like also, and I’d be happy to help further.

Ah sorry about the lingo, Erich73!

I meant on my local, test install of WPMU and BP.

I can’t say for sure that upgrading will fix your problem, because if DJPaul is having the same problem, then it must be a legitimate problem!

Although I’m not sure which version of BP DJPaul is running.

—

I’m just going to try and clarify a few things here.

In the “private group invite” email I received, this is what I got:

One of your friends Ray has invited you to the group: "Private Group".



To view your group invites visit: http://localhost.localdomain/members/test/groups/invites



To view the group visit: http://localhost.localdomain/groups/private-group



To view Ray's profile visit: http://localhost.localdomain/members/admin

I click on the first link and it takes me to a BP Group Invites page, which allows me to accept or reject the invite.

—

This is the process you guys are talking about right?

Or are you talking about accept / reject links from within the email?

Hmm… Erich73 and DJPaul, private group invite worked for me on my sandbox BP install.

I’m on WPMU 2.8.1 and BP 1.0.3.

Excellent! Someone else with this problem. If a third person could test and confirm, we’ve got ourselves a live one!

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?