The main goal of this release candidate is to beta test improvements brought to the BP Nouveauโs compatibility with the WordPress 5.6 new default theme โTwenty Twenty-Oneโ (see #8395). @im4th insisted on the fact it was important to make sure text was readable in both modes : dark and light and as the 7.0.0 final release will happen one or two days after WordPress 5.6, itโs important BuddyPress looks nice in Twenty Twenty-One. The initial patch attached to the ticket is using the companion stylesheet feature so that styles are only loaded for this theme or this themeโs child themes.
@vapvarun said he would test the patch asap and that he would probably improve it. Thatโs what he did a few days after the development meeting.
We still need to finish the announcement post of the release, so we couldnโt have it packaged to the scheduled date ๐. As soon as it is ready, we will package it. Thanks in advance for your comprehension.
Open floor
Topics weโve been talking about:
How to find ways to get more contributors to beta test BuddyPress? @vapvarun suggested:
Write a todo list about tasks to achieve for next release (8.0)
Improve documentation about BP support for themes
Make template customization easier for users (WP FSE?)
Possible 8.0 early tasks: #7162 & working on giving more control to the user about the registration form (allowing users to select what xProfile fields to use in this form).
What about having a new BP Standalone theme? @johnjamesjacoby shared his wishes about it:
a 3 columns bp-default looking โchat appโ theme.
Itโs time to take advantage of all the work thatโs gone into BuddyPress since the beginning, and use that to rethink what a โbp-defaultโ looking theme would be today.
It should be responsive and use the BP REST API.
What about having a BP Specific area into WP Admin to manage every feature?
Next Dev-Chat
It will happen onย December 16 at 19:00 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!
BuddyPress 6.4.0 has been released yesterday, as weโve been discussing during the development meeting, it includes fixes to PHP 8.0 deprecated notices for BP Core & BP REST. It also includes a security fix. Read more about this release.
@vapvarun has been working on the release note, the remaining things to write is the changelog. @johnjamesjacoby removed the link to the BP Survey on our official site, @im4th needs to write a post about the results and publish it on BuddyPress.org asap.
7.0.0 first release candidate
Weโve spent the rest of the meeting working on getting the 7.0.0-RC1release ready:
@dcavins reviewed the Hello Screen texts ๐ (#8376).
@im4th worked on improving the Activity Embed block instructions (#8397) as only public activities can be embed into a post or a page.
Finally we decided to include the feature to list the displayed Memberโs Member Types into their profile header (#8394) as the poll @im4th made on Twitter got 83% votes for ๐.
7.0.0-RC1 has been released 2 days late (November 20) according to the initial schedule. Itโs an important step, BuddyPress plugin/theme authors should really test their piece of work against it so that our users can fully enjoy 7.0.0. If you find a bug, please open a ticket to report it on our Trac environment or use this support topic.
RC1 also marks theย string freezeย point of the 7.0.0 release schedule. So we will not add/edit or delete i18n strings until 7.0.0 is released. Just like what we did for 6.0.0, we will credit people who contributed to translating BuddyPress into as many languages as possible. Donโt hesitate to join the effort!
Hereโs 7.0.0 (development column on GlotPress) translation tops so far:
It will happen onย December 4 at 19:00 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!
First of all, the Developer documentation has been updated according to the latest improvements weโve brought to the BuddyPress REST API!
Members Endpoints
Whatโs the friendship status of the logged in user with other(s)?
If the Friends component is active and youโre wondering whatโs the answer to this question, then you can get a clue thanks to a new property weโve added to the Members item schema: friendship_status_slug.
As you can see in the above browserโs inspector, the logged in user is :
not friend with admin (friendship_status_slug: 'not_friends'),
has requested a friendship request to Mercime that is still pending her approval (friendship_status_slug: 'pending'),
has received a friendship request from John that is awaiting his response (friendship_status_slug: 'awaiting_response'),
friend with Boone (friendship_status_slug: 'is_friend').
When was a user last active, what is his/her latest update and how many friends do he/she has ?
Thereโs now a new request argument you can use to know these information : populate_extras. You simply need to set it to true to do so. The response will include these extra properties:
The last_activity object which contains 2 properties:ย
date: the date the user was last active,
timediff: a human diff string, eg: โ20 minutes agoโ.
The latest_update object which contains 3 properties:
id: the ID of the activity,
raw: the content of the activity as it exists into the database.
rendered: the content of the activity ready for output.
The total_friend_count variable which contains the number of friends of the user (integer)
Hereโs an example of use of this new request argument:
When was the last time a group was active & how many users are members of this group ?
Juste like for the Members Endpoints (GET Members & GET Member), thereโs now a new request argument you can use to know these information : populate_extras. You simply need to set it to true to do so. The response will include these extra properties:
total_member_count: the count of all Group members,
last_activity: the date the Group was last active,
last_activity_diff: the human diff time the Group was last active.
Is it possible to append one or more Group Types to the Group Type(s) the group is assigned to ? What about removing one or more specific Group Types from the ones the group is assigned to ?
The PUT verb of the Groups/:group_id endpoint now supports 2 new request arguments to achieve this:
append_types : a string containing the Group Type name to append to existing groupโs Group Types. To append more than one Group Type, use a comma separated list of Group Type names.
remove_types : a string containing the Group Type name to remove to existing groupโs Group Types. To remove more than one Group Type, use a comma separated list of Group Type names.
Hereโs an exemple of appending Group Types to the one that is already assigned to the group:
Is it possible to filter the list of activities on more than one action/type?
Yes, to filter the fetched activities (GET Activities) on one action/type, you need to set the type collection parameter to an array containing the corresponding action/type. For more than one action/type, include all the needed actions/types into the array used as the type collection parameter.
Do we still need to set the component request argument to groups when fetching group activities about a specified group_id request argument?
No! From now on the group_id is enough, of course you can still alternatively use a request (GET Activities) having the primary_id argument set to the ID of the group and the component argument set to groups.
Hereโs an example about how you can use this request argument:
And last but not least, weโve added a new route to let users create a blog (POST Blog) when the Network option is allowing it, read more about it from our freshly updated Developers documentation.
PS: if you want to get all examples at once, hereโs a Gist.