Hi!
Our next documentation meeting will happen on April 24 at 19:00 UTC (today) in #BuddyPress. Here’s our agenda:
If you have specific/additional points you need to discuss, please share them in the comments area of this post.
BuddyPress is using the $wpdb->signups table to manage signups since 2.0.0. This table which is only available into the WordPress Multisite DB schema is generated by BuddyPress on regular WordPress installs.
For 10 years we’ve been carrying on creating users to preserve backwards compatibility with 3rd party plugins relying on our “prehistorical” way of dealing with signups on regular WordPress configs, today we are finally deprecating this behavior to improve BuddyPress consistency and fix this 9 years old issue.
If you are still playing with the activation_key user meta and the {$wpdb->users}.user_status (which we used to set to 2 to mark a user as a signup), please update your code so that you now fully enjoy our BP Signups API.
In 14.0.0, we are throwing deprecation notices if you use the BP “prehistorical” way to deal with signups, but please note we will completely remove this code in 15.0.0.
Phase 1 (a.k.a., BP Codex migration meta task ) was completed which resulted in a total quantity of 271 BP Codex pages reviewed, which netted 208 pages to be ignored and 63 pages to be migrated.
The actual count of issues created were:
For Phase 2 (a.k.a., BP Documentation meta task) the main emphasis is document creation and, if necessary, the updating of documents previously created during Phase 1, as well as Phase 2.
A question was posed (by @emaralive) as to the presentation of statistics for Phase 2; IOW, what should be included? @im4th suggested:
In an effort to help facilitate the tracking and gathering of metrics for the statistics @emaralive suggested and completed action to archive the 208 ignore issues. This left a total of 71 issues of which 24 issues were completed , by @im4th and @vapvarun, (status of Done) during Phase 1, which left 47 open issues (status of Todo and In Progress) and the % of complete (as of April 10, 2024) to be 34%.
Futhermore, @emaralive created additional views within the project for documentation (although, this appeared to have gone unnoticed):
Although, not explicitly stated, the additional project views could help with the gathering of data in support of the statistics, for example:
| Open | Closed | % Complete | |
|---|---|---|---|
| Migrate | 39 | 19 | 33% |
| Add | 6 | 4 | 40% |
| Update | 2 | 1 | 33% |
| Total | 47 | 24 | 34% |
Or:
| Todo | In Progress | Done | % Complete | |
|---|---|---|---|---|
| Migrate | 39 | 0 | 19 | 33% |
| Add | 6 | 0 | 4 | 40% |
| Update | 2 | 0 | 1 | 33% |
| Total | 47 | 0 | 24 | 34% |
However, presentation of documentation statistics is still open to discussion, since this topic has not been settled.
A comment was posted regarding BP Docs-Chat Summary March 28, 2024 and the poster’s concern for the deprecation of the BP_ENABLE_MULTIBLOG constant and whether this would affect a plugin the poster was using.. @im4th volunteered to make a reply to the comment and completed the action.
@vapvarun reported his efforts in support of documentation for this area of interest (Multiblog/Multi Network/Multisite):
Additionally, @im4th & @vapvarun conversed a bit about the logistics of embedding/including videos within GH (GitHub) documents.
@im4th revealed the completion of a:
Whereby documents such as the following can reside:
@emaralive suggested and volunteered to update the main README.md for the bp-documentation repo, since Phase 1 has been completed, which makes the content outdated, along with the removal of 2 issue templates (ignore & migrate) that are no longer relevant. This task has yet to be started and @im4th volunteered to review the changes, once a PR has be generated.
It will happen on April 24, 2024 at 19:00 UTC in #BuddyPress.
Hi!
Our next development meeting will happen on April 17 at 19:00 UTC 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.
🚀 💫
Although we planned to share the progress we achieved about 14.0.0 tickets, just after @vapvarun informed he will work on #9097 (Member type assignment), we focused our attention on Group roles (#8728: making sure the group’s moderator role can better assist the group’s administrators).
If #8728 is about letting group moderators delete group activities, we extended the discussion to group admins and a particular group admin : the group creator.
bp_groups_filter_activity_user_can_delete filter is not doing what it should.It will happen on Wednesday April 17, 2024 at 19:00 UTC in #BuddyPress.
Hi!
Our next documentation meeting will happen on April 10 at 19:00 UTC in #BuddyPress. Here’s our agenda:
If you have specific or additional points to discuss, please do so in the comments section of this pos
@vapvarun is testing multisite cases to prepare new screenshots and documents. Discussion on issues and complexities related to multiblog setup, including configuration and potential bugs.
@espellcaste mentioned limited testing against plugins like Redis and plans to set up CI for testing against Memcache. #9076
Identified CSS issues with the “hello” screen and other areas. Discussion on related tickets and ongoing efforts to resolve them. @emaralive tasked with investigating a specific #9111 ticket related to BP Hello menu. Discussion on focusing documentation efforts on multiblog configurations for BuddyPress.
@vapvarun working on documenting various multiblog configurations and use cases. Consensus to deprecate multiblog due to low usage and maintenance challenges.
@imath suggest to consideration of deprecating multiblog feature. @patriciab mentioned using multiblog for multilingual communities where each subsite represents a different language. @imath reassured that deprecation is not happening soon and emphasized the need to preserve backward compatibility.
Participants discussed the use cases and challenges of the multiblog feature, as well as potential implications of deprecation. Plans were made for further discussions and a demo of the multilingual community site.
It will happen on April 10, 2024 at 19:00 UTC in #BuddyPress.
Hi!
Our next development meeting will happen on April 3 at 19: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.
🌱☘️
During the chat we discussed about the opportunity to build this maintenance release a bit before WordPress 6.5. @emaralive volunteered to test the last unfixed ticket of the milestone (See #9086). At the end of our chat @vapvarun brought #9096 to the discussion. The Last activity repair tool has become obsolete and we forgot to remove it from the available BP tools. Site Admins who used it so far experienced a very annoying effect: after the last activity item are removed they are not generated back. Result is the Members directory can have no active users displayed. We’ve explained why this tool was added in BuddyPress 2.0 and came to the conclusion it should now be removed to prevent the issue about « vanishing » Active Members. We evaluated we couldn’t wait for a major release like we’re used to do for such a change and decided to fix it into this maintenance release. 12.4.0 was released on March 25.
Thanks to #9086 patch, @dcavins transitioned to a ticket slated to the 14.0.0 milestone: #9063. The goal of this ticket is to be able to have BP directory pages as children of another one. Instead of doing this @im4th’s plan is to only use the WP rewrite rules improving the BP Rewrites API to make support custom root prefix (eg: replace / by /community/ for instance.
In short, @im4th opened this ticket #9098 to explain why he thinks this feature should become a Core feature instead of being dependent of the BP Messages component.
Finally we quicky talked about BuddyPress permissions management and realized there’s a lot of possible improvements to bring to this part of the software.
It will happen on Wednesday April 3, 2024 at 19:00 UTC in #BuddyPress.
Hi!
Our next documentation meeting will happen on March 27 at 19:00 UTC in #BuddyPress. Here’s our agenda:
If you have specific or additional points to discuss, please do so in the comments section of this post.
BP Team Updates 