Would be great to have metadata commands: wp bp group meta update etc.

Hi @renatonascalves could you have a look to this https://buddypress.org/support/topic/buddypress-7-2-0/#post-317390 ?

Thanks 😊

This check is done all over the package. Let's remove them.

if ( ! $user ) { WP_CLI::error( sprintf( 'No user found by that username or ID (%s).', $i ) ); }

as titled.

Was just needing to look at some activity meta and realized we don't have a subcommand like wp bp activity meta.

I'll look into adding a PR for this, but if anyone can get to it sooner, that'd be awesome!

I'll be working on this.

Allow certain number of users to be created by.

wp bp member create --quantity=55

or

wp bp member generate --quantity=55

I'd suggest:

• wp bp friend list <user-id>, possibly with flags like --pending
• wp bp friend add <user-id-1> <user-id-2>, which would take some sort of arguments for skipping the invitation process
• wp bp friend check <user-id-1> <user-id-2> - I would call this "get" but "get" usually implies that the first argument will be an item ID, but the friendship ID is not really a useful ID in this context.
• wp bp friend delete, probably taking and but maybe with the option of passing a friendship ID
• wp bp friend accept-invitation <invitee-id> <inviter-id> - or something like that

as titled.

It can fail in the CI and it should not block the merge of pull requests unless there is no issue. =P

Update the --silent into a flag in all the commands.

I feel a generate command should be added for testing. I think it is very useful for me, and others, to populate the site with default information.

We could create a generate command for each component or a single generate command to install and populate default data.

I'd love some feedback on the necessity of this and how we could approach it. :)

https://buddypress.org/support/topic/deleting-records-in-wp_bp_notifications/

Here is a good scenario where the notification commands could be useful. I think I missed creating them. Let's do it.

When https://buddypress.trac.wordpress.org/ticket/7641 is merged, update BP_Signup::get removing the wp_list_pluck hack.

as titled.

Ideally, the CI matrix would test the same as BuddyPress, since the BP-REST and the WP GraphQL BuddyPress projects are trying to follow that.

wp bp group create --name=testgroup1 --creator-id=11
The default user (1) is used no matter matter what i put in creator-id=
If i change the code to use creator_id instead it seems to work.
I forked it to test example the changes:
https://github.com/corsacca/wp-cli-buddypress/commit/217f874c58c070cccf9f326c6ba456ed18b9821e

Mainly list the components to know which is active and which one is not.

I'm preparing a PR for this, but here follows the error:

wp bp core activate groups

