BP 2.8 Trac Tickets
BP 2.8 – Prevent loading if PHP < 5.3 (#7277) @boonebgorges has patch. Dev feedback requested (esp. @johnjamesjacoby & @djpaulgibbs).
Removal of `create_function` usage for BP 2.8 (#7325) @tw2113 has patches.
Anonymize BP Core Dependency functions file. (#7335) Closed as wontfix.
`groups_promote_member()` shouldn’t attempt to fetch BP_Core_User object (#7382) Patch needs unit tests. Assigned to @boonebgorges.
Add a “buddypress” class to body element of wp-admin (#7353) @slaffik has committed fix to trunk.
@slaffik will be contacting everyone who volunteered to maintain BP components in Trac.
@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
member schema will have something like an
xprofile_data property, 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
users endpoint. 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
members endpoints. (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
Some more enhancement for translators (#5784) @slaffik recommended to close the ticket.
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
We had a productive chat about the BP REST API today.
In attendance: offereins, boone, djpaul, espellcaste, mamaduka, chetansatasiya, shanebp, dimensionmedia, shitalmarakana, modemlooper (fashionably late)
We made some preliminary decisions about strategy and next steps:
- We’ll be starting with the Members endpoints, a rough list of which will be:
- create user
- update user
- delete user
- get user
- get users
This phase will also include support for XProfile data – fetching field data, setting field data, querying by field data – though it’s not yet determined whether these things will happen via separate endpoints or as query params passed to the endpoints described above.
- During the chat, we were leaning toward piggybacking on WP’s
/wp/v2/users endpoint for BP member queries. modemlooper pointed out after the meeting that WP locks down the
get_items() users query to users with certain permissions levels, and also that security plugins have blocked the endpoint altogether. This pretty strongly suggests that we should go with our own
- We brainstormed a few early ways that we might take advantage of Members endpoints in BuddyPress itself:
- member widget AJAX
- @-mention AJAX
- user search when adding users to group in wp-admin
- I’ve started a Google Doc for sketching out the existing PHP CRUD interfaces for BP content. This’ll be a helpful starting point for understanding the conventions and syntax we should use across the REST API endpoints, as well as to understand how we can come up with a set of endpoints and routes that cover all our content types in a way that is non-redundant. Anyone should feel free to pitch in: https://docs.google.com/document/d/16Wah0MQRS_ktWQSJLGfiAlxHKXORtpo-QaX9JUGxXnA/edit?usp=sharing
- We’ll be continuing to work in the GitHub repository https://github.com/buddypress/bp-rest. Improvements should be sent via PR and peer reviewed before being merged. We’ll give people merge/push permissions after they’ve proved themselves with a couple good PRs.
- We’ll have our next meeting Thursday, December 22 at 1700 UTC. Then we’ll take a break for the holidays, and hold weekly meetings at this time starting in January.
- There are currently 89 tickets slated for this dev cycle (26 closed, 63 open).
- January 4, 2017 – Beta 1
- January 18, 2017 – Release Candidate 1 (string freeze)
- January 25, 2017 – Target release date
BuddyPress 2016 Survey
The 2016 Survey will be closing this Thursday, Dec. 15. Thanks for your participation 🙂
Slack log: https://wordpress.slack.com/archives/buddypress/p1481140823000207
Companion stylesheets to support the latest WP twentyseventeen theme is now committed to BP core and will be included in the 2.8 release.
While further iterations are forthcoming shortly to address some design concerns feedback would be helpful especially browser /device testing.
Any issues spotted can be notified on this ticket:
Your comments and testing are appreciated 🙂
At slightly short notice (although briefly mentioned last week on slack) I’m resuming the template chats for Thursdays @ 20:00 utc ( or earlier if it suits more people? )
As today is at short notice the chat is a more informal one to get the ball rolling again and I hope anyone that is interested will check in and lend a voice.
We’ll keep to a short meeting of 30 mins – depending on how things go this might roll on longer.
As the Nouveau project is in a fairly complete state vis a vis templates, styles, majority of the directory structure, functions/classes etc this is the opportune moment to discuss the areas that will dictate how the template pack is managed and executed in BP core and these areas to some extent dictate how work on the project in general moves forward.
The discussion points are therefore:
- Agreement or otherwise that template packs or templates are run in the core bp-templates folder.
- If running from core do we want to implement the template switching process? See ‘UI to Pick Template Packs‘ Trac ticket & to be considered in this point is that imath has effected a very effective solution here currently in use if running Nouveau as a plugin
- If we do run multiple templates – what if any are the implications of supporting these multiple packs in terms of time updating them if required?
- In terms of styles I’ve followed a ‘partials’ approach to breaking the various components into smaller file includes compiled into the main .scss sheet, the principle notion here was that those ‘ _partials’ are maintained in <code>/src/bp-templates/shared/styles/</code> and can be used as a base set for any new set of templates (obviously not being compiled into the ‘build’ for final releases). Although I have kept things flexible so we have options I think this best approach so would seek consensus &/or opinion here.
There is a fair bit to discuss just in the points above, ideally we seek consensus on these points so we can move forward but am not expecting we can achieve this in one chat session but making a start is the important thing.
Hope to see as many there as possible.
P.S. Please feel free to leave any comments about the points above or any other thoughts on the Nouveau templates project.
P.P.S. The template pack is available here on the BuddyPress github account ‘Next Template Packs‘