-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: 'jw-random' is not a registered wp command #19
Comments
Running into the same error, within docker. I don't have any error upon Installing 2.0 with Installing package JayWood/jw-wpcli-random-posts (2.0)
Updating /var/www/.wp-cli/packages/composer.json to require the package...
Using Composer to install the package...
---
Loading composer repositories with package information
Updating dependencies
Resolving dependencies through SAT
Looking at all rules.
Something's changed, looking at all rules again (pass #1)
Dependency resolution completed in 0.603 seconds
Analyzed 1530 packages to resolve dependencies
Analyzed 51336 rules to resolve dependencies
Package operations: 2 installs, 0 updates, 0 removals
Installs: fzaninotto/faker:v1.9.1, JayWood/jw-wpcli-random-posts:2.0
- Installing fzaninotto/faker (v1.9.1)
- Warning: JayWood/jw-wpcli-random-posts 2.0 requires fzaninotto/faker ^1.8 -> satisfiable by fzaninotto/faker[1.9.x-dev, v1.8.0, v1.9.0, v1.9.1].
- Installing JayWood/jw-wpcli-random-posts (2.0)
Writing lock file
Generating autoload files
---
Success: Package installed. |
Hello, Same error here !
Cheers |
Same for me:
|
Same here. Installing 2.0 yields Installing 1.4 works though. I'm using
Sorry I don't have time to dig in further than that right now... |
Hi,
The installation fails on my MacBook Pro (macOS 10.15.4). I use the following command to install:
wp package install jaywood/jw-wpcli-random-posts:dev-master
It ends with
Success
two PHP notices:The command doesn't register, too:
Error: 'jw-random' is not a registered wp command. See 'wp help' for available commands.
I've tried version 2, but it doesn't help. Any idea how to fix it without digging into wp-cli core files?
The text was updated successfully, but these errors were encountered: