Happy release day! After 325 merged pull requests, we’re excited to bring you WP-CLI v1.2.0, chock full of enhancements, bug fixes… and a bootstrap refactor. But first… We have a new logo! Coming soon to a laptop near you: Thanks to Chris Wallace and the crew at Lift UX for their work, as well as…
WP-CLI welcomes its second maintainer, thanks to the support of our 2017 sponsors. New co-maintainer: Alain Schlesser First, I’d like to formally welcome Alain Schlesser as WP-CLI’s newest co-maintainer. If you’ve been following the project over the last month, you may have noticed him diving deep into WP-CLI’s internals.
Excited to experiment with a couple new WP-CLI commands? wp doctor and wp profile are now available for everyone to install. wp doctor lets you diagnose problems within WordPress by running a series of checks for symptoms. It includes an API for defining your own diagnosis, as well as writing custom checks.
wp plugin install rest-api –activate Installing WordPress REST API (Version 2) (2.0-beta13) Downloading install package from https://downloads.wordpress.org/plugin/rest-api.2.0-beta13.zip… Unpacking the package… Installing the plugin… Plugin installed successfully. Activating ‘rest-api’… Success: Plugin ‘rest-api’ activated.
The response to my tweet has been overwhelmingly supportive. One future I’m considering is directly commercializing WP-CLI, through patreon-esque membership, advertising on the website, and other ideas to be determined.
This release represents a level of maturity few open source projects achieve. It also marks a moment of transition. The WP-CLI project will shift its focus to the WP-CLI package ecosystem, where it will enable innovation by building and encouraging new features as standalone packages.
Helpful shortcuts for bash and zsh.
As I mentioned in my WordCamp Europe talk: Just like WordPress has plugins, the future of WP-CLI is packages of commands. For this future, I’m trying to proactively solve the problems WordPress has with plugins: Where WordPress plugins are considered second-class to what’s included in core, I’d like WP-CLI packages to be considered first-class citizens amongst the commands in WP-CLI.
Last November, I published a Kickstarter, and was completely blown away by the support. This month, the funding ran out, so I thought I’d post one last RESTful WP-CLI update. Actually, the story doesn’t end here. I’m writing a massive retrospective post about using Kickstarter to fund open source, so keep an eye out for that.
Docs ” GuidesQuick links: Anatomy of a command |Annotating with PHPDoc |Command internals |Writing tests |Add to the package index Creating your own custom WP-CLI command can be easier than it looks. WP-CLI’s goal is to offer a complete alternative to the WordPress admin; for any action you might want to perform in the WordPress admin, there should be an equivalent WP-CLI command.
Many thanks to the 206 (!!!) people who took our second user survey. We appreciate your time in helping us to understand how WP-CLI is being adopted by the community. Curious as to how the numbers have changed? Take a look at the summary of the first user survey from April 2014.
WordPress 4.4 loads a few new files even more files in wp-settings.php. Because WP-CLI has a custom wp-settings-cli.php ( background), WP-CLI v0.21.1 and v0.20.4 are compatibility releases to load these new files.
Even though WP-CLI is a mature project, we still manage to pack a great set of improvements into each release. Here’s what’s coming to you in v0.20.0. Use the –regex flag to wp search-replace to… wait for it… use regex in your search and replace operations.
Just in time for your crazy load of summer projects, we have a new version of WP-CLI for you. Here’s what’s new.