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
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’ ); }
It seems like Cygwin doesn’t support inline environment variables, like Bash does. Opened a ticket: https://github.com/wp-cli/wp-cli/issues/1086
If we restrict us to the output of wp post list, then here’s a way to search for %test% within the post titles of published posts: wp post list –ignore_sticky_posts=1 –post__in=$(wp db query ‘SELECT ID FROM wp_posts WHERE post_title LIKE “%test%” AND post_status=”publish” AND post_type=”post”‘ –skip-column-names | paste -s -d ‘,’ – ) Here’s the … Read more
Yes, there is! I didn’t find it at first, but wp cli offers a command called eval-file which does what you want: $ echo ‘<?php echo is_wp_error(“foo”) ? 1 : 0;’ > example.php $ wp eval-file example.php 0
WP-CLI now has native commands for it. # Activate Maintenance mode $ wp maintenance-mode activate # Deactivate Maintenance mode $ wp maintenance-mode deactivate See wp-cli/maintenance-mode-command for more information.
Go into your wp-config.php and change your DB_HOST to 127.0.0.1 instead of localhost. Credit goes to Craig Wayne above in the comments.