Before releasing 11.0.0 on January 5, we had another look to #8783. This is still a mysterious issue we haven’t manage to reproduce yet (Displaying The Opt-outs Administration page is not generating an error for us on multisite). We also decided @im4th would package the release & draft the announcement post & @dcavins would take care of the release changelog.
Focus on the BP Messages component
Specific needs about this component BP REST API endpoint were brought to @espellcaste‘s attention (see #8696). It made him think about this component more broadly. So far BP Messages is fetching all messages belonging to a thread and he thinks we can improve this behavior and performance using pagination. He shared the roadmap we all agreed on about it:
Remove the default behavior of loading all messages;
Set reasonable default for page and per_page ;
Update the BP Theme to support pagination (currently, it loads all messages);
Cache with bp_core_get_incremented_cache – The same approach used in the Activity component;
Apply the same suggestions to the recipients’ query.
How do you see BuddyPress at the end of 2023?
That’s the question we took a few minutes to try to reply to.
@espellcaste‘s priority is mostly dev-focused: a developer reference site, BP GraphQL Extension, PHPCS/PHPDoc Improvements, VSCode BP Extension,
@dcavins would like to see a simple “private site” option land in BP, he believes another big possibility is to make core BP template pieces “insertable” using the WP Site Editor.
@im4th‘s predictions are: “To me, at the end of 2023, BuddyPress Activities will use the Blocks API, the Post Form will be a block based one and we’ll have a brand new Block Templates based theme”.
We’ve also discussed about:
the opportunity to move the Site Wide Notices feature outside of the BP Messages one,
splitting optional components into plugins,
the ActivityPub protocol to make BuddyPress a bridge between WordPress sites.
the need to organize all the feedbacks we got from last year to take wise decisions.
@espellcaste has a conflict of meeting, so he won’t be able to attend future meetings. @im4th & @dcavins are flexible about the meeting day and time (as long as it’s after 19:30 UTC for @im4th), let’s find asap a new day to “biweekly” meet!
Thanks in advance for beta testing this pre-release version. If you’re using the BP Default theme, we’d be even more thankful if you could give us some of your time to make sure everything is fine for you with this third beta release.
That’s the important decision we made during our meeting a few minutes ago. We prefer to delay 11.0.0 final release to early next year.
In 11.0.0 we’re making an important change about the way BuddyPress is loading deprecated code. Everything is fine with it when you use one of the BP bundled template packs (BP Nouveau or BP Legacy). Using a template pack to dynamically inject BuddyPress content into one of the templates of your active WordPress theme’s (most likely the page.php one) is the plugin’s default behavior since version 1.7. But we forgot there was still some BP Default old classic theme fans around 😱.
Since version 1.9, The BP Default theme is “hidden behind a filter” for new BuddyPress installs. In other words, you need to add some custom code to bring it back. That’s why we haven’t thought about it so far. Fortunately we were alerted into our Slack channel about issues when this theme was still used and active on the WordPress site (this can be the case if you regularly updated BuddyPress since version <= 1.8).
We’ve been working on it and we think we’ve fixed BP Default issues. Releasing a third beta version instead of directly making the release candidate available seems a wise move. Thanks in advance for your understanding.
Only one ticket was raised about our usage of an outdated version of moment.js (see #8766). We’ve fixed the ticket deprecating this outdated version and using the one already bundled into WordPress since its 5.0 version.
@espellcaste asked whether the ticket about $this usage into function doc-blocks (see #8611) were still in 11.0’s roadmap. It was as it’s now fixed 🤝.
@espellcaste also raised @im4th‘s attention about the fact it was not possible for a user to delete their own account using the BP REST API (see #8758). The ticket has since been fixed ✅.