BP Dev Chat Agenda for March 25, 2020

Hi!

Next dev-chat is scheduled this Wednesday (March 25) at 19:00 UTC. As usual it will happen in #BuddyPress. We will discuss about :

  1. The BuddyPress 2020 survey,
  2. Progress about the 6.0.0 main features (we’ll be a few days away from first beta release 😱),
  3. Open floor.

Reminder, 6.0.0 schedule is:

  • First beta at the end of march.
  • Final release at the end of April.

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

#6-0-0

BP Dev Chat Summary: March 11th, 2020

BuddyPress Survey

We’ve been discussing about adding questions about 2 topics : BuddyPress integration with e-commerce plugins and BuddyPress alternatives. We found a compromise about the second topic and @mercime will add this question:

What other networking/membership plugin/software have you considered or used?

@espellcaste suggested to add a question about BP GraphQL consideration. @im4th suggested to add this feedback to the Google doc @mercime uses to work on the survey questions.

Progress about 6.0.0 release

@im4th asked about the BP REST API complete merge into BuddyPress core now all remaining endpoints are ready. @espellcaste prefers to keep maintaining it from its GitHub repository for now.

@im4th has decided to merge the BP Blocks plugin into BuddyPress core, following @johnjamesjacoby advice to reconsider his first idea about only merging “JavaScript built” blocks. A complete merge seems a better option to make sure to generate a pot file taking in account JavaScript translations. He recently added a patch on #8048 to make this happen, feedbacks welcome.

@dcavins was a bit worried he needed more than 2 weeks to end the Network invites work. If it’s the case, he will only include a portion of the code into 6.0.0.

Finally @im4th asked for help about #7729 @rayisme has been working on during. It’s about removing the legacy BuddyBar.

6.0.0 schedule & main features

  • Schedule:
    • First beta at the end of march.
    • Final release at the end of April.
  • Main Features:
    • BP REST API remaining endpoints ✅
    • BP Blocks ✅
    • Network invitation & Membership requests 😬
    • & maybe some surprises! 😬

Next dev chat

It will happen on March 25 at 19:00 UTC (a few days before first beta 🙄) 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!

#6-0-0

BP Dev Chat Agenda for March 11, 2020

Hi!

Next dev-chat is scheduled this Wednesday (March 11) at 19:00 UTC. As usual it will happen in #BuddyPress. We will discuss about :

  1. The BuddyPress 2020 survey,
  2. Progress about the 6.0.0 main features (we’ll be 2 weeks away from first beta release 😱),
  3. Open floor.

Reminder, 6.0.0 schedule is:

  • First beta at the end of march.
  • Final release at the end of April.

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

#6-0-0

BP Dev Chat Summary: February 26, 2020

6.0.0 Progress

@espellcaste shared about the work he’s been doing about improving the BP REST API (activity scope, member type, group type, friendship). The last issue we need to deal with is the Blogs Avatar endpoint (2 unit tests are failing mysteriously). @im4th will give it a second look before next dev-chat.

@dcavins & @im4th didn’t find the time to work on #8139 & #8048 😬

