In keeping with our WordPress compatibility policy, BuddyPress 2.6 will require WordPress 4.1. See https://buddypress.trac.wordpress.org/ticket/7013.
Version 2.5.0 “Medici” has just been released! Check out the official release post.
Many thanks to all contributors!
Growing out of some discussions between team members over the last year or two, along with some musing on https://buddypress.trac.wordpress.org/ticket/6258, I’ve drafted a page explaining our WP version compatibility guidelines: https://codex.buddypress.org/wordpress-version-compatibility/ I’m sure that anyone reading this site always runs WP bleeding on their sites😉 but if you have any thoughts on these guidelines, please feel free to comment here.
On a related note, BuddyPress 2.4 will require WP 3.8. We will no longer actively build workarounds for WP < 3.8, and 3.7 will be removed from our Travis matrix (3.6 was already untested – 3.7 was when the /src transition took place). See https://buddypress.trac.wordpress.org/changeset/10031 and https://buddypress.trac.wordpress.org/ticket/6258#comment:9.
BuddyPress 2.3.2 is now available. Go get it! https://buddypress.org/2015/06/buddypress-2-3-2/
BuddyPress 2.2 will introduce the basics of a Member Type API. The primary goal of the API is to provide a common framework for the storage and retrieval of arbitrary member types, a common task on BuddyPress sites. See #6006 for more background.
The new Member Types page on the BP Codex outlines the details of the API, so that developers can get acquainted with the new tools.
In BuddyPress 2.2, BP will provide native support for a number of features beyond the mere fetching/storage of member type data. When BP detects that member types have been registered by a plugin/theme, the following items will be exposed:
- Member queries (
BP_User_Query) can be filtered by
'member_type'. This allows developers to filter member lists in directories and elsewhere.
- A Member Type metabox will appear on each user’s Community Profile page in Dashboard > Users. Admins can use this metabox to view and change the member type for the current user.
We think that these tools will serve as the foundation for various new features in plugins, themes, and in future versions of BP itself. See, for example, #5192 (show different xprofile fields to different types of members) and #6060 (on Dashboard > Users, display member types and allow filtering by member type). Developers: as you start using this framework, we hope you’ll provide us with feedback and ideas for improving it in future releases.
Hi everyone – I have a few items I’d like to discuss during tomorrow’s dev chat, and I thought I’d start a list here so that others could add their own:
#6005 – Some improvements to the interface on the Messages screen. Started as some minor improvements to no-js support, but has blossomed into some more intermediate-level interface changes. Mainly, I want to be sure that the team is on board with making changes of this magnitude in bp-legacy.
#6008 – After some discussion, we’ve moved toward the recommendation of removing HTML altogether from page titles in theme compat. This will mean moving the “Create a Group” and “Create a Site” buttons elsewhere, and will mean a slight change in existing behavior for users who expect the title to be clickable. I’d like for the team to agree on whether this level of breakage is OK, given the benefits.