[S/O to @TomJNowell whose comments helped me track down the issue. Sharing in case it could help others troubleshoot a similar problem] In my setup, I’m using two Docker containers with different images: wordpress:4.9: wp container wordpesss:cli: wp-cli container In order to allow wp-cli container access to the WordPress config, files, etc., I configured them … Read more
According to Alain Schlesser in wordpress slack: The folder that the packages are installed into is set to use your server user’s home folder. When you try to execute this command from PHP, however, it is being executed by the webserver’s user, which probably has a different home folder, and the package is not installed … Read more
You can try a couple of things. WordPress has a built-in Importer/Exporter you can find under the Tools menu: The tool is a bit hit or miss, your mileage may vary. Alternatively, you can do the following: First, take backups of everything!! It sounds like you already have, but do it again, just in case. … Read more
WP CLI’s option update command only accepts one key per call, but you can use other commands to handle updating multiple keys in sequence. The command page in the Codex has some examples. # Update one option on multiple sites using xargs. $ wp site list –field=url | xargs -n1 -I {} sh -c ‘wp … Read more
The WP CLI aliases are mostly for context. WP CLI uses Drush as a source of inspiration, but Drush has a much more robust implementation of aliases. If it were me, I would include other scripts and complex logic as a custom command. WP_CLI::add_command( ‘core foo’, ‘Foo_Command’ );
See Cannot create a post with Latin characters in the title on Windows. Using UTF-8 in PHP arguments doesn’t work on Windows for PHP <= 7.0, however it will work for PHP >= 7.1, as it was fixed as part of Support for long and UTF-8 path. A workaround for PHP <= 7.0 is to … Read more
You can put the PHP anywhere in your plugin, or a file that’s included into your plugin, the same as you would any other code for extending any part of WordPress in a plugin. The only thing you need to do is check that WP_CLI exists before using any of the WP CLI API: if … Read more
You can try to get current structure first by run wp option get permalink_structure and then wp option update permalink_structure ‘/%postname%’ or wp rewrite structure ‘/%postname%’ with ‘/%postname%’ is the return result of the first command. Not sure if this help
WP CLI needs to know some things about the terminal it’s running in to format the table, aka the TTY. But when you pipe, there is no TTY! But you can trick it into thinking there is if you use this bash function: faketty() { 0</dev/null script –quiet –flush –return –command “$(printf “%q ” “$@”)” … Read more
Currently i have several process running in my CI/CD with wp-cli and all works fine in windows and unix. In my experience this is your best option in windows: #1 Add PHP to your Windows Path Variable #2 Install, as @Rup suggests, Git-bash terminal. #3 Execute an wp-cli command like that: vendor/bin/wp cache flush –path=public/wp-cms/wp-core … Read more