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?
@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.
@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
First beta at the end of march.
Final release at the end of April.
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!
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 co https://buddypress.svn.wordpress.org/trunk/
git clone git://buddypress.git.wordpress.org/
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.
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:
@mercime shared her progress about her first pass on the BuddyPress survey for 2020 (see #8153). She prepared 16 questions.
We’ll use CrowdSignal to publish the survey.
On a side note @johnjamesjacoby suggested BuddyPress could have a lightweight Questionnaire component, @im4th believes it’s a great idea !
@mercime shared with all of us the questions she worked on after the dev-chat. Please take some time to review it before our next dev-chat
BuddyPress dev-chat are maintained on every other wednesday at 1900 UTC.
Unfortunately @espellcaste can’t join us on all the alternative days of week we’ve found into the doodle 😦 As the result it doesn’t worth changing our dev-chat meeting day/time.
@dcavins is making good progress about Network invites (#8139). He’s getting some inspiration from the Invite Anyone plugin. @im4th asked if it would be possible to invite a user not yet registered to the site to join it using a group invite, and the reply is yes 🙌
@im4th confirmed BuddyPress 6.0.0 will ship 2 Blocks and shared his progress about the Group Block. Here are 3 early screenshots of how it could look like :
BP REST API (improvements and remaining endpoints)
@espellcaste has been working on fixing some issues posted on the GH repository. With @im4th they discussed quite a time about one specific issue that is now resolved (many thanks to @espellcaste for his work on it 💪). About the tasks scheduled for 6.0.0, you can take a look at this GH project. Here are the remaining endpoints:
Member’s cover endpoint
Group’s cover endpoint
Blog’s cover endpoint
Blog’s avatar endpoint
FYI this Core ticket should also be fixed for 6.0.0: #8156 (Move Avatar into the Members component).
@karmatosed has shared sketches and thoughts about the first 2 BuddyPress blocks we will add in 6.0.0:
@im4th will start working asap on the first implementations of these 2 blocks building an autocomplete control to select the member or the group to display. @dcavins suggested this could be a good opportunity to review our Suggestion API so that it uses the BP REST API.
Network invitations & Membership requests.
@dcavins will work to make it happen in 6.0.0, you can still add your feedbacks on this ticket #8139.
@mercime & @im4th will also try to work on some surprises for this next release. We are keeping the features secret for now 😂
@im4th also shared his wish to use WordPress Rewrites instead of our legacy way of building URLs, see #4954. A possible way of progressing about it could be to use a plugin… He will look into it to see if it needs some Core adjustments.
Discussing about the previous points took us a while and we decided to talk about the survey during our next dev-chat.
@espellcaste cannot attend our dev-chats at the date/time they are scheduled. I’ve published this doodle to let us try to find a new day / time of the week for our meetings. I’ve left the current day / time: choose it if you prefer to leave the day / time unchanged.