BP Dev-Chat Agenda July 3, 2024

Hi!

Our next development meeting will happen on Wednesday July 3 at 19:00 UTC in #BuddyPress. Here’s our agenda:

  • 14.0.0 tickets to fix before RC release:
    • #9189 Bump bundled BP CLI to 3.1
    • #9188 Hello Screen updates for 14.0.0
    • #9196 Team roles update & formalize the fact @vapvarun & @emaralive are part of the BP Team.
    • #9204 start working on up/next right after current RC1.
  • Who’s volunteering to lead the 15.0.0 release?
  • RC1 release party! 🥁🎸🎤

PS: this chat will probably last longer than usual, thanks in advance for your understanding, we need to accelerate a bit to be ready to release 14.0.0 stable version on July 8.

If you have specific/additional points you need to discuss about, please share them into the comments area of this post.

#14-0-0, #agenda, #dev-chat

Notice of Deprecated Functions in 14.0.0


BuddyPress 14.0.0  has deprecated functions and constants that will no longer be supported. Furthermore, these functions and constants may be removed from future versions, therefore it is  recommended to update any code that uses them, appropriately.

FunctionStatusVersion
bp_block_init_editor_settings_filter()Deprecated14.0.0
bp_block_init_category_filter()Deprecated14.0.0
bp_use_wp_admin_bar()Deprecated14.0.0
bp_admin_email_add_codex_notice()Deprecated14.0.0
bp_activity_admin_screen_options( $value, $option, $new_value )Deprecated14.0.0
bp_groups_admin_screen_options( $value, $option, $new_value )Deprecated14.0.0

See src/bp-core/deprecated/14.0.php for further code details.

ConstantStatusVersion
BP_USE_WP_ADMIN_BARDeprecated14.0.0
BP_SIGNUPS_SKIP_USER_CREATIONDeprecated14.0.0

Additional Suggestions:

For non-developers, here are some tips for resolving deprecation notices in BuddyPress:

  • Update themes and plugins: This is the most common fix.
  • If the plugin or theme developer doesn’t have an update available, contact them directly. 

FYI: 14.0.0 schedule

  • June 13: 14.0.0-beta1 ✅.
  • June 24: 14.0.0-beta2 ✅.
  • July 5: 14.0.0-rc1 ✅.
  • July 8 July 12: 14.0.0.

#14-0-0, #notification

Translating BuddyPress texts into your community vocabulary is back in 14.0.0

Thanks to WordPress 6.5 localization improvements, we’re happy to share with you this great news: customizing BuddyPress texts according to your community site’s purpose is possible again without any additional plugins 😅. Whether you use the default WordPress locale (en_US) or any other ones, you can override it to change all the BuddyPress texts of your choice! Below is an example of my test replacing all “group” terms with “team” ones.

We thought as we made it possible for you to customize any BuddyPress URLs since our previous major version (12.0.0), we had to bring back custom translation files locations (which sadly vanished 😭 when WordPress 4.6 was released, 8 years ago).

We even extended it so that you can also have custom translation files for BuddyPress blocks 👇

If you’re wondering what you’ll have to do to enjoy it, here’s the documentation about it.

You need to view it to believe it? Be my guest: you can beta test it (& contribute to BuddyPress beta testing 😁).

#14-0-0, #translations

BP Docs-Chat Agenda June 26, 2024

Hi!

Our next documentation meeting will happen on June 26, 2024, at 19:00 UTC in #BuddyPress. Here’s our agenda:

  • BP Documentation tracker status.
  • Review the 23 open issues that are labeled “user“. ➡ The 23
    • Determine which of the 23 belong to WP Admin screens/pages., e.g., Activity, Group, etc.
    • If WP Admin, determine if we need a label to earmark these for priority.
    • Determine if we are missing issues for WP Admin screens/pages, e.g., needs help tab and/or link to GitHub document.
  • If time permits, review workflow process, e.g., there are currently 42 open issues, of which only 4 are unassigned: does this mean the other 38 are currently being worked?
  • If time permits, Open Floor.

If you have specific/additional points you need to discuss, please share them in the comments area of this post.

#agenda, #docs-chat, #documentation

BP Docs-Chat Summary June 13, 2024

BuddyPress Issues and Pull Requests:

  • @vapvarun: Shared updates about closed pull requests on Group Type and Group Cover Image, highlighted 41 open issues, and submitted a new PR on joining private groups.
  • @imath: Acknowledged @vapvarun‘s updates and planned to address the next tasks.

Documentation and Translation Discussions:

The group discussed where to place documentation for advanced users and suggested making it accessible to regular users. There was a consensus on the need for easy access to translation tools and documentation on customizing labels, messages, and URLs.

Handling Language Translation Paths:

  • @vapvarun and @imath: Discussed handling language translation files in WordPress, focusing on paths and behavior post-updates.
  • @vapvarun: Advocated for the need to translate common labels and messages for normal users, emphasizing site-specific customizations.

Prioritizing Documentation Efforts:

  • @imath: Suggested deciding where to place advanced user documentation and questioned the necessity of a separate handbook for advanced topics.
  • @vapvarun: Discussed focusing first on user tags that require only screenshots and guides and then moving to developer tags that need in-depth work and code testing.
  • @emaralive: Expressed concerns about potential conflicting priorities in documentation efforts.
  • @espellcaste: Supported focusing on broader user documentation before delving into advanced topics.

