BuddyPress 5.0.0 “Le Gusto”

We’re very happy to announce the immediate availability of BuddyPress 5.0.0 🍕. Please upgrade and share the news 😉

Here’s the official announcement post.

#5-0-0, #release

BuddyPress 5.0.0-RC2


The second release candidate for BuddyPress 5.0.0 is now available for an ultimate round of testing!

Thanks in advance for your help 😍

#5-0-0, #rc

BP Dev Chat Summary, September 18

5.0.0’s schedule

🎯 5.0.0 release: ~ September 30.

About 5.0.0 RC1

The release candidate was packaged on September 17. A few hours late comparing to the schedule: @im4th explained this was due to last minute fixes he had to do about failing unit tests for WordPress trunk (5.3 dev cycle).

So far no feedbacks were published about this release candidate in BP Trac or in BP Support Forums.

BP Rest API Documentation site

A first version of it is now available on developer.buddypress.org. There is still work to achieve to improve the responsiveness of the theme and the way it integrates itself into the BuddyPress.org network.

@boonebgorges and @im4th agreed it was ok to launch it in this state. @im4th will soon post about it on BuddyPress.org so that BuddyPress developers are informed about the BP REST API handbook availability.

5.0.0 remaining tasks

@boonebgorges will work on extracting the release props next week. As the BP REST API has been maintained on GitHub so far, we’ll need to incorpore manually these contributor names. He & im4th will also review the “Recent Rockstars” list.

@im4th will take care of drafting the first version of the announcement post and writing the release page on the Codex.

About the 🍕 name of the 5.0.0.. It’s a surprise !

Next dev-chat

It will happen on October 2 at 19:00 UTC in #BuddyPress slack channel 2 days after the 5.0.0 release. We will talk about its first feedbacks and about our first ideas for the next(s) development cycle(s).


BP Dev Chat agenda: September 18, 2019.

This is the agenda for our next Dev Chat which will happen this Wednesday (tomorrow) at 19:00 UTC in #BuddyPress.

  • 5.0.0-RC1 first feedbacks.
  • A first version of the BP REST API Documentation site is ready. Let’s discuss about how to announce it to our community.
  • 5.0.0 remaining tasks :
    • Announcement post,
    • Release page on the Codex,
    • Recent rockstars & release props,
    • 🍕 name for the release!

If you have anything you wish to add to this agenda or specific items related to those listed above, please leave a comment below.


BuddyPress 5.0.0 Release Candidate

Hi everyone,

The release candidate of BuddyPress 5.0.0 is available for testing. Read more about it in this announcement post.

Thanks in advance for your tests 😍

#5-0-0, #rc

bp.apiRequest(), your JavaScript Buddy to help you start using the BP REST API

In BuddyPress 5.0.0 (Release date ~ September 30, 2019), we’re introducing the BP REST API: a new way for BuddyPress developers to interact with the components of BuddyPress powered community sites.

If you’re familiar with the WordPress REST API, you should easily find out how to use the BP REST API as it extends it to provide new community oriented endpoints.

The BP REST API, just like the WP REST API, uses a cookie authentication. You need 4 things to get a response from one of the BP REST API endpoints :

  1. The rest_nonce
  2. The WP REST root URL rest_url()
  3. One of the available BuddyPress endpoint’s path, for example /buddypress/v1/members
  4. The transport method (GET, POST, PUT, DELETE, OPTIONS).

You can build everything yourself into your JS script making sure to carry points 1. & 2. from PHP using the wp_localize_script() function.

You can also add a dependency to bp-api-request when enqueueing your JS script to :

  • save some time ⏱
  • make sure it will work for all the WordPress versions BuddyPress supports (4.7 to latest) 😅

Adding a dependency to bp-api-request

    'your-plugin-js-handle', // The handle to use when enqueueing your script.
        'bp-api-request', // The dependency to add to use the bp.apiRequest function.
    '1.2.3', // Your plugin version.
    true     // True to load your script into the footer. False otherwise.

Doing so, you’ll just need to enqueue your JavaScript file at the right time and for the right context using wp_enqueue_script( 'your-plugin-js-handle' ) without having to care about the REST nonce and the WP REST root URL.