@im4th shared about his wish to solve two tickets (#8156 & #8172) asap to inform the BuddyPress contributors early about the introduced changes. They are now solved, so please make sure to have a look at these 2 posts:

BuddyPress Survey

Open floor

@im4th asked if anyone had an opportunity to look at GitHub actions to see if this was a way to ease the release packaging process. If a BuddyPress contributor could explore it, he’d be very happy 😍

@espellcaste asked about the status #5525 : the testing site is still open for review, but @im4th already found some issues about o2 as soon as it’s not used on the home page of the site. He will work on a fix about it.

@espellcaste shared his worries about the meta ticket related to the BP GraphQL handbook creation for the developer.buddypress.org site. @im4th is confident it will be fixed soon 🤗

6.0.0 schedule & main features

  • Schedule:
    • First beta at the end of march.
    • Final release at the end of April.
  • Main Features:
    • BP REST API remaining endpoints
    • BP Blocks ✅
    • Network invitation & Membership requests
    • & maybe some surprises!

Next dev chat

It will happen on March 11 at 19:00 UTC ( ~ 2 weeks before first beta 🙄) 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!

#6-0-0

The profile photo & cover image features belong to Members

Since the very first version of BuddyPress, the local avatar management feature was depending on the xProfile component. During the 2.1 development cycle we’ve renamed this feature “Profile Photo”. The cover image feature was introduced in BuddyPress 2.4 and, just like the Profile Photo feature one, it needed the xProfile component to be active to be able to enjoy it. In BuddyPress 6.0.0, we are introducing a major change about these 2 features: they will belong to the Members component.

This decision is the result of a Slack Discussion the team had about the subject just after we brought the first version of the BuddyPress REST API into BuddyPress Core. We’ve been working on it from this Trac ticket and yesterday the changes landed in Trunk.

What does it change for end users ?

When the xProfile component is active not much! They will only see that the settings to disable profile photo and cover image uploads are now available from a new Members settings section.

When the xProfile component is not active, BuddyPress used to fill the blank with a single member screen to show some information about the user’s WordPress profile (display name, website, biographical info and potentially some contact methods). As you can see below this lonely screen will have 2 new neighbours in BuddyPress 6.0.0*.

* If profile photo and cover image uploads are allowed by the site owner.

Logged in users will be able to edit/delete their profile photo and cover image from their self profile area, even if the xProfile component is not active.

Within the WordPress extended profile administration screen, Administrators will be able to edit the Profile Photo of the displayed user, even if the xProfile component is not active.

What does it change for BuddyPress plugin and theme developers?

If their WP_DEBUG constant is set to false, we believe nothing more than what we’ve described so far. Otherwise there are good chances their screens will be full of deprecation notices!! As a result we’re asking plugin and theme developers to start testing BuddyPress very early to make sure their master pieces will be ready before 6.0.0 release (scheduled for end of April). You can do it by cloning one of our Git mirrors or by checking out our SVN development repository:

# SVN
svn co https://buddypress.svn.wordpress.org/trunk/

# GIT
git clone git://buddypress.git.wordpress.org/

# OR
git clone https://github.com/buddypress/buddypress.git

To help you, here are the deprecated functions and hooks in 6.0.0 about the profile photo and cover image features.

Deprecated in 6.0.0Replacement in 6.0.0Type
xprofile_avatar_upload_dir()bp_members_avatar_upload_dir()Function
xprofile_action_delete_avatar()bp_members_action_delete_avatar()Function
bp_before_xprofile_cover_image_settings_parse_argsbp_before_members_cover_image_settings_parse_argsFilter
bp_after_xprofile_cover_image_settings_parse_argsbp_after_members_cover_image_settings_parse_argsFilter
xprofile_cover_image_uploadedmembers_cover_image_deletedAction
xprofile_cover_image_deletedmembers_cover_image_deletedAction
xprofile_avatar_uploadedbp_members_avatar_uploadedAction
xprofile_template_change_avatarbp_members_template_change_avatarFilter
xprofile_screen_change_avatar()bp_members_screen_change_avatar()Function
xprofile_screen_change_cover_imagebp_members_screen_change_cover_imageAction
xprofile_screen_change_cover_image()bp_members_screen_change_cover_image()Function

Let’s use the time we have left before the 6.0.0 release to make sure we haven’t forgot anything: please test your plugins and themes against Trunk, update them as needed and let us know asap if you need more help / BP Core code changes to take these evolutions in account.

BuddyPress Contributors, let’s update the Codex!

We still need to update our documentation about these changes. Here are the first Codex pages needing updates I’ve identified:

Thanks in advance for your help in making this change as smooth as possible for our end users 😍.

#6-0-0

BuddyPress 6.0.0 will require at least PHP 5.6

Hi everyone,

Please note we’ve just raised our PHP minimal required version to 5.6. Of course, we are supporting PHP versions up to WordPress requirements.

According to these stats PHP 5.3 is now used by less than 3 % of WordPress installs.

👋

#6-0-0

BP Dev Chat Agenda for February 26, 2020

Hi!

Next dev-chat is scheduled to tomorrow: February 26 at 19:00 UTC. As usual it will happen in #BuddyPress. We will discuss about :

  1. The BuddyPress 2020 survey,
  2. Progress about the 6.0.0 main features,
  3. Open floor.

Reminder, 6.0.0 schedule is:

  • First beta at the end of march.
  • Final release at the end of April.

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

#6-0-0