BuddyPress.org

Hi @ankitjoshi11 – Check out the file buddypress/bp-friends/bp-friends-functions.php. The functions you’ll need are:


friends_add_friend( $initiator_userid, $friend_userid );


which accepts a third $force_accept parameter which makes it unnecessary for user B to manually accept. If you want to handle acceptance separately, look at…[Read more]

Hi @jeffm2008 – Thanks for the post!

I’ve just had a look at how Jetpack handles this. Unfortunately, it looks like it’s probably fundamentally incompatible with the way that BP’s top-level pages work. While BP does use WP’s page infrastructure in the Dashboard, it then tricks WP into thinking that BP pages are *not* in fact WP pages at the time…[Read more]

Thanks for the quick response.

Looking over some of the earlier posts, it is weird that the message says “For better results, make sure to upload an image that is larger than 0px wide, and 225px tall.”. This suggests that theme is set up in such a way that it sets the cover image width to 0. As such, it’s possible that it’s being rendered, but…[Read more]

You don’t say which fb plugin you’re using. Anyway, you’d be best served to ask the author of that plugin really.

Exact location of this depends on your theme, of course, so this is based on themes that are using BP Legacy.

When a group admin views the single forum post, at the top of the post you should see the date on the left and then options at the right: CLOSE | STICK | MERGE | BIN | SPAM | REPLY – just click on STICK.

This will stick it to the top of…[Read more]

Hi @wackao – Thanks for the post. I agree that the REST API could be a big driver for future adoption. (And I obviously agree that BuddyPress is a superior product to its competitors!) That being said, the BP team is a group of volunteers. The folks who build BP are professional and serious, but they work on projects that interest them, according…[Read more]

@almostsultry – It depends on your setup. By default, on Multisite, WP user objects are not created at ‘bp_core_signup_user’. By default, on non-Multisite, users *are* created at the time of registration (ie ‘bp_core_signup_user’). This behavior may be modified by other plugins, especially those that interact with the login process (like SSO…[Read more]

Hi @barkins – Unfortunately, BuddyPress doesn’t yet have a full set of CRUD endpoints for BP objects. The team is working on it, and we hope to start rolling out endpoints in the near future. BP-REST is the repo to follow for that.

BP will work fine with the default WP REST API, if all you want to do is access a list of users. However, WP’s user…[Read more]

@shanebp is correct that you’ll need to choose a hook where the user ID is made available.

Unfortunately, ‘bp_core_signup_user’ may be too early. On some setups (specifically, most Multisite configs) no user has yet been created at ‘bp_core_signup_user’ – only a signup object. The earliest point when you can be confident that a WP user object…[Read more]

Hi @julienbr – Sorry you are having problems with this. Invite Anyone should use the same mechanism for sending emails as WP itself uses, so the first thing I’d check is whether WP emails are being sent. For example, do you get an email when you initiate a password reset?

If the problem seems specific to Invite Anyone, you should check to see…[Read more]

Yes, this can be done in code. You’ll need two filters. One removes the unwanted items from the dropdown on the activity page, and the other removes them from the activity stream itself.


add_filter( 'bp_get_activity_show_filters_options', function( $filters ) {
unset( $filters['friendship_accepted,friendship_created'] );
unset(…[Read more]

The easiest way to customize things like this is by creating a child theme and overriding the template – in this case, members/register.php. See https://codex.buddypress.org/themes/theme-compatibility-1-7/a-quick-look-at-1-7-theme-compatibility/#child-themes for some information on getting started with child themes.