BP 1.9-beta1 is now available. Check it out! http://buddypress.org/2013/11/buddypress-1-9-beta-1-is-now-available/
Updates from Boone B. Gorges Toggle Comment Threads | Keyboard Shortcuts
Since BP 1.7 and the introduction of theme compatibility, BuddyPress has worked seamlessly with pretty much any WP theme. Yet we’ve been continuing to maintain the old bp-default theme, which dates back to when themes needed to be built specifically for use with BP. For the last two release cycles, we’ve maintained more-or-less 100% feature parity between our packaged theme compat templates (bp-legacy) and bp-default. After the release of BP 1.9, this will no longer be the case. In BuddyPress 1.9, we begin the process of phasing out the BuddyPress Default theme. bp-default will continue to be packaged with BuddyPress, and will still receive critical fixes and security updates. However, it will no longer get routine bug fixes or new features.
We’ve made this decision for a number of reasons. First, it simplifies the workflow for BP contributors – patches only need to be written for bp-legacy templates. More importantly, this move encourages BuddyPress users – from developers to site administrators – to stop using the old, buggy method of loading templates (see #5241 for just one recent example of how the old method causes problems). The techniques used by our theme compatibility layer, in contrast, are more robustly integrated with WordPress’s request parsing and template loading systems, and will become even more integrated when we move to using proper WP rewrite rules. In short, theme compat is the future, and the BuddyPress ecosystem will become more stable as people gradually move away from the old themes.
Toward this end, we have, as of , stopped offering bp-default on installations that are not already using it. That means that if your site is not already running bp-default (or a child theme of bp-default), BuddyPress 1.9 will not register its bp-themes directory, and bp-default will not show up on Dashboard > Appearance. This’ll ensure that new installations don’t get locked into using the now-sunsetted bp-default theme.
If you are already using bp-default, either directly or as a parent theme, don’t worry. BuddyPress 1.9 will detect that you need bp-default, and will continue to register it with WordPress. Note that if you switch away from a bp-default theme (say, for testing), the theme will disappear from Dashboard > Appearance. If you need it back, add the following line to your bp-custom.php file:
add_filter( 'bp_do_register_theme_directory', '__return_true' );
In some future release, we’ll aim to remove bp-default altogether from the BuddyPress package. It’ll likely find a new home in the wordpress.org theme repository. We’re working on a method of doing this that’ll be as transparent as possible for existing users of the theme. If you’d like to participate in the conversation about how and when this will happen, follow #5212.
I think I speak for everyone who has worked extensively with bp-default and its derivatives when I say that this is something of a bittersweet moment. bp-default was often a bear to work with, but it also proved to be a remarkably flexible and powerful foundation for building BuddyPress sites. And oh, that beautiful blue header gradient!
The BuddyPress default theme is being phased out : Post Status, Boone Gorges, hnla, and 3 others are discussing. Toggle Comments
BuddyPress 1.8.1 is now available: http://buddypress.org/2013/08/buddypress-1-8-1/
[Thanks to Trisha for helping to compile these notes!]
After the BuddyPress dev chat on July 31, we’ve got some tentative plans for the 1.9 scope and timeline.
For the 1.8 dev cycle, our experiment with a short timeline and strict deadlines was, by most measures, a big success. We’ve had very few bug reports related to changes in 1.8, and the speed of the cycle meant that nothing sat unused in trunk for too long. We’re hoping to replicate this success by taking a similar approach for BuddyPress 1.9.
We settled on roughly the following major feature set for the 1.9 release. I’ve listed appropriate ticket numbers, along with those who’ve committed to the tasks (though, as always, more participation is very welcome).
- New template pack (@karmatosed and others; see #4952). This work was begun during the previous release cycle, and we think we’re in a good position for this to be the main user-facing improvement in 1.9.
- Move user ‘last_activity’ out of wp_usermeta. (@boonebgorges; see #5128)
- Better two-way sync of activity comments with sources like forum replies and blog comments (@r-a-y and @paulgibbs; see #1419)
- Migrating to the WP Rewrite API (@johnjamesjacoby; see #4954)
- Custom Post Type enhancements: better activity stream integration, and better dashboard support for that integration (@trishasalas and @boonebgorges; see #3460)
- Codex cleanup and refresh (@mercime and @hnla)
- August 1, 2013 – 1.9 development cycle begins
- September 26, 2013 – End of new development for 1.9. Beyond this date, nothing gets committed that is not either a bug in a new feature, or a regression from 1.8.x. Any major features from the list above that are not commit-ready by this date will be bumped. Note – The period between Aug 1 and Sep 26 is eight weeks, two weeks longer than the corresponding part of our 1.8 cycle. We’re hopeful that this extra two weeks will give us more time to wrap up big features, and perhaps to focus more specifically on scrubbing old bugs.
- October 1ish, 2013 – 1.9-beta1. We’ll release the first beta as soon as the cleanup from the dev period has taken place.
- November 7, 2013 – BuddyPress 1.9 release
BuddyPress 1.8 “Di Fara” is now available: http://buddypress.org/2013/07/buddypress-1-8-di-fara/
Many, many thanks to the members of the dev community who have contributed to this release!
I’ve just completed a draft of the new codex page for
BP_Group_Extension, which has been rewritten for the upcoming BP 1.8 release. Here’s where it’s currently living: http://codex.buddypress.org/group-extension-api-1-8-draft/. After 1.8 is released, http://codex.buddypress.org/group-extension-api/ will be replaced with the new page, and the old content moved to its new home http://codex.buddypress.org/developer/plugin-development/group-extension-api-prior-to-bp-1-8/
If you’ve worked with
BP_Group_Extension before, please dive into this new documentation to make sure it makes sense from a dev’s point of view.
BP 1.8 Release Candidate 1 is available http://buddypress.org/2013/07/buddypress-1-8-release-candidate-1/
BuddyPress 1.8-beta2 is now available. Get testing!
I’ve just tagged BP 1.8-beta1. Read more about it: http://buddypress.org/2013/06/buddypress-1-8-beta1-is-now-available/
Watch this space for updates about new feature documentation within the upcoming days. And thanks to all for your help thus far during this dev cycle.