Hi!
Our next development meeting will happen on March 27 at 21:00 UTC (today) 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.
⚙️🔭
BuddyPress is 15 today 🎂🎊 To celebrate this specific day, here’s our gift 🎁 to the community:
Hi!
Our next development meeting will happen on March 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.
⚙️🔭
#4954 3 changes were committed so far. The third one introduced an important function that will be used to build all BuddyPress links bp_rewrites_get_url(). We now need to replace all existing links so that they use this function.
We also talked about moving the BP Default theme into the BP Classic back compatibily plugin we’ll package for plugins not yet ready for BP Rewrites.
@im4th fixed all issues and improvements @dcavins identified during his beta-tests. We decided to request a repository to the WordPress.org plugins directory on early March.
@dcavins will run some more testing of the Add-on and share new feedbacks about it. Here’s a preview of a Media attached to an activity into the BuddyX theme.
It will happen on March 13 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 27 at 21:00 UTC (today) 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.
Here comes 11.1.0, this is a maintenance release, please upgrade!
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 !
Please note that BuddyPress 12.0.0 will require WordPress >= 5.8.
To learn more about this change: https://buddypress.trac.wordpress.org/ticket/8822
To learn more about how we decide to bump our WordPress required version: https://codex.buddypress.org/getting-started/wordpress-version-compatibility/
@espellcaste and I thought it was important to talk about the pull request he suggested about changing action callbacks returned value (from boolean to no returned value) See #GH55. During the discussion we had with @dcavins, we came to this conclusion as the change is a possible breaking one & targeted callbacks are in a bp-component-functions.php file we are not discouraging third party plugin authors from using them, these functions shouldn’t have their signature changed. Instead we should use hooks the right way inside a bp-component-hooks.php file.
We’ve decided the main focus of this release will be to merge BP Rewrites into Core (see #4954) and create a new plugin to provide backward compatibility users will be able to use in case one of their third party plugin is not compatible with BuddyPress Rewrites. We’ll also raise WordPress required version to above 5.8 and move legacy widgets into this plugin. We agreed a nice name for this plugin would be BP Classic!
Here’s 12.0.0 initial schedule
@im4th plans to package a first beta version to submit it to the WordPress.org Plugin directory. @dcavins will use the next 2 weeks to test it as @im4th ask him to do so to feel more secure about it. To see the list of available features, you can have a look at the add-on’s GH readme.
It will happen on February 13 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.
BP Dev Updates 