Legacy Forums support will be…

Legacy Forums support will be removed with BuddyPress #3.0, due for release next year.
If your site is still using Legacy Forums, you will need to migrate to bbPress 2. Backwards compatibility will be ceased.
The last planned BuddyPress release that will support Legacy Forums is #2.9.3.

“Legacy Forums” is what we call the bundled version of bbPress 1 that has shipped with BuddyPress for over nine years. In fact, bundled or not, bbPress 1 only runs on WordPress versions older than 4.7, because a conflict between something called BackPress, which is nested inside bbPress 1, and the WP_Taxonomy class introduced in WordPress 4.7. So: if you’re using bbPress 1 today, you must be using an old version of WordPress, otherwise your site is broken.

This withdrawal of support is something that has been discussed for the last four years (see tickets 5351, 7502), and we feel now is the time. We will be including compatibility fixes for Legacy Forums with the upcoming BuddyPress 2.9.3 (date tbc) to help assist with any sites that are about to migrate to bbPress 2.

The removal of Legacy Forums from trunk will happen very soon.

BuddyPress 2018 Survey

What would you like BuddyPress to focus on in 2018? The core team has ideas of where BuddyPress can expand on and your input is important to harness the time and resources of an all-volunteer crew.

The survey will take 10-15 minutes to complete. Be assured that we will not publish your name, email address, nor IP address when we post the results of this survey at BuddyPress.org.

Thank you for your time and cooperation. Your feedback will help us improve BuddyPress for you.

=> Take the 2018 BuddyPress Survey

BuddyPress 3.0 Dev Cycle

Paul Gibbs is Release Lead for BP 3.0

Paul Gibbs Paul (twitter) is a BuddyPress Lead Developer, Senior WordPress Engineer at Human Made, master of memes extraordinaire, and lives in the UK. His latest project is WordHat, a Behat extension. When not working, Paul enjoys playing video and board games, and luxury travel. You can also find him at byotos.com and at github.com.

Following are a few of his plans for this dev cycle.

Nouveau Template Pack

The items listed below need to be resolved before we ship bp-nouveau and BP 3.0:
1. Review all the superglobals and JSON handlers and nonces, for security.
2. Review all i18n strings.
3. Review of custom SQL.

BuddyPress.org Redesign

Paul is also reviving the development of the site’s redesign. If you’d like to participate, get in contact with Paul on our Slack. The current code is at https://gitlab.com/paulgibbs/bporg and there’s a staging site at http://dev-bporg.pantheonsite.io

Dev Chats

In lieu of the weekly dev chats in Slack, Paul would be using this site for async contribution updates and explore other avenues for developer chats like video hangouts, etc. Expect an announcement soon.

Schedule of Release

BP 3.0 is expected to be released early in the first quarter of 2018. We won’t be following the 3- to 4-month scheduling as in the past BuddyPress releases. BP 3.0 will be a focused release, specifically introducing the new Nouveau template pack along with other bug fixes and enhancements along the way.

BuddyPress Case Studies

Thanks to all who have shared their BuddyPress use cases with the community! The list of published articles this year are available in the BuddyPress Codex for your reference. If you’re interested in sharing your own BuddyPress use case, fill up this form and we’ll get back to you ASAP.

#3-0, #dev-chat

Real-world testing of BuddyPress WP-CLI commands

A few years ago, I started a wp-cli-buddypress project. I occasionally added commands that were useful to me personally, but didn’t pretend to have anything close to complete coverage. A few months ago, Renato Alves (@espellcaste) contacted me to see whether he could help flesh out some of the missing commands. We moved the repo to the official BuddyPress GitHub account https://github.com/buddypress/wp-cli-buddypress, opened a BP ticket to track the potential integration of the commands into BP itself https://buddypress.trac.wordpress.org/ticket/7604, and got to work.

Since that time, Renato and I have done extensive work to bring basic CLI commands to all the main components of BuddyPress. Specifically, we have CRUD commands for all major content types, as well as a few helpful utility methods. The list of supported commands is too long to list here – you can explore by typing <code>wp bp</code> and digging down through the tree – but here’s a very brief summary:

  • activity – CRUD commands, comment management, favorite management, spam/unspam
  • core – Component activation and deactivation
  • group – CRUD commands, member listing and management, invitation management
  • member – bulk generation
  • signup – CRUD commands, activation, resending
  • tool – commands for running any BP repair tool
  • xprofile – CRUD commands for groups, fields, and user data

While there’s more to build – and refinements to be made – we’re at a point where we need real-world testing and feedback. If you are a BP developer, or administer BP-powered sites, and if you use WP-CLI, please install wp-cli-buddypress today and start using it.

There are numerous ways to install a wp-cli package, but because this one is in development, we encourage you to get a repo checkout. Something like:

$ git clone https://github.com/buddypress/wp-cli-buddypress ~/.wp-cli/commands

and then add the path to wp-cli-buddypress/wp-cli-bp.php to the commands subsection of your wp-cli config file https://make.wordpress.org/cli/handbook/config/#config-files.

Questions to consider while using the commands:

  • Are the commands named in a way that makes sense? Note that in some cases, commands have aliases (eg wp bp group create and wp bp group add).
  • Think about argument patterns across the commands, and whether they are consistent and make sense. Some commands take certain positional arguments (wp bp group get my-group) while others require named arguments (wp bp xprofile data get --user-id=5 --field-id=10)
  • What major features are missing?

For specific issues, you’re encouraged to open a GitHub ticket: https://github.com/buddypress/wp-cli-buddypress/issues. For high-level discussions, you can open a GitHub ticket, leave a comment here, or drop into the #buddypress channel on wordpress.org Slack.

And for the truly intrepid: Contributions are encouraged! We’ve worked hard to ensure 100% Behat test coverage, which makes writing new commands fun.

#wp-cli

BuddyPress 3.0 will require WordPress…

BuddyPress 3.0 will require WordPress 4.5 or greater. See https://buddypress.trac.wordpress.org/ticket/7618 and https://codex.buddypress.org/getting-started/wordpress-version-compatibility/.

BuddyPress 2.9.2 security and maintenance release

BP 2.9.2 is now available: https://buddypress.org/2017/11/buddypress-2-9-2-security-and-maintenance-release/

BudyPress 2.9.0 ‘La Lombarda’

We’re  happy to announce the launch & availability of it’s latest release 2.9 ‘La Lombarda’ available for download or updatable from your WordPress install plugin directory.

As always this release has been a huge team effort from both the core contributors and many new contributors with first time patches and we thank everyone for their time and effort put in to bring this release home.

I personally thank everyone for the support I’ve had as a first time release lead, an interesting experience. special thanks must go to @mercime for acting as release deputy, keeping the devchats abridged and posted on bpdevel and for the help on the first beta packaging run at an ungodly hour of the morning 🙂

A full changelog can be viewed here – Codex Changelog 2.9.0

Please report any issues to our Trac home

Happy updating!

hnla.

#2-9-0, #new-release