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 🙌
@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.
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!
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.
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 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: