Shortly after BuddyPress 2.0 is released, we’re going to be updating BuddyPress’ development trunk (buddypress.svn.wordpress.org/trunk) to a Grunt-powered build system. Most people won’t even notice, but for developers and contributors, this means a small workflow change.
TL;DR – keep reading if:
- You develop plugins for BuddyPress
- You are a core contributor
- You run a checkout of trunk on a production site
In BuddyPress 2.0, one of the coolest things for developers is the
bp_parse_args() function. This function is copied over from our cousin, bbPress.
What this allows developers is the chance to filter various parameters before they are passed for further rendering.
I’ve just created a codex article explaining how to use
bp_parse_args() to filter BP’s template loops here:
If anyone has any questions about the codex article, please drop a comment below and I’ll try to answer it.
Now, go and read the codex and grab a slice of pizza!
BuddyPress 2.0 “Juliana” has been released: http://buddypress.org/2014/04/buddypress-2-0-juliana/
Special thanks to the readers of this blog who have helped with development and testing during this dev period. Go enjoy a slice of pizza!
BP 2.0 RC 1: http://buddypress.org/2014/04/buddypress-2-0-release-candidate/
BP 2.0-beta2 is now available: http://buddypress.org/2014/04/buddypress-2-0-beta2/
Happy #weekly-updates, everyone. If you haven’t read @karmatosed‘s posts on the state of the template pack, or @boonebgorges‘ performance improvement numbers, go do that. Both are must-reads.
Beta 2 will be arriving this week. If you’ve contributed to the project this last week, thanks so much — share here what you did. :)
As most know by now, the template pack isn’t going to be part of 2.0. Whilst this is a little sad, it’s for the best. It wasn’t ready and there is no point releasing something that isn’t going to be amazing.
That all said, the focus for the template pack should move onto 2.1. I’ve spent a bit of time thinking about this and plan on during April to do something a little different. I will personally work on a fork experimenting with some layouts and interfaces. I feel the project was the casualty of both taking a long time and momentum. I want to take stock and create a fork to play with ‘what could be’.
This will be a short time and will be an attempt to be more brave about this project. The aim is to push and come up with a solution for the navigation and other areas we had to settle for. It won’t be to commit it all, I will post what I create to get feedback and opinions. I think at this stage the project needs this singular focus and experimentation just for a few short weeks.
I will be doing this all on a Github branch called lab on the project here:
Perhaps one of the biggest areas that will need hands come the push into 2.1 will be the messages area. I am keen we work on the layout we dropped due to issues. I am optimistic with renewed strength and new development hands we can deal with this. I think this is something we shouldn’t settle for not doing.
Whilst it’s disheartening when we don’t reach a goal, I feel that this template pack will be stronger for this process. Those that have worked on it, thank you. Those that want to work on it for 2.1 – yay thank you and welcome.
As far as ‘what happens next’ goes. I think in a few weeks I will post a summary of my experimentation. We still have the Github project, that won’t go away. Anyone is welcome to work on anything there and test, refine in meantime. We will after that look at the next steps. I’m very keen we get this early into core during 2.1.