function your_plugin_enqueue_assets() {
    // Only loads the JavaScript when a user is viewing his profile.
    if ( bp_is_my_profile() ) {
        wp_enqueue_script( 'your-plugin-js-handle' );
add_action( 'bp_enqueue_scripts', 'your_plugin_enqueue_assets' );

Using bp.apiRequest() within your JS script

The only elements you’ll have to care about are:

You’ll need to group all these elements into an object looking like the highlighted lines below:

( function( bp, $ ) {
    window.bpRestApiResponse = {};

    var helloBPApiRequest = function() {
        bp.apiRequest( {
            path: '/buddypress/v1/members/me',
            type: 'GET',
            data: {
                context: 'view',
        } ).done( function( data ) {
            bpRestApiResponse = data;
        } ).fail( function( error ) {
            alert( error.message );
        } );
    $( document ).ready( helloBPApiRequest );
} )( window.bp || {}, jQuery );

From there, If you log the bpRestApiResponse variable into your browser’s console when visiting your BuddyPress profile you’ll see the JSON object the BP REST API should respond to you.

Oh.. wait but how can I get all BuddyPress endpoint paths etc. ?

We wrote a complete documentation with an example of use for each endpoint. We will soon make it available on the BuddyPress.org network.

In the meantime, if you’re eager to have some fun with the BP REST API, simply replace /buddypress/v1/members/me with /buddypress/v1 into the helloBPApiRequest()function of the above example.

Logging bpRestApiResponse will now give you all available endpoints, their corresponding transport methods and arguments for your community site (The ones of your active BuddyPress components) 😉


BP Dev Chat Summary, September 4

5.0.0’s schedule

  1. Second beta release: September 10.
  2. First release candidate: ~ September 16.
  3. 5.0.0 release: ~ September 30.

Issues & Feedbacks about the first beta release

Some i18n issues appeared into the BP REST API code and have since been fixed by @espellcaste. @im4th will improve the bp.apiRequest JavaScript function before beta2 (#8131).

IAmTheWebb reported that he hasn’t noticed any regression issues but also informed us he hasn’t found the time to test the new features yet. The lack of ticket report is a bit worrying as it makes us wonder if the beta1 has actually been tested by BuddyPress plugin or theme developers 🤔.

@boonebgorges explained it wasn’t easy to test the BP REST API as it required building clients. Having the BP REST API documentation site available would probably help.

The BP REST API documentation site

@johnjamesjacoby & @netweb have been working on the developer.wordpress.org needed set-up to host the BP REST API documentation site. Although we are very confident they will soon fix #4601-meta, we decided to wait until September 20 before applying our backup plan.

In case we can’t make it on developer.wordpress.org @im4th will buy a specific domain name for the staging site we used to write the documentation and we’ll make this site widely available.

BuddyPress plugin & theme developers will be able to consult The BP REST API documentation before the 5.0.0 release 💯.

Hello BuddyPress modal

BuddyPress 3.0.0 introduced this modal to replace the Welcome Screen. We use it to inform about the new features introduced in the new major releases of BuddyPress.

@im4th shared a patch on #8132 to make this modal more inline with the WordPress Administration styles. @johnjamesjacoby shared his thoughts about it on the ticket and agreed during dev-chat that matching core’s modal would be best.

@im4th is 🇫🇷 so there are probably some english mistakes in the text parts of the patch. BuddyPress contributors : don’t hesitate to find and fix them 🙏


We decided to package a second beta next week to remind our contributors we need their help to test our contributions. Let’s not wait for the stable release to find bugs we could have avoided during the beta period!

Next dev-chat

It will happen on September 18th at 19:00 UTC in #BuddyPress slack channel, just before the release candidate.

PS: @dcavins couldn’t attend to the dev-chat but recently shared in our Slack channel he will soon publish an overview about the changes introduced by the BP Invitations API 👌.


BuddyPress 5.0.0-beta1

Hi !

We’ve just published the 1st beta version of our next major release. You can read more about it here: https://buddypress.org/2019/08/buddypress-5-0-0-beta1/



BP Dev Chat Summary, August 21

5.0.0’s schedule

Here are three important dates about our next major version:

  1. First beta release: August 28.
  2. First release candidate: ~ September 16.
  3. 5.0.0 release: ~ September 30.

BP Invitations API

@dcavins has committed this new API to manage Invitations/Membership Requests across components. The first BP Component to enjoy it is naturally the Groups one. Many thanks and huge congratulations for the accomplished work 👏🤝. See #6210 for more details about it.


Code improvements

  • He also adapted the Group Invites and the Group Membership Requests endpoints so that they are now using the BP Invitations API.
  • The create_item() method of the Group Membership controller is now taking in charge the action to let members join a public group.
  • WP_REST_Server::DELETABLE methods are now all returning an object with two keys. The first one informs about the success of the DELETE request and the second one contains the previous BP object as it existed before its deletion.


The content is almost ready! Documenting the Group Invites and the Group Membership Requests endpoints (the last ones) will be achieved before the beta release.

Making it available from BuddyPress.org is in very good hands @johnjamesjacoby will work on it asap to try to have it ready around beta release so that it should be easier for contributors to play with the BP REST API during our Beta/RC release steps.

How the BP REST API will be included into BuddyPress Core for this beta release?

To keep working from our BP REST GitHub repository to fix potential bugs / improvements, we will include it during our build process a bit like what happens today with BP CLI: see this comment on #7156 for more details.

This means:

  • the BP REST API plugin, if active, will take over BuddyPress, making it easier to carry on maintaining it from GitHub during the Beta/RC time.
  • If contributors are using trunk to beta test, they’ll need to npm install & grunt build to get the BP REST API into this build.

5.0.0 milestone’s remaining tickets

  • #8046 & 8093 have been moved to next release.
  • #8103 (BP Legacy Companion Stylesheet for Twenty Nineteen) is kept during the beta/RC to leave a last opportunity to include it before final release if it gets some contributions/testing.
  • #8123 will be committed asap & before beta release.

Beta Release tasks

  • @im4th will take in charge the beta release packaging
  • @dcavins will try to post on this blog to introduce the BP Invitations API
  • We still need to write the announcement post for BuddyPress.org. A draft for it is available on BuddyPress.org (the title is BuddyPress 5.0.0-beta1), don’t hesitate to add the information you think are important to mention. I’ll polish the writing part 🖼 📝

Next dev-chat

It will happen on September 4th at 19:00 UTC in #BuddyPress slack channel. Of course is something goes wrong with right after the beta release, we’ll always be able to meet next week.


BP Dev Chat Agenda: August 21, 2019

This is the agenda for our next Dev Chat which will happen this Wednesday at 19:00 UTC in #BuddyPress.

    • Latest updates about the code.
    • Documentation.
    • Let’s decide about how we will include the BP REST API in the beta release, see #7156
  2. Potential tickets to move to next/future release.
  3. Beta Release tasks repartition (Beta1 is scheduled to the week after this dev-chat).

If you have anything you wish to add to this agenda or specific items related to those listed above, please leave a comment below.