Hi!
Our next development meeting will happen on May 1st at 21:00 UTC (tomorrow) in #BuddyPress. Here’s our agenda:
If you have specific/additional points you need to discuss about, please share them into the comments area of this post.
👩🏽💻👨💻🧑🏻💻🤝
We mainly discussed about this ticket #8821. In short, if a string containing placeholders has not been updated by a translator of the Polyglots team, it can result in a fatal error when using the sprintf() function. @dcavins and I think it’s a WordPress issue, but WordPress core team don’t, see #55776. As it was too heavy to address this issue in a maintenance release, we’ve decided to use a workaround for 11.1.0 trying to alert translation contributors they need to remove one of the placeholders for specific strings using gettext comments. We’ll try to find a nicer way to avoid these kind of fatals during the 12.0 development cycle, see #8836.
11.1.0 was released on February 16. Many thanks to contributors who shared their time with us to make it happen.
@im4th believes most of the work will consist in documenting the changes about the way to extend BuddyPress. A place of choice for this documentation is the developer.buddypress.org site.
@dcavins thinks so too and started talking about the Code Reference part of this website. We haven’t progressed much into this area & @im4th thinks we do need to use composer on the server to benefit from the WP Parser tool. Tests he made about WP export/import tool wasn’t conclusive due to missing relationships between post types. It doesn’t mean we’re giving up, it simply needs some available time.
@im4th’s idea is to create first chapters of a BP Plugin Handbook as it’s very easy to do so on the current developer documentation site. We’ll try this way once most of the BP Rewrites API will have been merged into Core.
About this subject, progress can be followed from this ticket #4954. @im4th will make small steps using pull requests. Once the function to build links using BP Rewrites is available in Core, @dcavins will be able to give him a hand on reviewing all existing BP links so that they are built using this new function.
@dcavins will take in charge #8794 💪
@dcavins tested the plugin and found some issues. The biggest one was with regular WordPress themes. As @im4th only tested it with Block themes he hadn’t figured it out so far.
@dcavins & @im4th then discussed about how site owners need to set the private uploads directory. @im4th is convinced the best way to do it is to put it one level upper the site’s directory: a bit like what you can do to secure your wp-config.php file. Doing so requires a bit more work to make sure the directory is writable for the server’s user, but this feedback from a betatester is very interesting as it seems not too difficult to understand thanks to the admin notices in place.
As @dcavins noted, we’ll need to document the private uploads directory creation process.
It will happen on February 27 at 21:00 UTC in #BuddyPress. If you have specific points or ideas you want to discuss about, don’t hesitate to share them in comments.
Hi!
Our next development meeting will happen on February 13 at 21:00 UTC (Monday) in #BuddyPress. Here’s our agenda:
If you have specific/additional points you need to discuss about, please share them into the comments area of this post.
💕 👬👭👫
Hi!
Our next development meeting will happen on January 18 at 19:30 UTC (today) and of course in #BuddyPress. Here’s our agenda:
If you have specific/additional points you need to discuss about, please share them into the comments area of this post.
📯
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.
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:
page and per_page ;bp_core_get_incremented_cache – The same approach used in the Activity component;That’s the question we took a few minutes to try to reply to.
We’ve also discussed about:
@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!
It will happen on January 18 at 19:30 UTC in #BuddyPress. If you have specific points or ideas you want to discuss about, don’t hesitate to share them in comments.
Thanks for welcoming “La Scala” into your WordPress sites: please upgrade!
🙌 🍕
Hi!
Our next development meeting will happen on January 4 at 19:30 UTC (tomorrow) and of course in #BuddyPress. Here’s our agenda for this 1st meeting of the year:
If you have specific/additional points you need to discuss about, please share them into the comments area of this post.
🥂🍀🔮
Thanks in advance for your help 😍
👋
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.
It will happen on December 21 at 19:30 UTC in #BuddyPress. If you have specific points or ideas you want to discuss about, don’t hesitate to share them in comments.
BP Dev Updates 