You are browsing the archive for developers.

BuddyPress Skeleton Component v1.6 is built for BuddyPress 1.5

September 29, 2011 in News

Are you (or do you aspire, from the bottom of your heart, to be) a BuddyPress plugin developer? For several years, the go-to template for building BP plugins has been the BuddyPress Skeleton Component, originally written by Andy Peatling and Jeff Sayre. Through time, the original BPSC has gotten a bit out-of-step with the current best practices for BuddyPress plugins. And with the recent release of BuddyPress 1.5 – with its new BP_Component class and a whole load of new goodies for plugin devs – the time was ripe for revisiting the Skeleton Component.

And so, available immediately is the brand new BuddyPress Skeleton Component, version 1.6! A quick overview of improvements:

  • Refactored to use the BuddyPress 1.5′s new BP_Component class, making it dead-simple to register globals, create navigation items, and hook into the BP load order
  • File structure reorganized to better reflect BP 1.5′s organization, and to provide more fine-grained access to functions
  • Data storage class totally refactored, to use custom post types and WP_Query, instead of custom database tables.
  • Added a small guide for creating a top-level component directory (a “root component”), which was missing in earlier versions
  • Tons of documentation added and revised
  • All WP_DEBUG notices removed

Please note that, due to its use of BP_Component class and other new features, plugins based on BPSC 1.6 will only work with BuddyPress 1.5 or greater. If you need to retain compatibility with earlier versions of BuddyPress, it’s recommended that you *first* build your plugin for the current version of BP, and then build the 1.2.x compatibility as an afterthought. See the “1.5 plugin update” series on bpdevel.wordpress.com and earlier versions of the Skeleton Component for more details on building plugins for BP < 1.5.

Questions, comments, or suggestions about the BuddyPress Skeleton Component? Check out the buddypress.org forums. You can also follow (and contribute to!) the plugin’s development here.

Introducing Marshall

April 7, 2010 in Community, News

For those of you who spend a bit of time interacting in the BuddyPress community, Marshall (MrMaz) will need no introduction.

Marshall is the developer of the BuddyPress Links plugin that adds rich media sharing to your BuddyPress install. If you’ve used it you’ll know it’s one of the most tightly integrated plugins available, interacting with the core BuddyPress components as though it’s actually one itself. He’s done a fantastic job and that’s one of the main reasons he’s now coming on board as the newest core BuddyPress developer.

Marshall will be focusing specifically on developing the BuddyPress API and making it easier for developers to seamlessly and efficiently integrate their plugins into the BuddyPress experience. He’ll be working his API wizardry for version 1.4 and onwards. In the meantime to ease himself in he’ll be helping JJJ and I out with outstanding tickets and patches for version 1.3.

Welcome aboard Marshall! We’re really looking forward to what you can do to continue to make BuddyPress one of the best social platforms around.

Doubling Up

October 30, 2009 in Community, News

I’d like to congratulate John James Jacoby (aka jjj) for doubling the size of the core development team and gaining commit access to the project!

BuddyPress is growing, and at a pace that just one core developer cannot possibly keep up with. I’ve been looking to expand the size of the core development team for a while now and I’m excited to be able to announce the first stop along that road.

If you’re a regular in the forums or trac you’ll already know who John is. He has been an unrelenting force for some time with quick responses to questions and quality core patches.

John will be helping with bug fixing to begin with, then looking to take on some of the new features listed on the roadmap. Congratulations again John, I’m very excited to have you on the core team.