Warning: require_once(/vagrant/www/bp-rest/htdocs/wp-content/plugins/buddypress//bp-core/admin/bp-core-schema.php): failed to open stream: No such file or directory in /home/vagrant/.wp-cli/packages/vendor/boonebgorges/wp-cli-buddypress/components/core.php on line 41

This file, https://github.com/boonebgorges/wp-cli-buddypress/blob/master/components/core.php#L41

bp-core-schema is called bp-core-admin-schema now.

Happens when I launch
wp bp --allow-root

The problem does not appear when not using "--allow-root".

On:
WP: 5.1.1
BP: 4.3.0

I'm getting this error message:

Fatal error: Class 'WP_CLI\CommandWithDBObject' not found in /Users/adriantoll/.wp-cli/packages/vendor/boonebgorges/wp-cli-buddypress/component.php on line 8

It seems to be with any wp command, so not strictly related to any wp bp commands.

I think it may be related to a brew upgrade that I ran recently, as wp-cli was upgraded, and the problem started occurring after that.

As a plugin developer I rely on wp scaffold plugin-tests a lot. I often end up customizing the scaffolded code to load BP along with WP for BP_UnitTestCase extensions. It would be great if I could scaffold a BP-specific test framework with a single command.

If you're willing to include this feature I'd like to help build it, but I wanted to ask in case it already exists or isn't something you think should be included for some reason.

An issue to keep track of this request from #3.

import/export tools would be the holy grail. See https://buddypress.trac.wordpress.org/ticket/408. This would be a huge project; building it for wp-cli-buddypress could be a way to test-drive a strategy for rolling the features into BP core

I'm using:

PHP 7.2.4
WP-CLI 1.5.0
BuddyPress 2.9.3
WordPress 4.9.2

I installed this package like this:

wp package install buddypress/wp-cli-buddypress

When I try to use a command that consists of more than two words e.g. bp group member I get an error:

Error: 'member' is not a registered subcommand of 'bp group'. See 'wp help bp group' for available subcommands.

I noticed that all three-word commands are affected. Just running wp bp only shows me two-word commands:

$ wp bp
usage: wp bp activity <command>
   or: wp bp component <command>
   or: wp bp email <command>
   or: wp bp friend <command>
   or: wp bp group <command>
   or: wp bp member <command>
   or: wp bp message <command>
   or: wp bp signup <command>
   or: wp bp tool <command>
   or: wp bp xprofile <command>

See 'wp help bp <command>' for more information on a specific command.

And the three-word commands are apparently not registered as subcommands since they're missing from this list as well:

$ wp bp group
usage: wp bp group create --name=<name> [--slug=<slug>] [--description=<description>] [--creator-id=<creator-id>] [--slug=<slug>] [--status=<status>] [--enable-forum=<enable-forum>] [--date-created=<date-created>] [--silent] [--porcelain]
   or: wp bp group delete <group-id>... [--yes]
   or: wp bp group generate [--count=<number>] [--status=<status>] [--creator-id=<creator-id>] [--enable-forum=<enable-forum>]
   or: wp bp group get <group-id> [--fields=<fields>] [--format=<format>]
   or: wp bp group list [--<field>=<value>] [--fields=<fields>] [--user-id=<user>] [--orderby=<orderby>] [--order=<order>] [--format=<format>] [--count=<number>]
   or: wp bp group update <group-id>... [--<field>=<value>]

See 'wp help bp group <command>' for more information on a specific command.

If I change the second word from group to something unique like groupp in wp-cli-bp.php then I can see & run the command as expected:

$ wp bp groupp
usage: wp bp groupp member <command>

See 'wp help bp groupp <command>' for more information on a specific command.

I also tried replacing the installed buddypress/wp-cli-buddypress package with a clone of the latest master branch and had the same problem.

While reviewing the recent code from wp-cli-buddypress, @boonebgorges suggested this would be a very good opportunity to use proper PSR-4 naming for CLI classes.

As wp-cli-buddypress probably will be merged into BP core in the near future, it would be used as a start, setting the example for the whole BP project to use PSR-4 as well.

Personally, I'm all for it! But we would like to open this discussion to gather more feedback or possible drawbacks.

So, fire away! :)

From my perspective, this is almost ready to go into BP core, but:

1. I'm unhappy about the random functions: get_random_user_id() get_random_group_id() get_random_login() generate_random_text(). I think WPCLI's "generate" dummy content functions are pretty weird.
   • Instead of get_random_user_id(), can we require the user to be specified via a required parameter, please?
   • For get_random_group_id(), can we make sure the random group is a public group? Can we use BP_Groups_Group::get_random( 1, 1 )?
   • For get_random_login(), why are we creating users? That's a WordPress thing? Can we avoid doing this entirely?
2. The Todo comments on get_random_login() and get_components_and_actions() need resolving.
3. When committed to BuddyPress, the class file names will have to match our conventions.
4. get_components_and_actions()
   • This should not be hardcoded. Is there not a function in BP core that returns this, or can we do something to parse it out of $bp if not?
5. Signups - create()
   • How about using the site domain instead of example.com for the email addresses?
6. How about we use namespaces for this?

We are using the latest version of BuddyPress, trunk.

Add a custom bp command.

https://buddypress.trac.wordpress.org/ticket/7885

#7623 was merged into BuddyPress. Now we can remove our custom function.

This is more of a question rather than a suggestion. If the goal is to add this package on BuddyPress core, do we need to internationalize the strings?

I'd say yes. What are your thoughts @boonebgorges?

Add support for managing notices.

Example: wp bp notices

In component.php:43, get_user_id_from_identifier($i) uses $i parameter to retrieve $user_id.

It doesn't however do anything with $user_id but returns intval($i).

Probably a bug?

The natural syntax (to me at least) seems like this:

wp bp activity list --user-id=5 - items with 5 as user_id
wp bp activity list --user-id=5 --component=groups - items with ( user_id = 5 && component = group )

