WP-CLI is the official command line tool for interacting with and managing your WordPress sites.
Need help with something? Please review your available support options.
Want to help make it better? Check out our Contributing guide for an introduction, or “good first issues” for your first pull request.
X-comment from +make.wordpress.org/docs: Comment on We're applying to Season of Docs
X-comment from +make.wordpress.org/updates: Comment on WordCamp Europe 2020 Contributor Day Update
X-comment from +make.wordpress.org/updates: Comment on WCEU 2020 – Leave no Contributor Behind
Just in time for the release of WordPress Core 5.3.0 we have a new release of WP-CLI as well. A team of 37 contributors has collaborated to get 159 pull requests merged.
Let’s go over some of the noteworthy changes in this release. Most of the work went into compatibility fixes, so there’s not many new toys to play around with, unfortunately. As always, you can also skip directly to the detailed changelog if you prefer.
It should be obvious that WP-CLI supports the latest upcoming WordPress Core release, of course. However, there were quite a few changes that went into 5.3 that made it not only difficult to keep WP-CLI working across 5.3 and earlier versions at the same time, but also made it necessary to release WP-CLI in parallel to have a working option available.
The push to support more of the newer PHP features that became available due to the bump to the minimum PHP version of Core introduced changes to function signatures and class interfaces, which required a few adventurous fixes in some cases…
PHP 7.4 is not yet available in a stable release, but we’re slowly coming closer to the planned release date.
There have been quite a few fixes that went into WP-CLI to make sure it works correctly with PHP 7.4 once it’s available. It’s an ongoing process, still, as we’re working towards the first stable version. Tests are running for PHP 7.4 in the background as well for each package. These are still allowed to fail right now, but after this release, they will be switch to break on error.
The core download command now accepts a URL to download a specific ZIP archive with a version of Core to use. This also allows you to use your own custom version easily. Just add the URL and you’re good to go: wp core download https://somesite/build.zip
WP-CLI will properly deal with large images in the way that WP Core 5.3 was improved. It knows about the original source images as well so you can safely rebuild your thumbnails without losing quality.
hosting-companies.md file [#341]hosting-companies.md file [#336]hosting-companies.md file [#334]wp-completion.bash [#391]core download test [#136]core download [#135]install changed to installation [#132]site_id is 1 [#122]db clean get all the tables with prefix [#152]comment spam output [#272]--debug output for the file being processed. [#183]package.json [#225]@aommundsen, @azito122, @beaucollins, @burhandodhy, @connerbw, @derweili, @drzraf, @dz0ny, @felipeelia, @gitlost, @greatislander, @herregroen, @jrfnl, @l3ku, @localheinz, @marksabbath, @marty-crane, @maximejobin, @mcdwayne, @michaelzangl, @mustafauysal, @nxnjz, @nylen, @ocean90, @pdaalder, @raphael-concil, @sagarnasit, @schlessera, @siliconforks, @swissspidy, @tecking, @thrijith, @vladutilie, @wojsmol, @yousan, @zzap
Version 2.4.0 of WP-CLI will be released on Tuesday, November 12th, 2019, presumably around 15:00 UTC.
This places it in-between the release dry-run and the final release for WordPress Core 5.3, which is currently slated for November 12th at around 19:00 UTC.
Note: In case the scheduled release for WP 5.3 is adapted, we might also need to move the one for WP-CLI accordingly. In this case, I’ll send updates as needed.
There quite a few breaking “non-breaking changes” in the upcoming 5.3 release, and some of them have shown a weakness in the current packaging strategy regarding the framework package itself, which are the reason for this release to come on such short notice. Due to its very tight integration with Core, WP-CLI is very susceptible to these breaking changes, and the current packaging strategy does not always deal with this in the best way possible.
After 2.4.0, I will re-evaluate the current versioning policy regarding the framework package and how best to take interface changes in Core into account, that need us to modify signatures between Core versions to support.
We’re all looking forward to an awesome WordPress 5.3 release, so let’s make sure the ecosystem is ready for it! 👍
This release v2.3.0 is, as already announced, rather unspectacular. The previous release was very taxing for several reasons, so we lowered the pace for a while to recover.
This version is mainly meant to finally get a few bug fixes out there that were not critical enough to warrant an immediate hotfix release but are nice to have eradicated at one point, nevertheless.
Overall, a team of 36 contributors has collaborated to get 129 pull requests merged. I’ll briefly go over some of the more noteworthy stuff, but as always, you can also skip directly to the detailed changelog if you prefer.
Some cameras and smartphones will automatically tag pictures to denote “which way is up”. This means that you will have these devices show you the pictures you took during your handstand in the correct orientation no matter what, even though the actual picture file is upside down.
The media command now has a new subcommand media fix-orientation that reads these special tags and properly applies them to your images. This way, the images will also be shown with the correct orientation on devices that do not support this tag.
The --skip-tables flag for the search-replace command has learnt a new trick – it now lets you skip a group of tables in one go through wildcards.
You can use wildcards like 'wp_*options' or 'wp_post*' to make your life easier.
Up until now you always had to provide an anchor to attach changes to your wp-config.php to when using the config add command.
You can use this through the special anchor flag --anchor=EOF.
When you’re connecting to your vagrant VMs through WP-CLI’s special-case vagrant SSH connection scheme, you’ll notice that the operations are way faster now, as we’re caching the configuration across calls now.
php7.2-mysql and php7.3-mysql in Debian build [#130]parse_url scheme bug [#5241]vagrant ssh-config [#5235]File_Writer for STDOUT support [#60]load_export_api() public [#59]wp theme get command [#177]strpos(): Empty needle when going through include paths [#149]--skip-copy [#110]media fix-orientation command [#108]--skip-tables parameter [#124]@afragen, @ajoah, @blackfile, @connerbw, @drzraf, @felipeelia, @fernandoherlo, @fuegas, @fullsteamlabs, @gitlost, @greatislander, @herregroen, @hofmannsven, @jrfnl, @l3ku, @localheinz, @maximejobin, @michaelzangl, @MikeWKrystal, @mustafauysal, @ocean90, @ovidiul, @pdaalder, @sagarnasit, @schlessera, @shadyvb, @shashank3105, @siliconforks, @swissspidy, @szepeviktor, @tecking, @thrijith, @vladutilie, @wojsmol, @yognsk, @yousan
The WP-CLI release v2.3.0 needs to be postponed.
The code itself should reliably work right now. However, between Travis server connectivity issues and the Travis PHP environment not being able to connect to the wordpress.org servers, I have been unable to run successful tests over the resulting build (although all local tests pass without issues).
Next planned release date is Tuesday, August 13th. This gives me some time to work through the Travis curl issues and work on getting the project “into the green”.
Just a quick heads-up regarding the next release for WP-CLI.
WP-CLI v2.3.0 is scheduled to be released on August 7th, 2019, which is a Wednesday according to the calendar I’m looking at.
It will be a pretty unspectacular release, as I will mostly focus on tying up a few loose ends in that particular release and wanted to get a few bug fixes out into the wild.
Expect v2.4.0 (November-ish) to be more feature-rich again… 😊