Technical Issues and Project Management:

  • @emaralive: Reported a bug in BP Tools for managing opt-outs and highlighted discrepancies in label counts on GitHub.
  • @vapvarun: Suggested improvements for the BuddyPress.org UI based on developer feedback and discussed promoting BuddyPress during contributor day at WordCamp.

Concluding the Chat:

  • @vapvarun: Invited final suggestions and concluded the chat, noting the need to address documentation priorities and UI concerns.
  • @imath and @espellcaste: To explore new strategies for documentation and contribution, considering feedback on UI and technical issues.

#docs-chat, #documentation, #summary

BP Dev-Chat Summary June 19, 2024

⏳ BuddyPress 14.0.0

2 tickets were needing attention:

  • #8319 was reopened due to an issue with the BP Default theme: the way we are filtering current_theme_supports-buddypress needs some extra checks to avoid PHP warnings. The goal of this improvement is to let BP standalone theme developers opt-in for BuddyPress support globally using add_theme_support( 'buddypress' ) as well as for future specific component features using bp_current_theme_supports( array( 'activity' => 'block-editor' ) ) for instance. A patch has been added and will be committed shortly.
  • #9187 is a last minute improvement to bring back custom locations for language files. Thanks to it users will be able to fully customize all BuddyPress texts to match their community needs (eg: using “teams” instead of “groups” etc..) without fearing their language files to be updated with the regular BuddyPress ones. A patch enjoying WordPress 6.5 l10n improvements is ready to be committed.

Working on BuddyPress documentation is helping us finding bugs or potential improvements: #9187 can thank this PR being reviewed, @emaralive found a regression introduced in 12.4.1 as well as an issue with the BP Opt-outs tools screen options.

We’ve decided to set Beta2 release date to June 24 (next monday). If you haven’t tested Beta1 yet, please be our guests!

14.0.0 updated schedule

  • June 13: 14.0.0-beta1 ✅.
  • June 24: 14.0.0-beta2
  • July 8: 14.0.0.

Open floor

  • 12.6.0 milestone is there in case we’re releasing 14.0.0 after WordPress 6.6 is released. Main goal is to preserve the Notification WP Admin bar “bubble” position since 6.6 has made some changes into this area lately (See #9182).
  • We talked about the BuddyPress.org site’s new theme project (see #9193). The simpler the better (@emaralive).
  • @johnjamesjacoby reminded us that when we were batch closing all buddypress.org issues, we are effectively also closing them for bbPress.org, because they share a common codebase 😬.
  • WCEU 2024 was great! @vapvarun went there, met with Matt and with other great developers that may get involved into BuddyPress. The more we are the better (@im4th).

Next Dev-Chat

It will happen on Wednesday July 3, 2024 at 19:00 UTC in #BuddyPress.

#14-0-0, #dev-chat, #summary

BP Dev-Chat Summary June 5, 2024

🧰 BuddyPress 14.0.0

We started by talking about the ticket #7658 (the BuddyPress logged in user can be desynchronized with the WordPress logged in user during some REST API Requests) & whether to look at it later (during 15.0.0 development cycle) @im4th said he’d try to have another look to it asap.

@dcavins led the chat & reviewed the 14.0.0 milestone’s remaining tickets as we were very close to our Beta1 initially scheduled date (Beta1 was planned on June 6).

  • @renato’s been doing a great job about improving Docblocks (See #9164). We closed this ticket to carry on improving this part in 15.0.0 (See #9173).
  • We haven’t progressed much about dealing with potential malformed inputs (#9065), but @im4th thinks we should work on it progressively very early during next milestone (15.0.0).
  • About #9163 (we shouldn’t allow the last admin to be removed from a group) @espellcaste was waiting for additional feedbacks from @im4th (he did so 4 days ago about the BP REST API part) & @emaralive (the BP CLI issue has been fixed). This ticket is now fixed.
  • #9117 (redirecting buddypress post type guid to their pretty URL) has been delayed to 15.0.0.
  • Ticket #9126 (Editing some table schemas to be compatible with WP Playground) has been fixed and it allowed us to ease 14.0.0-beta1 testing (see #9185).
  • #7228 a lot of WordPress code standards improvements has been committed during 14.0.0 milestone, so we fixed this ticket & @espellcaste will carry on working on this task during 15.0.0 development cycle (see #9174).
  • About #8319 we improved the way we deal with Standalone Theme supports so that we’ll soon be able to release the BP Activity Block Editor add-on soon.
  • @im4th didn’t find the time to progress about making BP Signups a de-activable feature (see #9057), it has been postponed to next major release.
  • Finally, the issue about deleted users private messages display (see #9160) needs more time so that we take the right decision about it as we currently aren’t consistent between the web and the REST API versions. We’ll be back on it during next milestone.

We’ve decided to delay beta1 release by a week to finish the last details about code and communication (eg: the announcement post). As this summary is written very late, you should know 14.0.0-beta1 has been released on June 13.

14.0.0 updated schedule

Next Dev-Chat

It will happen on Wednesday June 19, 2024 at 19:00 UTC in #BuddyPress.

#14-0-0, #dev-chat, #summary