Core Dev Chat Summary for January 27, 2016

Trac Tickets

Comment syncing between activity and post comments for Custom Post Types (#6842)  @im4th needed to run an upgrade routine to add a new activity meta to activities about a blog post and consulted whether he could do this using a regular upgrade routine or wait for #6841 to be fixed to committed to core.  @boonebgorges, @djpaulgibbs, @johnjamesjacoby, @rayisme, and @dcavins joined in the discussion to find the optimal solution in the upgrade routine. @im4th also suggested using a dynamic meta_key so that he could avoid the upgrade routine. Update: @im4th has uploaded a new patch which shows that using the dynamic meta_key can avoid an upgrade routine 🙂

Profile/Cover image upload doesn’t work in MS Edge browser (#6846) Update: @im4th just committed to trunk and 2.4 branch so this one’s fixed already 🙂

Email API and customisation features (#6592)  @djpaulgibbs has started committing section by organized section of this cool new feature last week (Jan. 27). Dev feedback welcome.

BuddyPress 2.5.0

  • Beta 1: February 8, 2016
  • RC 1 (string freeze): February 22, 2016
  • Target Release Date: March 2, 2016
  • There are 126 tickets slated for this cycle to date. (Closed: 41. Active: 85)

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

#6592, #6842, #6846, #dev-chat

Core Dev Chat Summary for January 20, 2016

This summary includes pertinent developer conversations in Slack before and right after the official chat time last week.

Trac Tickets

Email API and customisation features (#6592) Three hours before dev chat, @boonebgorges and @djpaulgibbs had a long and interesting discussion about the new Email API. Topics covered: standardizing verbs for method names, choosing taxonomy for Email Types to give admins the option of implementing multiple templates, among others. Latest: @djpaulgibbs has since updated the `amazing-emails` branch at https://github.com/paulgibbs/buddypress/

XProfile field database schema (#6350) @johnjamesjacoby will be writing down his vision for improving the xProfile tables.

Groups: Add Profile Fields and Profile Field Groups (#6783) From an enhancement for the Groups component, @im4th has proposed a change in direction to making this a generic component which would work for any object (Members, Groups, and Blogs) in ticket. @im4th consulted with @johnjamesjacoby about the best way forward.

Comment syncing between activity and post comments for Custom Post Types (#6482) @imath and @rayisme deliberated and agreed on adding `bp_activity_type_supports()` which works similar to WP’s `post_type_supports()` function. This would provide some flexibility if/when more features are added to BP activity types in the future.

General Administration

Messaging

A lively brainstorming session arose from a proposal by @johnjamesjacoby to replace the old “social network” association used for the past 8 years. There were slogans, taglines, and observations shared during and even after the chat:

• If we’re going to change it, can we think of it more as a strategic/goal/mission statement—more than just a tag line? ~@dcavins
• Social network” and “in a box” are both icky. Something having to do with “community” is better than “social network”. As for “in a box”, it glosses over the developer-focused flexibility of BP, which IMO is one of its strong points. ~ @boonebgorges
• It (“BP as a platform”) seems technically accurate, and speaks to the breadth of purpose, and I think it’s meaningful to a non-technical audience. I think we have two audiences – network builders and developers – so maybe our branding should have two parts too ~ @boonebgorges

BuddyPress. Go Social. Build Communities. Create Networks. ~ @mercime
Enabling Community Platforms ~ @hnla
Building Blocks for your Community ~ @jjj
Community toolbox ~ @karmatosed
Community components you can put together in a very easy and funny way ~@im4th
A suite of social components for building communities ~ @pollyplummer
BuddyPress. A developer/professional platform that can scale up to millions of users. ~ @mercime
BuddyPress: Create your own community space ~ @rayisme
You have the users, BuddyPress (has) the building blocks to kit out your community to the fullest ~@netweb
BuddyPress, an online community building kit ~ @robkk

Fun & flexible software for online communities, teams, and groups.
BuddyPress helps you build any type of community website using WordPress, with member profiles, activity streams, user groups, messaging, and more.
~ @johnjamesjacoby

New BudddyPress.org Theme

@johnjamesjacoby noted that the “theme needs a complete revamp and redesign to make it more attractive. I would like for BuddyPress & bbPress to be powered by the same theme, so that they are effectively co-branded as such.” Someone’s going to be tapped to work on the new theme.

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

#dev-chat

#6350, #6482, #6592, #6783

Core Dev Chat Summary for January 13, 2016

BuddyPress 2.5.0

  • Beta 1: February 8, 2016
  • RC 1 (string freeze): February 22, 2016
  • Target Release Date: March 2, 2016
  • There are 113 tickets slated for this cycle to date. (Closed: 29. Active: 84)

Trac Tickets Mentioned

Comment syncing between activity and post comments for Custom Post Types (#6482) @imath Patch updated. Dev feedback needed.

Comment notification NOT notified (#6057) @imath Has patch. Ready to commit. Dev feedback needed.

Manage Signups on Network Admin dashboard returns Blog Admin URL, not Network Admin URL (#6371) @imath Has patch. Ready to commit. Dev feedback needed.

Deleted activity items remain favourited (#3794) @imath Wants to reactivate the discussion on this issue. Has patch. Dev feedback needed.

developer.buddypress.org (#6812) @tw2113 has gotten the parser to work on the codebase. He will focus next on the “Members based functions” and the theme.

Email API and customisation features  (#6592) @djpaulgibbs Has uploaded separate patches for any “drive-by code reviews”. Dev feedback needed.

Slack Log: https://wordpress.slack.com/archives/buddypress/p1452715302003088

#3794, #6057, #6371, #6482, #6592, #6812, #dev-chat

Dev Chat Summary for January 6, 2016

The first dev chat of the year focused on the 2.5.0 release scope. There are currently 104 tickets slated for  this dev cycle: 22 closed and 82 active. The following were mentioned during dev chat (major features have asterisks).

API

*BuddyPress Embeds for activity, user profiles, groups (#6772) @rayisme and @im4th work on ensuring that nested embeds show up as well as preventing embeds from breaking layout, among others.

*Create New Invitations API (#6210) @dcavins has written a bunch of tests for this feature in the last two releases. He’s currently working on the actual code changes and it’s going pretty well. Ultimately, he mentioned he’d like nearly all of the  features of Boone’s Invite Anyone plugin to be rolled in.

*A new API to manage single items navigation (#6534) @boonebgorges

*Email API and customisation features (#6592) @djpaulgibbs will be ready for review in a week or so. He has done lots of work on it and has recently posted an extensive technical update in ticket.

*Group Types API (#6784) @boonebgorges

BLOGS

*Comment syncing between activity and post comments for Custom Post Types (#6482) @im4th has patch which ready for  review/testing.

CORE

Use WP page names for BP directory pages headings (#6765) @hnla

Hooks Documentation Continued @tw2113

GROUPS

Add function to send single invitation (#6025) @dcavins is working on this in relation to the main ticket (#6210) Invitations API above.

NOTIFICATIONS

Comment notification NOT notified (#6057) @im4th will refresh the patch next week.

Screen notifications settings page (#6712) @rayisme

TEMPLATE PARTS

*Companion Stylesheet – Twenty Twelve (#6766) @hnla has committed the first pass of the SASS and compiled CSS files.

BP Users front.php (#6769) @hnla

XPROFILES

*xProfile fielddata visibility should be stored in xprofilemeta (#6413) @boonebgorges has the patch written, “just some work to do on making the migration routine less insane.”

*xProfile fields used for signup should be configurable (#6347) @johnjamesjacoby

xProfile field database schema (#6350) @johnjamesjacoby

BUDDYPRESS.ORG

*developer.buddypress.org (#5129) @tw2113 is working on the parser

GENERAL – ADMIN/UI

Accessibility Upgrades Continued @mercime

FOR NEXT WEEK:

  1. REST API
  2. “Social Network” vs. “Community Software” marketing direction

#5129, #6025, #6057, #6347, #6350, #6413, #6482, #6534, #6592, #6712, #6765, #6766, #6769, #6772, #6784, #dev-chat

General Summary as of December 23, 2015

This is a compilation of dev chats held in December 2nd, 9th, and 16th. There was no official dev chat last Dec. 23, we just had some BP Holiday fun.

Minor Releases

BuddyPress 2.4.4

BuddyPress 2.5.0

  • BP Beta 1: February 8, 2016
  • BP RC 1 (string freeze): February 22, 2016
  • BP 2.5.0 Target Release Date: March 2, 2016

Feature scope continued from last November 25:

Email API and customisation features (#6592) @djpaulgibbs reported Things are going well with the new feature.

Comment syncing between activity and post comments for Custom Post Types (#6482) @im4th will try to update patch and write unit tests.

Screen notifications settings page (#6712) @rayisme

Accessibility Improvements Part 2 (has tickets) @mercime

developer.buddypress.org @tw2113 has started work on the parser and fixing errors.

Navigation API tweaks for single items (#6534) @boonebgorges will be working on this for the next 2 weeks.

Create New Invitations API (#6210) @dcavins will update patches. @boonebgorges will be working on this for the next 2 weeks.

BuddyPress Embeds for activity, user profiles, groups (#6772) @rayisme has started working on this. @im4th has given feedback on the ticket.

Companion Stylesheet – Twentytwelve (#6766) @hnla has uploaded the stylesheets to trunk. Feedback welcome.

BP Users front.php (#6769) @hnla

xprofile fielddata visibility should be stored in xprofilemeta (#6413) @boonebgorges

BP JSON REST API @modemloooper. @marmaduka has volunteered to help. @djpaulgibbs and @boonebgorges were in agreement that the project would go through some documentation/vision phases before starting to write code. The BP JSON REST API would be introduced into core when the feature is “complete”, i.e.,  all read-only endpoints or an entire component, etc. This will be built as a plugin first. @djpaulgibbs also suggested that the eventual BP REST API plugin/module/eventual core integration require modern PHP.

#6210, #6482, #6534, #6592, #6712, #6766, #6769, #6772, #dev-chat

Dev Chat Summary for November 25, 2015

BuddyPress 2.4.1

  • As of 11/30/15, 2.4.1 will be released this week.
  • Six of the 7 tickets slated for this release are all good to go.
  • (#6675) WP 4.4. deprecates wp_title() will be moved to BP 2.4.2 which is scheduled sometime after WP 4.4.0 is released.

BuddyPress 2.5.0

  • @djpaulgibbs proposed start of dev cyle on Wednesday, Dec. 2, and release by March 2, 2016. He also mentioned that “we will lose probably a few weeks’ worth of development over Christmas, but I’d rather keep the pace up even if that means a smaller release.”
  • @boonebgorges noted that “in the last couple releases we’ve done fairly long beta/RC periods. I think it’s been good to be conservative. But they’ve also been too long for what we’ve actually needed. So if we think the release might be a bit smaller, we might consider a somewhat condensed period between feature-freeze and release. Not something we have to decide today.”

Wishlist

These are a few of our favorite things and suggestions for this dev cycle:

Improve BP Navigation from @im4th. @boonebgorges has started work on ticket last week refreshing the `BP_Nav` ideas. He will “dive into it after WP 4.4 comes out.”

Clear out all trac bugs from@tw2113.

Update Member home page to match new functionality of Group home page from @hnla. Can start off with user’s own `front.php` template and expand on top of this later.

BP Emails from @djpaulgibbs. This involves “architectural improvements to emails, and customizable emails. (#6592)

xProfiledata_meta from @boonebgorges.  Fix the way xProfile field visibility is stored (move from usermeta to xProfiledata_meta), which will make the data schema saner and also allow us to fix some search-related bugs.

Do the @todo items in codebase from @tw2113.

Improved caps from @im4th. Currently doing it in his template pack project.

Hashtags from @jconti. @slaffik noted that there are two BP-compatible hashtag plugins in WP repo. Chat continued on whether hashtags will be used for search vs. auto-completing hashtags or both.  @rayisme has worked on a fork of etiviti’s older hashtags plugin, will require at least some form of unicode support. He will be working on “Better compatibility when using ‘BP_ENABLE_USERNAME_COMPATIBILITY_MODE’ and UTF-8” which would also support emoji hashtags mentioned by @djpaulgibbs.

BP Template Versioning from @hnla. Feedback requested on current ticket to move the project forward.  (#6642)

developer.buddypress.org from @mercime. @djpaulgibbs noted the logistics required and testing will be needed before deployment. @boonebgorges mentioned some devs expect projects with stable APIs to have web-based documentation generated even when they are already big fans of the inline documentation.

Add “semi-private group” from @mercime. @boonebgorges pointed out that there were a couple tickets about separating the various parts of group status into standalone bits, so that you could make custom group types  like visibility vs join/invite vs who-can-invite etc. A version of “semi-private” would be some combination of these things. (#6094)

Bulk mentions for Groups from @jconti.  Feature is akin to Slack’s @ {here} {channel} {etc}. @djpaulgibbs noted that “the complexity there is around updating the notifications and probably a per-group setting to turn that on/off, when I rewrote the auto-suggest lookup stuff about a year ago, I had it in mind to be able to support group mentions, so there’s some work done already. @im4th brought up concern about notifications (emails) if a group has 200,000 members.

Reactions instead of favorites, dream from @im4th@boonebgorges replied with “A dream: BuddyPress Relationship Table and API.”  @djpaulgibbs: both ideas fill me with memories of many hours spent on those, I have like a quarter-done github branch somewhere porting Posts2Posts over if anyone’s really really keen. “

Update default templates from @hnla. Explore what we can do to update the default templates – perhaps with a focus on markup in core that can be extracted out to template directories.

There are more features, bug fixes, and enhancements not mentioned above that already have tickets in Trac and some that will have tickets soon. Join the fun in making this dev cycle another awesome one for the community!

Trac Tickets for the 2.5.0 milestone are available on this page.

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

#6094, #6592, #6642, #6675, #dev-chat

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

Dev Chat Summary for September 23, 2015

BuddyPress 2.3.4

BuddyPress 2.4.0

  • Forty-four tickets have been closed to date. There are 98 tickets left. The list of tickets completed so far is available on this page.
  • @boonebgorges noted, “Those who wield the terrifying power of Commit should go through (tickets with patches) and exercise it.”

Email API and customisation features (#6592) @djpaulgibbs: “If people want to help with any particular aspect of BP emails, (you are) more than welcome to participate.” Details are available in ticket. In addition to @espellcaste and @timersys who volunteered to help out in ticket, @marmaduka and @tw2113 have also indicated their interest to do the same during dev chat.

Add UI for adding Profile Header Images for Users and Groups (#6570) @im4th has uploaded new patches based on the decisions made during dev chat and recommendation in ticket: modals are put on hold, add filter to change the default Attachments uploads directory, and some string changes. He has posted more information about how to add the new cover images in ticket for stand-alone themes with custom BP templates and still using theme compatibility as well as for those still using the bp-default theme.
Update: Post about this new feature is imminent.

Groups single item home : improve the way we deal with custom front and activity component (#6388) @im4th sought consensus on patch for 2.4.0 release. @boonebgorges gave thumbs up on the approach. @djpaulgibbs had looked at it before and had positive feedback.

BuddyPress Codex

@slaffik inquired about editing codex pages and about the avatars of article contributors which show up at the bottom of the page. He was assured that anyone who was logged in can add new articles and edit current articles. @hnla reported the avatar / author function has been broken for a while. @djpaulgibbs mentioned that the avatars code is available in meta trac but at this time, he’s concentrating on BP Emails. Just to note that all are welcome to create a ticket and provide a patch to address the issue.

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

#6388, #6570, #6592

Dev Chat Summary for September 16, 2015

BuddyPress 2.3.4

  • Release is scheduled for this coming week to fix #6606: Visibility issues with BP_Activity_List_Table::row_actions().
  • Other tickets listed in the 2.3.4 milestone will be punted to BP 2.3.5.

BuddyPress 2.4.0

COMPLETED

Forty-three tickets have been fixed to date. The list for all tickets completed so far is available on this page.
Mentioned in chat:

BP component as front page messes up blog search (#5087) @boonebgorges has completed the fix for this ticket last week. Solution includes changing the default search query arguments for each BP component to be unique to remove the conflict with regular blog searches, among others. Testing and feedback welcome.

ONGOING

Ninety-four more tickets are slated for 2.4.0 to date. You can keep updated with the complete list of these tickets on this page.

Add UI for adding Profile Header Images for Users and Groups (#6570) @im4th has set up test of the button/modals and uploads at his test site http://imath-buddypress.wpserveur.net. If you’re interested in testing this out in his site, ping @im4th @ Slack (imath). Or you can check it out in your test installation, just apply the latest patch in ticket.
@im4th sought advice on the best way to organize file uploads now especially with more BP Attachments features coming in down the road. @boonebgorges and @djpaulgibbs approved to white label the ‘buddypress’ directory as long as @im4th adds a global filter.

BuddyPress modal iframe (#6604) @im4th  noted that: 1) You can add buttons in the front end profile’s header to set avatar / cover image and 2) The real problem is that our javascript is not yet modular, so you can’t deal with avatar and cover image at the same time, meaning not having the modal would prevent us to have cover image in the Administration screens as everything is managed in one page. @rayisme noted the benefits of using BP modals in the BP admin pages. This new feature will be discussed further this week after additional review by Lead Devs.

Email API and customisation features (#6592) @djpaulgibbs has been working on the email framework and has “reached out to a couple of potential contributors to help with some of the buildout.” He has since updated the ticket to include: the link to his “Amazing Emails” repo in Github, tasks he has completed so far, a list of remaining tasks, and instructions on how you can get involved with the project. Contributors are welcome!

Accessibility Fixes – @mercime has uploaded patches to a number of tickets, most of which have been committed to core.

@hnla: Will be free this week to “work on something fun and rewarding, and look over” the cover photos ticket. Btw, he has committed the BP companion stylesheet for Twenty Thirteen. Testing and feedback welcome.

@boonebgorges: “I would like to find time to look at migrating profile field visibility over to profile meta, so that we can fix a couple of bugs there. Beyond that, I’ll just drop in and do gardening as I have time for 2.4.0” (like fixing #5087 above).

@rayisme: “There’s already quite a few big features for 2.4.0 and I want to concentrate on helping move those along”, just like he has been doing for the cover photos ticket. He has also been doing some gardening specially on the tickets slated for 2.3.4.

Boone on the “Very French Trip WordPress”

@boonebgorges was the special guest on “Very French Trip WordPress”, a podcast in French (of course!), hosted by Thierry Pigot, Grégoire Noyelle, and @im4th last September 10. @im4th remarked later, “French people (listeners) are amazed about Boone’s French level!” 

Boone spoke about how to contribute to the development of BuddyPress and WordPress , along with little Wilhelmina. The hosts also shared information about SkiPress, the very first WP coding and skiing event in the French Alps for one week, and WordCamp Paris in February 2016, among others.

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

#5087, #6570, #6592, #6604, #6606, #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