The simplest way via wp-cli that comes to mind (while it’s not supported yet as far as I can see) is something like: wp eval “update_option( ‘auto_update_plugins’, array_keys( get_plugins() ) );” that will update the auto_update_plugins option with the array of all plugin files to update. This should probably be extended further to only update … Read more
It’s as if you were trying to run: wp plugin status –path=$(/home/me/domains/example.com/public_html) because what’s inside the backticks get’s evaluated. Here’s a good reading about using backticks in the command line. Let me quote @rozcietrzewiacz: Backtick is not a quotation sign, it has a very special meaning. Everything you type between backticks is evaluated (executed) by … Read more
Try the –skip-plugins flag with the problematic commands. Just as you experienced I’ve had wp-cli error out silently and do nothing, while frustratingly work for the simpler commands version/info commands. My silent errors were due to a bad plugin. This plugin was using php short tags, which weren’t enabled in php/x.x/cli/php.ini which wp-cli uses.
TL;DR: Run wp version –debug Check that wp-cli.yml was found Check that the ABSPATH set by WP-CLI matches the directory where WP is installed Look at find_wp_root() for hints about why it’s finding the wrong folder The docs say: inside the current working directory (or upwards) …so you should be able to use it in … Read more
Which version of WP-CLI are you using? What is wp –version returning you? Seems a little bit that you may be running out of memory as this is quite a large amount of images and there doesn’t seem some proper batch processing implemented in version 1 of WP-CLI. At least, that’s how I’d understand this … Read more
Your best bet to set up a reusable test environment on a Windows machine is to use Vagrant with a setup such as this. Vagrant will allow you to build portable, reusable virtual machines with a very simple interface which you can use across different operating systems and team members. To set it up, you … Read more
You could try to change it through the environment variable: WP_CLI_CACHE_DIR as we have it included in the WP_CLI::get_cache() method (src): $dir = getenv( ‘WP_CLI_CACHE_DIR’ ) ? : “$home/.wp-cli/cache”; You can also check out issue #1848 – Use shared cache directory for multiple installs for usage examples. In the WP-CLI Handbook on make.wordpress.org, we have … Read more
Since the issue is probably DB configuration you could try adjusting it conditionally in wp-config.php: if ( defined( ‘WP_CLI’ ) ) { define( ‘DB_HOST’, ‘example.com’ ); } else { define( ‘DB_HOST’, ‘localhost’ ); }
You can try this (untested) modification to the answer you linked to by @something wp post delete $(wp post list –post_type=”attachment” –format=ids –post_parent=0) to delete attachments without parents. To target a given mime type, e.g. image/jpeg try: wp post delete $(wp post list –post_type=”attachment” \ –format=ids –post_parent=0 –post_mime_type=”image/jpeg”) Notes: Remember to backup first before testing! … Read more
Not allowed by design: If we try to change the user login by the email: wp user update [email protected] –user_login=mary_new or by the user id: wp user update 123 –user_login=mary_new we get the following warning: User logins can’t be changed. This is the reason: if ( isset( $assoc_args[‘user_login’] ) ) { WP_CLI::warning( “User logins can’t … Read more