2.8.0 RC1 is now available: https://buddypress.org/2017/02/buddypress-2-8-0-release-candidate-1/
- Release Candidate 1: Imminent
- There are 83 tickets slated for this release and only 2 remain open.
@slaffik packaged and released BP 2.8 Beta 1 last January 19.
BP 2.8 Trac
BP Email: Allow end user to specify which PHPMailer should be used (#7286). @djpaul has committed patch to trunk.
get_group_extras function doesn’t “respects” the user_id variable from groups_get_groups() function (#6431). Ticket punted to Future Release.
Group Types Default Pagination Broken (#7423). @r-a-y has committed patch to trunk.
When user is not logged , in he/she clicks email link to view new messages gets 404 page when should get login page (#7349). Ticket punted to BP 2.9.
XProfile: use filterable field input name in radio/checkbox field type (#7425). @offereins has committed patch to trunk.
Group and member template functions should check current group/member as well (#3842). Ticket punted to Future Release.
Notice: Trying to get property of non-object (#7329). @r-a-y has committed patch to trunk.
Welcome Screen for 2.8.0 (#7426). Under construction.
Hook for custom email type schema (#7431). @DJPaul has committed patch to trunk.
Update and fix all the NPM things (#7429). Ticket punted to BP 2.9.
XProfile: a group’s first field becomes last after save (#7428). @offereins has committed patch to trunk.
BuddyCamp Miami, March 24, 2017
WordCamp Miami hosts BuddyCamp for the 6th time and this year, expect a REST API workshop along with interesting BuddyPress topics in this single full-day event.
As of Feb. 6, topics for the “BuddyCamp + REST API” track on Friday, March 24th, include:
- “BuddyPress 101: What You Need To Know” by David Laietta
- “Taming BuddyPress” by Tanner Moushey
- “A BuddyPress Case Study” by Tara Claeys
- “How To Build A WordPress/BuddyPress Mobile App” by Brian Messenlehner
- “The State of BuddyPress” by John James Jacoby
- “Working With The WordPress REST API” by Joseph Van
- …more speakers and surprises to come!
WordCamp Miami 2017 will be held over the course of three days, March 24-26, at Florida International University.
BuddyPress 2.8 will be released in a couple of weeks, and it’s time for our community to start considering release leads for BuddyPress 2.9 and 3.0.
Our experiments with the release lead role over the last year have worked out well, and for BuddyPress 2.9 and onwards, we’re opening up the nomination process publicly for improved transparency.
The release lead works with all contributors to ensure the success of the release. The role blends aspects of being a product manager, project manager, engineering manager, release manager, and community manager. Release leads do not need to be developers, but having experience contributing to open source projects is required.
Release leads are supported by the lead developers, the project team, and deputies of their choosing. Volunteering as a release deputy is a great way to give it a try and learn about the process, but with a smaller time commitment.
For the sake of clarity, BuddyPress release leads and their deputies, between them, can expect to:
- Run our weekly project meeting, and write and publish meeting notes on our development blog.
- Coordinate blog posts and announcements on social media.
- Make final decisions about whether a proposed feature is able to be put into the release.
- Help new contributors make their contributions seen and heard in project meetings.
While BuddyPress is built by people volunteering their own time, contributing whatever they want, however they want, the release lead should take advantage of their position and use it to shape BuddyPress. For example, if the release lead feels that the next release should have a focus on specific aspects, we expect them to declare this, and try to encourage regular contributors to make that a reality.
Are you interested?
If you are interested in volunteering to be a release lead, please comment here or contact either myself (@djpaul), Boone (@boone), or John (@jjj) on Slack.
It’s shipped and ready for testing! Details in a blog post:
BP 2.8 Trac Tickets
Anonymize BP Core Dependency functions file. (#7335) Closed as wontfix.
@dcavins would like notifications from Trac for new tickets under the Group components. He mentioned different workarounds like getting Slack notifications for the Groups component to getting the RSS feed from Trac for the specific component. @johnjamesjacoby: “We’d need to merge into our Trac what’s already in WordPress Trac. That’s probably Dion and/or Nacin.” @netweb noted after the chat that there’s a ticket in Meta Trac to get this underway.
🥂 Wishing Everyone a Happy & Prosperous New Year! 🥂
Dec. 21 https://wordpress.slack.com/archives/buddypress/p1482350517001398
Dec. 28 https://wordpress.slack.com/archives/buddypress/p1482955219002247
Slack log: https://wordpress.slack.com/archives/buddypress/p1482426116001568 (at the time I’m writing this, there seems to be a Slack bug that’s causing a 30-minute gap in the log)
Present: boone, codeart, chetansatasiya, chiragpatel, rekmla, ckchaudhary, espellcaste, offereins, modemlooper
I started with a couple discussion topics for moving toward our inital
- We decided that xprofile data will be available (and updateable) via the
/members/endpoints. So the
memberschema will have something like an
xprofile_dataproperty, which will be an array of fields and their data. For performance, we’ll explore having a parameter that allows the client to specify the xprofile fields that should be return in a request (or to disable them altogether).
/members/routes will have full CRUD endpoints, even when those endpoints are totally redundant with WP’s corresponding
usersendpoint. This is specifically the case with
- Avatar URLs will be available as part of the default member object. We’d like to explore the ability to create and update avatars via the API, but this will be a parallel project that shouldn’t block the
membersendpoints. (Avatar creation will require some discovery mechanism for clients to determine the proper size/aspect ratio, and will require the client to handle crop/resize, at least in the first implementation.)
codeart and chiragpatel will spend some time over the next few weeks collaborating on a first pass at the endpoint controller and the data schema. Our next meeting will probably be during the first week of January, depending on progress; a time will be announced next week.
- Release Date: TBA
- There are currently 2 tickets in queue (1 open, 1 closed).
- Can ‘change’ visibility on registration form even for fields marked “Enforce field visibility” (#7391) Ticket has been reopened to address coding standards.
- Notice: Trying to get property of non-object (#7329) Has patch. Requested dev feedback from @rayisme
- @djpaulgibbs: We are incompatible with PHP 7.1 as things stand – and I think we may have to rely on a fix in WordPress 4.7.x as well – so that’s the sort of thing that will likely go out once it’s ready.
BuddyPress 2.8 Tickets
PHP Fatal error: Uncaught Error: Call to a member function get_do_autolink() on null (#7337) @slaffik has patch. @djpaulgibbs noted that patch should extend beyond preventing fatal errors to making the function usable outside the template loop.
Uninstall button and routine (#2755) This ticket would have to be put on hold until decisions are made on routines and details required to export/copy then delete/drop BP DB tables and other options.
Slack log: https://wordpress.slack.com/archives/buddypress/p1481745673000991