Letās all joinĀ the firstĀ #BuddyPressĀ developer meetingĀ of the year.Ā It is scheduled onĀ January 6 at 19:00 UTCĀ (tomorrow), hereās the agenda:
BuddyPress 8.0.0ās kick off
Features / bug fixes wishlist, please reply to the 8.0.0 call for tickets if you havenāt already!
2 bugs related to the 7.0.0 release were posted on Trac:
#8411 The Groups Administration screen was not reachable anymore for configs using the multiblog constant BP_ENABLE_MULTIBLOG. ā It has been fixed.
#8414 Using the BP Blogs component tool to repair site icon / blavatar synchronization on non multisite configs was generating an error due to a WordPress function not available. ā It has been fixed.
We also spent some time investigating a possible bug about Activity recorded dates but it turned out it wasnāt involving the plugin. Weāve decided to package a minor release (7.1.0) before christmas. It should be available for download later today (around 21:00 UTC).
The 7.0.0 release had the best download spike of our 2020 releases. It was reached on December 11 with 34326 downloads š
About the 8.0.0 features wishlist!
Weāll post a new call for tickets at the very beggining of 2021, the same way we did it for the 7.0.0 release. Everyone will be welcome to contribute to it. You can start looking for Trac tickets youād like to see fixed for 8.0.0.
@slaffik will personally take a look at good-first-issue tasks, on those that he has created a while ago, and will open a new ticket to work on bringing Twenty Twenty One compatibility improvements to our default Template Pack š.
Finally and more globally about development cycles, weāll have a discussion about how we can improve things such has release regularity, release leading, etc.
Next Dev-Chat
It will happen next year onĀ January 6 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!
Many thanks to all BuddyPress contributors for their help during 2020, we wish you all great holidays and to stay safe. See you in 2021 for some great BuddyPress times!
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.