Dev Chat Summary for September 30, 2015

BuddyPress 2.3.4

  • Tickets slated for this minor release are available on this page.
  • Release date: TBA.

BuddyPress 2.4.0

  • BP 2.4.0 Beta: October 7, 2015
  • BP 2.4.0 Release: October 28, 2015
  • Fifty tickets have been closed to date. The list of tickets completed so far is available on this page.
  • There are 91 tickets left in queue.

Add UI for adding Profile Header Images for Users and Groups (#6570) Feature is in trunk. https://bpdevel.wordpress.com/2015/09/30/buddypress-2-4-0-will-introduce-cover-images-for-members-groups/
Per @im4th: Testing and feedback welcome!

Groups single item home : improve the way we deal with custom front and activity component (#6388) Feature is in trunk. https://bpdevel.wordpress.com/2015/10/03/get-ready-2-4-0-will-introduce-important-changes-in-groups-homes/ Per @im4th: Testing and feedback welcome!

Twenty Sixteen BP Companion Stylesheet. Per @hnla, this stylesheet for the upcoming default theme along with the BP companion stylesheet for Twenty Thirteen (#6533) will be released for 2.4.0. As always, testing and reporting areas which need improvements are welcome.

Template Versioning (#6642) @hnla is working with @im4th on this new feature to provide users with a list of changes to BP template files during a dev cycle @ https://github.com/imath/bp-template-checker. Discussion held in chat touched on specific processes and expectations, including: the possibility of including this for BP 2.5.0; not showing message to admins/regular users, i.e., feature is enabled when developer adds define('WP_DEBUG', true); in wp-config.php; and “show this information in a developer-y way – maybe via_doing_it_wrong() – but to be able to suppress specific notices”, among others.

Email API and customisation features (#6592) @djpaulgibbs said that he’s not sure whether this feature would make it for 2.4.0 where it would also allow time for testing and feedback. He thanked @timersys and @shanebp for feedback on his latest updates. Calling those who volunteered to get involved on Slack 🙂

Use wp_editor for “multi line text area” xprofile field in frontend (#5625) @boonebgorges is working on this ticket and will “try to carry it across the finish line for 2.4.0.”

@since standard not parseable with phpDocumentor 2 (#6576) @tw2113 has completed the standardization of @since tags for all components to pave the way for the upcoming developer.buddypress.org. In addition, he left a friendly reminder that “WP docs standards do say to have inline comments treated as proper sentences, so capitalize the first letter and provide punctuation please.”

Slack log: https://wordpress.slack.com/archives/buddypress/p1443639711001089

#5625, #6388, #6533, #6570, #6576, #6592, #6642, #dev-chat

General Summary as of September 9, 2015

This is a compilation of dev chats held in August 26, September 1, and September 9.

BuddyPress 2.3.4

There will be a minor release coming up to address some necessary fixes and updates. Five tickets are currently slated for this release, four of which are still open.

  • The list of tickets slated for BP 2.3.4 are available on this page.
  • Release date: TBA

BuddyPress 2.4.0

  • BP 2.4.0 Beta: October 7, 2015
  • BP 2.4.0 Release: October 28, 2015
  • Features slated for this release are available in our Trac Milestone

TICKETS COMPLETED

Forty-one trac tickets have been fixed to date. The list for all tickets completed so far is available on this page. Notable:

User roles with differents profile fields (#5192) Many thanks to @boonebgorges, @Offereins, @tanner-m, and @im4th, work on this ticket has been completed and the “first killer feature for member types” is available for testing and feedback.

ONGOING WORK

Ninety-one more tickets are slated for 2.4.0 to date. You can keep updated with the complete list of these tickets on this page. The following have been highlighted in compiled chats:

xProfile Fields and Field Groups@johnjamesjacoby continues work on enhancements and fixes for the xProfile component, specifically querying & sign-up fields. Patches coming up.

@since standard not parseable with phpDocumentor 2 – (#6576) In preparation for setting up developer.buddypress.org, @djpaulgibbs posted that our current @since tags are not being parsed/extracted correctly per his tests. @tw2113 has accepted the task to convert the @since tags throughout the project and has already completed the conversion in four component folders to date.

Email API and customisation features – (#6592) @djpaulgibbs has posted the scope and vision for the first version of BuddyPress Emails. He has started work on this already in his github repo but would need to “add a bit more code” before he reaches out to all who said they wanted to help with this new feature.

Create New Invitations API – (#6210) @dcavins continues work on the Group Invitations API which needs some other trac tickets to be completed first. To start off, he has introduced a new function `groups_send_invite_by_invitee()` to handle sending a single invitation keyed by the invitee ID and group ID. In conjunction with that, he is working on adding a “manage invitations” pane to the group admin screen.

Let’s give post-form.php the love – (#6569) In ticket, @im4th, @rayisme, and @modemlooper have been in discussion about improving the UI of the Activity post form. @im4th has uploaded patches which include new hooks and reorganization of the post form. @im4th added, “We want to make it possible for any plugin to add custom ‘attachment’ types.”

  • @johnjamesjacoby noted that “with cover photos and avatar upload improvements, @im4th and @rayisme have both done a good job of assessing the typical user and use cases” when @modemlooper voiced his concern about adding new functionalities directly to core instead of introducing such as feature plugins first.
  • @boonebgorges mentioned that he “maintained a lot of BuddyPress sites and knew the pain of having an update introduce UX that he hadn’t prepared for. But I know how to deal with this, and it seems better than the alternative, which is disabling new stuff by default, and never having anyone use it.”
  • @rayisme said that an admin option to turn off attachments is doable and makes sense.
  • @im4th averred that new features will be extensible as usual and will include documentation.

Add UI for adding Profile Header Images for Users and Groups (#6570) and BuddyPress Modal Iframe (#6604) – @im4th has been rocking it with the new cover photos feature along with @rayisme. In the latest patches, in addition to the new UI for cover photo uploads for members and groups in the frontend, @im4th has added uploading via new BP Modals in the frontend and backend for both profile images and cover photos. Very cool, check it out 🙂

Commit Access

BuddyCamp Brighton Videos

The following videos are now available at WordPress.tv:

Enjoy 🙂

#5192, #6210, #6569, #6570, #6576, #6592, #6604, #dev-chat

Dev Chat Summary for August 12, 2015

BuddyPress 2.3.3

Release Date: After WP 4.3.0 rolls out next week.

There are three open tickets:

  • Wrong shape of the CROP size of the group thumbnail (#6551)
  • Mentions.js fails on wp-admin post editor (#6487)
  • WP 4.3 changes in WP_List_Table (#6465)

@djpaulgibbs has volunteered to help move these tickets forward.

BuddyPress 2.4.0

Add UI for adding Profile Header Images for Users and Groups

  • (#6570) @im4th opened the conversation which lasted ~ one hour on the best way forward for this new feature. This resulted with great feedback from @johnjamesjacoby, @rayisme, @djpaulgibbs, and @hnla.
  • Points made:
    1. Feature is available for all themes. bp-legacy‘s member-header.php gets the new hotness, and nothing gets broken if the feature is not activated.
    2. Create new template part with new markup, styles, and JS as needed
    3. Integrate a flexible header image for admin-area profiles, user dashboard
    4. If a custom template part is used in theme, then nothing happens because theme compatibility would never include anything in bp-legacy. If they are relying on theme compatibility and bp-legacy then they get the new markup and CSS that we give them.
    5. Users/theme authors will be able to edit their home.php template to support this new feature
  • More to follow. Odds are, there will be some fast and furious work coming soon.

Conversation replies don’t immediately inherit the HTML of custom templates

  • (#6572) @rayisme introduced a new template part to replace the hardcoded markup used to render a single message item in ticket. Discussion in dev chat then ensued to solve one of the two hard things to do in computer science, naming things . Consensus was reached on the name of the new template part, simply message.php.
  • Update: Patch has been committed to core.

@since standard not parseable with phpDocumentor 2

  • (#6576) @since tags throughout the BuddyPress project needs to be revised/updated to parse docs correctly in preparation for developer.buddypress.org.
  • @tw2113 will be working on this.

Attachment API conflicts with wp_enqueue_media()

BuddyCamp Brighton, U.K.

This event was a success based on the feedback from the attendees. Congratulations to @djpaulgibbs and @karmatosed, organizers of the first BuddyCamp in Europe, as well as to all the speakers and presenters!

  • @im4th has posted about his BuddyCamp experience in français along with his slides at his site.
  • @modemlooper has uploaded his BuddyCamp video about mobilizing your BuddyPress site @ Dropbox.

If you want to include links to your BuddyCamp Brighton slides/videos or photos, post a comment below and we’ll add it to the list above.

Slack log: https://wordpress.slack.com/archives/buddypress/p1439406192001125

#6465, #6487, #6551, #6570, #6572, #6574, #6576, #dev-chat