Some complementary explanations about the 9.2.0 release
@im4th started the meeting saying some words about this minor version which was released on January 3rd. The download spike (~39K downloads) was reached on January 4th. He apologized about the fact he took the decision quite in a rush without discussing about it during a dev-chat. He explained he wanted to have the BP Search Block released in the WordPress.org directory the soonest so that he could focus on the BP Rewrites feature as a plugin for the coming 15 days. 9.2.0 is including a change needed by the BP Search Block (activity search redirection support).
About BP Rewrites, @johnjamesjacoby wants to dive deeper into the plugin. @im4th said it was ok to delay its release after BuddyPress 10.0.0, if needed, as it’s a BP plugin. He also shared his opinion about a BP Core potential merge.
I believe it needs to stay an add-on for at least 2 major BuddyPress releases, there are too many plugins we need to make sure they still behave right before thinking about merging it into BP Core.
Finishing the 10.0.0 Hello BuddyPress screen
If you’ve started testing the RC1 release (if not, do it now!), you already saw it has been finished (See #8605). During the chat, we’ve decided about the 10.0.0 features we want to highlight into this screen:
The fact we’ve made sure to be compatible with Twenty Twenty-Two (and full site editing more globally)
Inside the “under the hood section”: the performance improvements brought by @oztaser (#8296, #8591 & #8426), the Avatar Recycle view as well as BP Signups improvements (#8540).
We also decided to release RC1 as soon as we could (it happened 2 days later) as we already postponed twice our schedule.
Last 10.0.0 schedule
10.0.0-RC: January 7, 2022 🏁 ✅
10.0.0 stable: January 17, 2022 🎯
@dcavins has been using the 10.0.0-beta2 release on some decent traffic sites and it seems to be working well 💪 😎
In case you missed it 10.0.0-beta2 was released on December 23. We decided to package this new beta version because @dcavins found a regression about the way custom Group extensions were registered. In short: in case there were more than one Group extension into the loading queue, only the last one were actually registered. @dcavins did a great job identifying the issue, finding the root cause and fixing it. For more information: #8558.
If, as a Plugin author, you are using the Group Extension API, we strongly recommend you to test 10.0.0-beta2.
Other 10.0.0 tickets
@vapvarun added a patch about #7540. @im4th reviewed it before committing it the day after the dev-chat. Members can now exit from a multi recipients Private Message thread.
During the chat @im4th said #8474 would stay opened until WordPress 5.9 is released. We’re finding small issues with Full Site Editing the more we test BuddyPress with it. If you’re contributing to WordPress 5.9 beta tests, make sure to test BuddyPress with Twenty Twenty-Two: we need your contributions!
About #8604@vapvarun suggested to wait for the first feedbacks about the « richer » logging activities before eventually adapting them according to the context they’re displayed in.
10.0.0 stable release tasks repartition
We need the Hello BuddyPress screen updates to be accomplished before 10.0.0-RC is published. @dcavins already prepared the credit updates, he will write a few lines about Site Membership requests. @vapvarun will also write some lines about logging activities. See #8605.
New 10.0.0 schedule
We’ve postponed the stable release date by 10 days to leave enough time to polyglots contributors to update BuddyPress translations.
10.0.0-RC: January 3rd, 2022 👈
10.0.0 stable: January 15, 2022 🎯
@dcavins & @vapvarun suggested we work on documentation updates for the time of a major release development cycle so that our codex can get some ❤️. Today, a lot of screenshots are outdated and latest improvements about BuddyPress are not necessarily explained there. We decided to give this huge task a 4 to 6 months time frame and why not try to gather some contributors into a BuddyPress documentation team. If you’re interested in being part of such a team: let us know!!!
@dcavins fixed the multisite issues about the feature, @im4th confirmed the fixes made the feature works as expected on the WordPress multisite config. @dcavins decided to add complementary explanations about how the feature deals with multisite registration options. He committed the code yesterday and BuddyPress 10.0.0 is now offering a Site Membership Request feature 🙌. Congratulations to @dcavins 💪.
#8451 Extending no content activities with images and call of actions
@vapvarun brought some nice improvements about how we load activity types template part and also added some new layouts for “no-content” activities. @im4th still had to finish the Avatar Recycle UI so that users can reuse a previously uploaded avatar or permanently delete a previously uploaded avatar.
#8148 Extend WordPress Plugins screen to allow Admins to easily install features as a plugin
@johnjamesjacoby added the BP Beta Tester plugin to the BuddyPress WP.org user favorites so that we have a first BuddyPress Add-on into the new WP Admin “Add New” plugin screen. The ticket is now closed and we’ll soon be able to publish new add-ons like the BP Rewrites plugin to the WordPress.org Plugin directory. Here’s a preview of this new screen:
Other tickets needing attention
@vapvarun will have a look to #7540 to try to have it fixed before the 10.0.0 stable release.
We’re adding the very final touches to the first 10.0.0 beta release… get ready for it!
@im4th tested the patch @dcavins updated lately and found some issues when BuddyPress is network activated on a WordPress Multisite configuration. In such a configuration, the site membership request feature is only available when the WordPress registration setting is “Logged in users may register new sites” (1) or “Registration is disabled” (2).
In the first case (1), the request membership form includes a checkbox to request a site at the same time, and once the form is submitted the user receives an email to activate their account instead of the awaiting moderation email.
In the second case (2), once the request membership form is submitted, an empty registration page is displayed and the site membership request is not created.
@dcavins is working on fixes about these two issues to have the feature ready for the BuddyPress 10.0.0-beta1 release.
#8451 Extending no content activities with images and call of actions
Great progress were made about this feature:
The BP Attachments API will include a new method to add file revisions. This is needed by the feature to keep an history of the uploaded profile photos so that generated activities always display the profile photo that was set when the activity was published.
The BP Template hierarchy will be improved so that it’s possible to override the layout of the activity content based on its activity type.
@im4th will try to add the needed adaptations to the Avatar Backbone views so that they includes a new tab to recycle or delete previously uploaded profile photos from history.
@vapvarun will work on the generated activity layouts to differentiate them according to the (no-content) activity types.
Other tickets/GitHub PR needing attention
@espellcaste couldn’t stay long during the chat but reminded us about the BP REST plugin Pull Requests needing a review.
to ease BP Rewrites testing @im4th wants to tackle #8148 during the 10.0.0 development cycle.
A first step has been made about making BuddyPress more friendly with themes supporting the WordPress Full Site Editing feature, see this commit message for a detailed explanation. You’ll find below a screenshot of the Activity directory displayed into the next WordPress 5.9 default theme: Twenty Twenty-Two.
Updated 10.0.0 schedule
We’ve updated the 10.0.0 schedule for the last time 😅. @dcavins alerted us about the comments on the Tavern’s post about our initial released date which was December 24, 2021. To avoid causing some stress to site administrators (and to the team ☺) during the christmas period, we’ve decided to postpone the release date to January 5, 2022. We also took this opportunity to give us one last week to add the final touches to the first 10.0.0 beta release.
The first thing we’ve discussed about was the scheduled date for the first beta release of BuddyPress 10.0.0. @im4th shared his concern about the fact he would not be able to test/review the latest improvements brought to the site request membership feature #8582 by @dcavins as well as the “no-content” activities patch @vapvarun was about to add to the ticket (#8451) before November 20 (beta1 initial scheduled date). He requested to use 2 more weeks before releasing beta1. Although @vapvarun was in favor of only adding 1 week, @im4th argued he was prefering to delay by 2 weeks once instead of by 1 week twice. @dcavins also thinks a 2 weeks delay is good and should help us to fix some other tickets.
New 10.0.0 schedule
10.0.0-beta 1: ~ december 3, 2021 👈
10.0.0 stable: ~ december 24, 2021 🎄
Updates about featured tickets
#8451 Extending no content activities with images and call to actions: @vapvarun announced he was about to submit a first patch about the feature.
#8582 Add site membership requests: we think we should use a new action link instead of links into a new WP List Table column to open the modal. @im4th will try to build an inline-edit feature using the BP REST API and we’ll be able to replace the modal link with the inline-edit one if it’s ready before first beta. @dcavins will also try to avoid adding an upgrade routine to edit the existing $wpdb->base_prefix . 'signups' table rows and use instead a new meta to differentiate site membership requests from signups. The last touch about the feature will be to update the list of BP Emails so that it includes the ones needed by the feature.
#8594 Legacy Widgets: next step before deprecation: @vapvarun shared his concern about it considering the number of downloads of the Classic Widget editor plugin. After checking the ticket’s patch and the plugin’s code, @im4th reassured @vapvarun telling him the legacy widgets would still be available for people using this plugin. He’ll do some more tests to be 100% sure about it.
@im4th thinks we shouldn’t include more BP Blocks into BP Core and that we should start using standalone blocks and publish them into the WordPress.org Blocks directory (which is actually using the plugins directory). @dcavins thinks it’s an interesting idea. @vapvarun is not convinced (yet 😁) about it especially when considering these blocks are increasing the number of active plugins on sites. He thinks a Blocks collection plugin would be better. If you have an opinion about it, we’d be happy to read it as a comment of this post 😉.
@dcavins updated the patch attached to the ticket to remove all references to data stored inside the Users table. He also added a way to preview all signup/membership request information using a modal window.
The modal window choice was debated with @im4th & @johnjamesjacoby. First concern is a11y: we need to check keyboard navigation to make sure everything’s fine with it. Second concern is the clumsiness of it into the WP Administration (old JS libraries, Ajax, etc..). @dcavins thought about an alternative way to reach the same result (be able to preview information) using a dynamic row like what’s included into the « inline edit » feature of the WP List Table class. @im4th believes it’s a nice idea and could be even more interesting if information could be edited from there. We might need to customize the feature for our need which can be too long for the remaining time we have until first 10.0.0 beta. @dcavins will give the modal window another thoughts before deciding whether to keep it or not.
Please help us progress about the site membership requests feature testing the last patch attached to this ticket: #8582.
#8588 use the “site-health” look & feel for BP Admin tabs
@im4th asked for some feedbacks about it. @dcavins thinks it should be committed. @espellcaste thinks this is the kind of change regular BP users will enjoy. @im4th also shared a preview of the new BP Rewrites admin screen using these revamped Admin tabs. This improvement has since been committed, a developer note will soon be published to explain the changes introduced about adding custom tabs in 10.0.0.
Other interesting updates
#8597: @espellcaste just added a patch about allowing Messages/Recipients pagination in the box template.
WP Graphql BuddyPress #88: @espellcaste opened a PR to add support to the Messages component.
10.0.0-beta 1: ~ november 20, 2021,
10.0.0 stable: ~ december 24, 2021 🎄
It will happen on November 17 at 19:30 UTC in #BuddyPress. We’ll be 3 days away from first beta release 😅. If you have specific points you want to discuss about during this next meeting, please share them into the comments area of this post.
During this development meeting we talked about two specific tickets:
#8451 Extending no content activities with images and call to actions
First @vapvarun opened a discussion about the best way to store member/group profile photos &/or profile cover images when making the generated activities about it richer (eg: Admin changed their profile picture). As BuddyPress only keeps the « latest version » of these images, we identified these options:
Use base64 encoded images into the content of the activity: it seems more engaging for the community as we keep a real story about these changes. But it may be problematic for large images + what happens if a user edits many times in a row his profile/cover image?
Do nothing, the older activities would show the latest profile/cover image. It’s less engaging, we rewrite the past in a way… But it’s a lot more easier 😅
Delete the older activities to only keep the latest one to be consistent with the profile/cover image.
If you have an opinion/ideas about it, feel free to share it as a comment to this post or the ticket: #8451.
@im4th shared his concern about how the feature should behave on Multisite configs. We discussed about how WordPress deals with the registration option in this case and their meaning: accounts can be created (1), accounts & sites can be created (2), existing users can create sites (3) and registration is disabled (4). @dcavins and actually us 3 agreed on the fact the site membership requests feature should only be available for cases (3) & (4).
We also talked about the non-Multisite configs registration process which can be misleading in WordPress as accounts are actually created into the Users table. For this feature we need to forget about the fact these data are available as they are not in Multisite and advanced users can use a specific constant to skip the WordPress account creation.
Please help us progress about the site membership requests feature sharing your thoughts or testing the patch attached to this ticket: #8582.
Many thanks to the contributors who commented our last dev chat summary about whether or not we should raise the BuddyPress required WordPress version to 5.4. During this dev-chat, we’ve taken in account your feedbacks, kept on discussing a bit about the subject, and we’ve decided 10.0.0 will require WordPress 5.4. Yesterday @im4th suggested a first patch about it and we’ll keep you informed when it will be converted into trunk. Don’t hesitate to contribute to it from this ticket #8571. We’ve also decided to include WP 5.4 to the GH action that runs PHPUnit tests after each commit to our development version. So far, we were only testing the latest WordPress stable version and the development one, fearing about exceeding our GH Actions quotas 😱.
@vapvarun is progressing on Legacy Widgets for community stats (before doing the Widget Block jump!) and impressed us with rich content activities for « poor » activities like « a member changed their profile photo ». He opened a ticket about it: see #8451. We believe these could be a nice enhancement to the activity streams.
@espellcaste is working on patches to improve our inline documentation 💪 : see #8553.
@im4th has been working on the BP Attachments feature as a plugin lately and hopes he’ll be able to have a first beta ready before the end of BuddyPress 10.0.0 development cycle.
@dcavins made progress about the Site Membership request feature and a first patch is available on this ticket: #8582. Feedbacks are very welcome.
We’ve also discussed about refreshing our BP Admin tabbed screens to use the look & feel of the Site-Health & Privacy settings screens. A first patch is waiting for your feedbacks there: #8588.
10.0.0-beta 1: ~ november 20, 2021,
10.0.0 stable: ~ december 24, 2021 🎄
@im4th asked the team to keep an eye on TwentyTwentyTwo new WordPress default theme and to the progress of the full site editing feature in WordPress 5.9-alpha/Gutenberg plugin. He reminded us about potential difficulties to have BuddyPress behaving the best way with Themes using this Full Site Editing feature. See #8474.
October 20 Dev-Chat Agenda
It will happen today, in a few hours in #BuddyPress. We’ll share our progress about the 10.0.0 release.
We started by congratulating @oztaser for the great contribution he brought about SQL performance improvements to the BP Notifications API (See #8426).
@dcavins will actively (👈 adding some pressure here 😁) progress about the site membership requests feature. He will also take in charge the issue about the inconsistent behavior of Groups Invites when the friends component is not active inside the Legacy template pack (see #8550)
@vapvarun is exploring BuddyPress statistic widgets from a plugin, @im4th challenged him to build Widget Blocks about it in 10.0.0 as well as exploring the mutual friends/mutual groups which are other Widget Block nice candidates (see #8559).
Then we had a long discussion about raising the BuddyPress required WordPress version to 5.4 (see #8571). It’s true it’s quite a jump from 4.9 but “Tipton” was released almost 4 years ago, it’s the last WP version before the Block Editor which is probably making it a bit special. WP 5.0 to 5.3 are under 5% of total WordPress installs which makes 5.4 a good candidate for our next required version.
If a WordPress version became obsolete over a year ago, it’s a candidate for removal. If a WordPress version’s use slips below 5% of all WP installations, it’s a strong candidate for removal.
@sbrajesh shared his first thoughts after testing the plugin. He was a bit surprised not to find the BP Directories into the WordPress pages. In BP Rewrites, BP Directories are using a Custom Post Type without using the corresponding WordPress generated UI. Instead there’s a new URL settings page to customize almost every possible slugs. The last improvement to add about slugs is to support customizable slugs for the Member’s secondary navigation. It’s true the UI used for this settings page should be improved (a lot!).
@im4th informed about the plan for this plugin : it’s not to merge it into BP Core during 10.0.0 (or even 11.0.0) but to release it as a plugin so that a lot more people can easily test it. There’s a ticket about easing hosted on WP.org features as a plugin installation from one of the BuddyPress Admin screens to also simplify this part for users (see #8148). Switching from our Legacy URL Parser to the WP Rewrite API will need a lot more testing to make sure BP plugins and themes are behaving almost like there was no switch!
@im4th strongly encourages all BP Plugin/theme developers to give a test to this feature as a plugin to contribute to the next way BuddyPress will parse URLs.
@im4th@dcavins & @vapvarun are going to participate to a Q&A hosted by Birgit Pauli-Haack from the Gutenberg Times on October 28 at 16:00 UTC. If you want to know more about our experience migrating the BP Legacy widgets to Block Widgets during the BuddyPress 9.0.0 “express” release, please join us! More info available there inside the Upcoming Live Q&As section.
It will happen on October 6 at 19:30 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!