• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved wp-cli needs wp-cli-bundle

sturm

New Pleskian
I'm aware that wp-cli is a part of wp-toolkit and I'm glad that it's finally been updated to v2.4.0 as of this writing. However, a new problem has been introduced with this upgrade: Some commands have been removed.

To be more specific, some commands have been split off into a separate package, wp-cli-bundle. See this WP blog post for more information. So wp-cli is just the core functionality now. I can't speak for everyone, but many of us who use wp-cli need it for some of those commands, such as `media` for regenerating thumbnails or `package` to install packages.

Are there any plans to incorporate wp-cli-bundle into wp-toolkit and, if so, what's the timeline on it?
 
Hi @sturm,

This looks perfectly reasonable. I've filed an item in our issue tracker and I'll see when we can add that (hopefully it'll be soon).
 
You can just wget the phar and execute it. Add it to /bin for global access.
Are you sure this is possible with Plesk? Already we cannot use regular `wp`, we have to use the wp-toolkit command `sudo plesk ext wp-toolkit --wp-cli -instance-id [id] -- [command] [options]` instead. I don't even know the phar file of which you speak, nor how to execute it properly.

Hi @sturm,

This looks perfectly reasonable. I've filed an item in our issue tracker and I'll see when we can add that (hopefully it'll be soon).
Thanks, Custer. I look forward to hearing when it's been implemented.
 
Are you sure this is possible with Plesk? Already we cannot use regular `wp`, we have to use the wp-toolkit command `sudo plesk ext wp-toolkit --wp-cli -instance-id [id] -- [command] [options]` instead. I don't even know the phar file of which you speak, nor how to execute it properly.


Thanks, Custer. I look forward to hearing when it's been implemented.
Yes.

Run

Code:
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
chmod +x wp-cli.phar
mv wp-cli.phar /bin/wp
wp --info
 
Yes.

Run

Code:
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
chmod +x wp-cli.phar
mv wp-cli.phar /bin/wp
wp --info

Remember that Plesk allows you to have multiple subscriptions and multiple WordPress installations. So if I wanted to run a `wp` command on just one of them, how would I tell it which installation on which to run the command?
 
Remember that Plesk allows you to have multiple subscriptions and multiple WordPress installations. So if I wanted to run a `wp` command on just one of them, how would I tell it which installation on which to run the command?
wp will make you pass --path to the WordPress install
 
@sturm Good news -- wp-cli-bundle will be included in the shipped wp-cli distribution in the upcoming WordPress Toolkit v5.6 release (to be out soon).
 
Back
Top