BuddyPress 9.0.0 is now available!


I have the great honnor to introduce you to “Mico” our latest major release. It’s ready for the new WordPress 5.8 Widget Block Editor. It was quite a challenge when we decided to build this release about a bit more than a month ago. We used a short time frame development cycle and we did it! I’m very proud of the work we’ve accomplished together: congrats to all the development team members, the contributors and the polyglots team members.

Have fun with the new 10 BP Blocks included into this release 🍕

BuddyPress 9.0.0 “Mico”

#9-0-0, #release

4 days to test BuddyPress 9.0.0-RC1!


We really need you to quickly test this release candidate as we plan to release it just before WordPress 5.8. If you want to test the 10 new Widget Blocks into the new Widget Block Editor, you’ll need WordPress 5.8-RC3 💪

Thanks in advance for your help 🙏

#9-0-0, #pizza, #release-candidate

BP Dev-Chat Summary: June 30/July 7, 2021

June 30 improvised dev-chat

Following the discussion we had during June 23 meeting about the frequently requested Follow feature, and a very interesting discussion between @sbrajesh, @espellcastewe and @johnjamesjacoby, we decided to improvise a new Dev Chat about a possible larger scope about it. We shared our views about building a wider vision for “relationship types” in BuddyPress. A new API that would firstly be used for the Follow feature, but could also be used for potential other needs: user likes, improved user favorites, blocking users, what may come to our mind in the future!

@sbrajesh will lead this new project using the “feature as a plugin” model like WordPress does from a BuddyPress GitHub repository. If you’re interested in contributing to this project, please “raise your hand” commenting this summary.

July 7 regular dev-chat

@im4th starts with an apology: unlike what was scheduled (July 8), we were not able to release the 9.0.0 first beta so far. Sorry about it.

9.0.0 🎯

We’ve migrated 90% of Widgets as Block Widgets from the GitHub repository we use to build BuddyPress blocks. We also improved some BP REST API endpoints and we’re on our way to include a new endpoint to deal with Sitewide Notices. BP Block Widgets have been built on 2 principles: use the BP REST API every time it’s possible and use Modern JavaScript on front-end and the Widget/Post Block Editor’s APIs (mainly built on top of React.JS) on back-end.

@dcavins has made great progress about the Sitewide Notices Block Widget (👉 the last one to reach 100%) and about the corresponding REST API Endpoints. @espellcaste gave great advices about the BP REST API to speed up the process.

We also talked about directly packaging a Release Candidate without doing a Beta release. As the 9.0.0 development cycle is focused on migrating Widgets as Blocks, we have a very limited risk of messing with other parts of BuddyPress. @im4th said he’ll work on merging the BP Blocks code into BuddyPress core and will try to find the time to quickly build a Beta Release and some time after the Release Candidate (he hates when he doesn’t do what he has written he would do).

We finally talked about the great work @vapvarun has done building a test drive to host the BuddyPress code reference. The goal is to make it available asap and before the end of the year here. The main difficulty is to generate the documentation using the WP CLI parser command directly from the server (10 minutes). @im4th wondered if this could be achieved using the WP import/export tool (the documentation plugin is using custom post types). This is an approach we’ll try to test to avoid possible downtimes of the BuddyPress.org network.

9.0.0 schedule

  • Beta: July ? 🤔
  • RC: July 12 to 14.
  • Final: July 16 to 19.

Next Dev-Chat

It will happen on July 21 at 19:30 UTC and of course in #BuddyPress. If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

Additional note about meetings during 9.0.0 development cycle

As we are running a short development cycle, @im4th will be available every Wednesday at 19:30 UTC in #BuddyPress for an hour or more time if needed. Don’t hesitate to ping him (@imath) for help or inputs about contributing to this version of BuddyPress.

#9-0-0, #dev-chat, #relationship-api, #summary

BP Dev-Chat Agenda July 7, 2021


Our development meeting will happen today (July7) at 19:30 UTC and of course in #BuddyPress.

Here’s our agenda:

PS: 9.0.0 is a short development cycle, here’s our schedule for it:

  • Beta: July 8.
  • RC: July 12.
  • Final: July 16.

If you have specific/additional points you need to discuss about, please share them into the comments area of this post.


#9-0-0, #agenda, #dev-chat

BP Dev-Chat Agenda June 9, 2021


Our development meeting will happen on June 9 (tomorrow) at 19:30 UTC and of course in #BuddyPress.

Here’s our agenda:

  • Feedbacks & results about « Alfano » 8.0.0.
  • BP widgets & the Widget Block Editor.

If you have specific/additional points you need to discuss about, please share them into the comments area of this post.


#8-0-0, #agenda, #dev-chat

BuddyPress 8.0.0


Meet “Alfano” our first major release for 2021!

#8-0-0, #release

BP Dev-Chat Agenda May 26, 2021


Our development meeting will take place tomorrow (May 26 at 19:30 UTC) in #BuddyPress.

Here’s our agenda:

  • Feedbacks about 8.0.0-beta2
  • Ticket needing attention: the Hello BuddyPress & Credits screens (#8468)
  • RC & string freeze.

8.0.0 release schedule’s reminder

  • 8.0.0-beta1: April 29
  • 8.0.0-beta2: May 20 ✅
  • 8.0.0-RC: 🤔
  • 8.0.0 stable release: early June.

If you have specific/additional points you need to discuss about, please share them into the comments area of this post.


#8-0-0, #agenda, #dev-chat

Nice! 8.0.0 will include a BP Email to welcome your new community members

If registrations to your site are open, your new members will now receive a warm welcome email once they activated their account.

Screen capture of the default Welcome email

By default its content is very simple, it contains:

  • a link to the user’s profile page,
  • a link to reset their password.

But as you probably know BP Emails are customizable emails, so you can edit this content and make it very unique to your community. Let’s remind ourselves how to achieve this.

First, from the Emails menu of your WordPress Dashboard, look for the [{{{site.name}}}] Welcome! BP Email, mouse over its title and click on the “Edit” link as shown above.

Then edit the content of your email with the text of your choice. I chose to use one containing a link using a custom email token: <a href="{{{groups.url}}}">. In order to replace the groups.url token with the Groups directory permalink before the email is sent, I need to make sure this token is defined using the bp_send_welcome_email_tokens filter. The code below shows you an example of how you can do it.

 * Add the Groups directory URL to the welcome email's tokens.
 * @param array $tokens  An associative array of email tokens.
 * @param int   $user_id The ID of the user who activated their account.
 * @return array An associative array of email tokens.
function bp_custom_code_add_groups_url_to_welcome_email_tokens( $tokens = array(), $user_id = 0 ) {
	// I known, as the Admin of the site, the Groups component is active, let's include a link to its directory.
	$tokens['groups.url'] = bp_get_groups_directory_permalink();

	return $tokens;
add_filter( 'bp_send_welcome_email_tokens', 'bp_custom_code_add_groups_url_to_welcome_email_tokens', 10, 2 );

And.. It’s working 🙌 See the screen capture below 😇


#8-0-0, #bp-email, #welcome

BuddyPress 8.0.0-beta2 is ready for your tests !

Here’s the announcement post about it we just published on BuddyPress.org:


#8-0-0, #beta, #release

BP Dev-Chat summary: May 12, 2021

8.0.0-beta1 feedbacks

@vapvarun checked our support forum and hasn’t found concerning feedbacks relative to this release.

@im4th replied to one of the comments that was posted on the announcement post about the next WordPress Full Site Editing (FSE) & Widgets Block Editor features. He tested the first one before our meeting and told us about his concerns during the chat. In short it’s a breaking change for the BuddyPress Theme Compat API. A pretty long discussion took place between @johnjamesjacoby @im4th and @vapvarun about it. We finally decided to open a very important ticket on our Trac to decide whether it’s on BuddyPress or FSE to adapt. If you have an opinion about it, please take a few minutes to share it with us.

8.0.0 tickets needing attention

  • About the bp_core_new_nav_default()function ticket (#8471), we decided we were too close to release date to do the necessary tests to be sure the patch doesn’t introduce some regression
  • About the BP Directory pages ticket (#8470), we think it’s best to split the ticket in 2 and deal with admin information on the Registration/Activation page during 8.0.0
  • @im4th wants to finish his audit regarding #8459 before packaging a new beta release.
  • @espellcaste reminded us about the GitHub Actions ticket (#8421). He agreed with @im4th about only committing the PHP Unit tests part.
  • We also punted the ticket about including PHPCS to our build tools (#7228) to leave us the time to discuss more about it as we don’t agree all about when to check WP PHP code standards (before committing or as soon as patching). The latter could possibly discourage people to submit patches in @im4th‘s opinion. Feel free to give us your opinion about it, commenting on the ticket.
  • Finally about the remaining release tasks (#8468). @vapvarun will take care of the changelog and @im4th will prepare the credits update.

8.0.0 updated schedule

We agreed to build a new beta release before our release candidate. @im4th will take care of it next week.

  • ✅ 8.0.0-beta1: April 29,
  • 8.0.0-beta2: ~ May 19,
  • 8.0.0 stable release: June 2.

Next Dev-Chat

It will happen on May 26 at 19:30 UTC and of course in #BuddyPress. If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

PS: we count on you to test the 8.0.0 beta release!

#8-0-0, #dev-chat, #summary