There wouldn't be an OR syntax (though perhaps you could have comma syntax like --component=groups,activity for single params), but as an administrator, OR queries are less useful than AND drilldowns.

@renatonascalves What do you think of this idea and syntax?

Hi All,

I'm not sure if this is the right place to report this issue. If not, my humble apologies 😅 I'd happily repost it elsewhere 😃

When running the command wp bp member generate --count=1 I receive the following error with stacktrace:

$ wp bp member generate --count=1
PHP Fatal error:  Uncaught Error: Class 'Buddypress\CLI\Command\User_Command' not found in /srv/users/serverpilot/apps/bptester/public/wp-content/plugins/buddypress/cli/components/member.php:34
Stack trace:
#0 [internal function]: Buddypress\CLI\Command\Member->generate(Array, Array)
#1 phar:///opt/sp/bin/wp-cli.phar/php/WP_CLI/Dispatcher/CommandFactory.php(89): call_user_func(Array, Array, Array)
#2 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(Array, Array)
#3 phar:///opt/sp/bin/wp-cli.phar/php/WP_CLI/Dispatcher/Subcommand.php(425): call_user_func(Object(Closure), Array, Array)
#4 phar:///opt/sp/bin/wp-cli.phar/php/WP_CLI/Runner.php(353): WP_CLI\Dispatcher\Subcommand->invoke(Array, Array, Array)
#5 phar:///opt/sp/bin/wp-cli.phar/php/WP_CLI/Runner.php(376): WP_CLI\Runner->run_command(Array, Array)
#6 phar:///opt/sp/bin/wp-cli.phar/php/WP_CLI/Runner.php(1102): WP_CLI\Runner->_run_command_and_exit()
#7 phar:///opt/sp/bin/wp-cli.phar/php/WP_CLI/Bootstrap/LaunchRunner.php(23): WP_CLI\Runn in /srv/users/serverpilot/apps/bptester/public/wp-content/plugins/buddypress/cli/components/member.php on line 34
Fatal error: Uncaught Error: Class 'Buddypress\CLI\Command\User_Command' not found in /srv/users/serverpilot/apps/bptester/public/wp-content/plugins/buddypress/cli/components/member.php:34
Stack trace:
#0 [internal function]: Buddypress\CLI\Command\Member->generate(Array, Array)
#1 phar:///opt/sp/bin/wp-cli.phar/php/WP_CLI/Dispatcher/CommandFactory.php(89): call_user_func(Array, Array, Array)
#2 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(Array, Array)
#3 phar:///opt/sp/bin/wp-cli.phar/php/WP_CLI/Dispatcher/Subcommand.php(425): call_user_func(Object(Closure), Array, Array)
#4 phar:///opt/sp/bin/wp-cli.phar/php/WP_CLI/Runner.php(353): WP_CLI\Dispatcher\Subcommand->invoke(Array, Array, Array)
#5 phar:///opt/sp/bin/wp-cli.phar/php/WP_CLI/Runner.php(376): WP_CLI\Runner->run_command(Array, Array)
#6 phar:///opt/sp/bin/wp-cli.phar/php/WP_CLI/Runner.php(1102): WP_CLI\Runner->_run_command_and_exit()
#7 phar:///opt/sp/bin/wp-cli.phar/php/WP_CLI/Bootstrap/LaunchRunner.php(23): WP_CLI\Runn in /srv/users/serverpilot/apps/bptester/public/wp-content/plugins/buddypress/cli/components/member.php on line 34

Other commands like wp bp group generate --count=1 seem to be working just fine.

The stacktrace from above is from a server installed with Serverpilot. But the same error occurs in a server installed with Local by Flywheel.

Any ideas how to fix this? I'm kinda lost here. Thanks!

What about the messages commands? Any value in having commands such as:

wp bp message list --user_id=10

My suggestions:

• wp bp message add/create
• wp bp message delete
• wp bp message list
• wp bp message get
• wp bp message star
• wp bp message generate (for testing)

I'd be interested in attempting adding some functionality, but I don't know what you have in mind, if anything.

wp bp signup list shows only a single signup. This is because the default value for number in BP_Signup::get() is 1. This is confusing.

We should come up with some consistent conventions for default list counts, as well as the name of the parameter - BP goes between count, max, per_page, number, etc. How does WP-CLI do this?

For example, trying the command wp bp core activate settings results in this error message:

Fatal error: Uncaught Error: Call to undefined function dbDelta() in /Users/username-redacted/Sites/sitename-redacted/public/wp-content/plugins/buddypress/bp-core/admin/bp-core-admin-schema.php:159
Stack trace:
#0 /Users/username-redacted/Sites/sitename-redacted/public/wp-content/plugins/buddypress/bp-core/admin/bp-core-admin-schema.php(35): bp_core_install_activity_streams()
#1 /Users/username-redacted/.wp-cli/packages/vendor/boonebgorges/wp-cli-buddypress/components/core.php(46): bp_core_install(Array)
#2 [internal function]: BPCLI_Core->activate(Array, Array)
#3 /usr/local/Cellar/wp-cli/1.1.0/php/WP_CLI/Dispatcher/CommandFactory.php(67): call_user_func(Array, Array, Array)
#4 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(Array, Array)
#5 /usr/local/Cellar/wp-cli/1.1.0/php/WP_CLI/Dispatcher/Subcommand.php(390): call_user_func(Object(Closure), Array, Array)
#6 /usr/local/Cellar/wp-cli/1.1.0/php/WP_CLI/Runner.php(316): WP_CLI\Dispatcher\Subcommand->invoke(Array, Array, Array)
#7 /usr/local/Cellar/wp-cli/1.1.0/php/ in /Users/username-redacted/Sites/sitename-redacted/public/wp-content/plugins/buddypress/bp-core/admin/bp-core-admin-schema.php on line 159

Despite this, the component is successfully activated.

I'm on pretty much the latest version of all relevant packages, and have an up-to-date Homebrew environment:

WordPress 4.7.3
WP-CLI 1.1
wp-cli-buddypress 1.1.1
Apache 2.4.25
PHP 7.0.17
MySQL 5.7.17.

I noticed there is a bug in the wp bp component list command. The components are not returning correctly.

I'm adding this ticket so that I don't forget to fix it soon.

Hello Boone,

Is it possible to have an updated version of readme of your package?

I don't have the necessary rights to add this support. So if anyone with the rights could do that, that would be much appreciated. :)

More info: #53 (comment)

Functional tests are an integral ingredient of highly-quality, maintainable commands. WP-CLI tries to make it as easy as possible to add functional tests to your package with its wp scaffold package-tests command:

https://github.com/wp-cli/scaffold-package-command#wp-scaffold-package-tests

I'd encourage you to consider adding functional tests to your package :) By starting your functional tests early on, it also makes it much easier to maintain your project over time.

Hi Team Buddypress

There is small typo in readme.md
12: The wp-bli-buddypress wp-cli-buddypress comes installed

Regards
Hari Krishna

Currently bp group add_member triggers PHP errors, which stops script from execution.

Also it will be good do update get_user_id_from_identifier() to mimic WP_CLI user fetcher - https://github.com/wp-cli/wp-cli/blob/master/php/WP_CLI/Fetchers/User.php#L21. This method is used only in two commands groups and xprofile, where we need full user object.

I'll be working on this. For now, I'll add those fields below.

• Name
• E-mail

Most BP delete operations are irreversible, and some of them have cascading effects. For example, deleting a group also deletes group memberships, and may delete some group content depending on plugins. In these cases, I think it makes sense to require confirmation, which could then be bypassed with the --yes flag.

Despite what we say in the documentation.

Speaking as someone who has had to manage large BP installations, I've had to manually activate many signups. I even wrote a plugin for it https://wordpress.org/plugins/unconfirmed/ :) Yet rarely has the activation process started with a key. Usually the user reports her login or email address. It's only when doing development that I've had a need for a CLI command that activates by key.

Let's make this a bit more useful. I see two options. The easy one is to offer three assoc_args flags - activation-key, user-email, user-login - and require at least one of them. The harder one, which might be a bit more useful in the real world, is to have some sort of "fuzzy" logic like I built for signup get, so that you can say wp bp signup activate foo and it'll guess what you mean by 'foo'; an optional --field parameter would let you be more specific. This latter technique would probably benefit from a confirm step: "You are about to activate the following signup...".

@renatonascalves or others, do you have thoughts about what would be best here?