Title: WP-CLI – Page 7 – The command line interface for WordPress --- [ ](https://profiles.wordpress.org/schlessera/) [Alain Schlesser](https://profiles.wordpress.org/schlessera/) 11:34 am _on_ October 31, 2018   # 󠀁[WP-CLI v2.1.0 release postponed](https://make.wordpress.org/cli/2018/10/31/wp-cli-v2-1-0-release-postponed/)󠁿 The **WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) v2.1.0** release was originally scheduled for _November 6th, 2018_. However, due to [the current timeline of the WordPress 5.0 release](https://make.wordpress.org/core/2018/10/31/wordpress-5-0-schedule-updates/) and the additional pressure it puts on all parties involved (WP-CLI contributors& testers included), I decided to postpone the release. The new planned release date will be **Tuesday, December 18th, 2018**. This will keep it away from the planned release date(s) of WordPress 5.0 and place it shortly after the contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of [https://make.wordpress.org/](https://make.wordpress.org/) There are many teams that people can participate in, each with a different focus. [https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/) at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. [Learn more](https://central.wordcamp.org/about/). US, allowing us to get bug fixes & improvements done that day into the release as well. For people who are waiting on getting their hands on the v2.1.0 release because of bugs in v2.0.1 that will be fixed, please note that you can always upgrade to the latest nightly release with the command `wp cli update --nightly` and switch back to stable releases later on with `wp cli update --stable`. * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcli%2F2018%2F10%2F31%2Fwp-cli-v2-1-0-release-postponed%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/schlessera/) [Alain Schlesser](https://profiles.wordpress.org/schlessera/) 1:40 am _on_ August 24, 2018 Tags: v2.0.1    # 󠀁[WP-CLI v2.0.1 Release Notes](https://make.wordpress.org/cli/2018/08/24/wp-cli-v2-0-1-release-notes/)󠁿 A bugfix release was in order, as the new `i18n make-pot` command was not properly packaged in v2.0.0! For this release, 9 contributors have produced 19 pull requests and squashed 12 bugs. ### Breaking change The only thing of note as a (potential) breaking change is “Throw error in theme fetcher on non-lowercase slugs” [[#126](https://github.com/wp-cli/extension-command/pull/126)]. It should turn scenarios that produce a success message and actually failed into error messages instead. However, given the many possible combinations of encodings and filesystem quirks, what should have failed might previously actually have worked out of sheer coincidence instead. This will now throw an error message nevertheless. ### Complete change log #### 󠀁[wp-cli/wp-cli-bundle](https://github.com/wp-cli/wp-cli-bundle/)󠁿 * Add i18n-command dependencies to make-phar [[#14](https://github.com/wp-cli/wp-cli-bundle/pull/14)] #### 󠀁[wp-cli/wp-cli](https://github.com/wp-cli/wp-cli/)󠁿 * Update dependencies and avoid redefining `WP_CLI_ROOT` [[#4918](https://github.com/wp-cli/wp-cli/pull/4918)] * Make `pick_fields()` work with numeric headers [[#4916](https://github.com/wp-cli/wp-cli/pull/4916)] * Automatically rerun failed scenarios [[#4906](https://github.com/wp-cli/wp-cli/pull/4906)] * Skip releases that lack a downloadable asset [[#4923](https://github.com/wp-cli/wp-cli/pull/4923)] #### 󠀁[wp-cli/config-command](https://github.com/wp-cli/config-command/)󠁿 * Permit use of `wp config edit` when WP isn’t functional [[#71](https://github.com/wp-cli/config-command/pull/71)] #### 󠀁[wp-cli/entity-command](https://github.com/wp-cli/entity-command/)󠁿 * Update readme [[#204](https://github.com/wp-cli/entity-command/pull/204)] * Automatically rerun failed scenarios [[#200](https://github.com/wp-cli/entity-command/pull/200)] #### 󠀁[wp-cli/extension-command](https://github.com/wp-cli/extension-command/)󠁿 * Throw error in theme fetcher on non-lowercase slugs [[#126](https://github.com/wp-cli/extension-command/pull/126)] * Raise timeout for HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. requests to 1 minute[ [#125](https://github.com/wp-cli/extension-command/pull/125)] * Automatically rerun failed scenarios [[#119](https://github.com/wp-cli/extension-command/pull/119)] #### 󠀁[wp-cli/i18n-command](https://github.com/wp-cli/i18n-command/)󠁿 * Require framework as hard dependency [[#78](https://github.com/wp-cli/i18n-command/pull/78)] * Add Composer config settings [[#74](https://github.com/wp-cli/i18n-command/pull/74)] #### 󠀁[wp-cli/language-command](https://github.com/wp-cli/language-command/)󠁿 * Make sure upgrader strings are always in English [[#54](https://github.com/wp-cli/language-command/pull/54)] * Slug fixes [[#53](https://github.com/wp-cli/language-command/pull/53)] * Automatically rerun failed scenarios [[#50](https://github.com/wp-cli/language-command/pull/50)] * Change access to `activate_language()`to `private` [[#47](https://github.com/wp-cli/language-command/pull/47)] #### 󠀁[wp-cli/scaffold-command](https://github.com/wp-cli/scaffold-command/)󠁿 * PHPCSPHP Code Sniffer [PHP Code Sniffer,](https://github.com/squizlabs/PHP_CodeSniffer) a popular tool for analyzing code quality. The [WordPress Coding Standards](https://github.com/WordPress/WordPress-Coding-Standards/) rely on PHPCS. template: fix XML error in ruleset [[#171](https://github.com/wp-cli/scaffold-command/pull/171)] * Automatically rerun failed scenarios [[#170](https://github.com/wp-cli/scaffold-command/pull/170)] ### Contributor List [@arunsathiya](https://github.com/arunsathiya), [@danielbachhuber](https://github.com/danielbachhuber), [@javorszky](https://github.com/javorszky), [@jrfnl](https://github.com/jrfnl), [@Mr-Alexander](https://github.com/Mr-Alexander), [@ocean90](https://github.com/ocean90), [@schlessera](https://github.com/schlessera), [@swissspidy](https://github.com/swissspidy), [@wojsmol](https://github.com/wojsmol) [#v2-0-1](https://make.wordpress.org/cli/tag/v2-0-1/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcli%2F2018%2F08%2F24%2Fwp-cli-v2-0-1-release-notes%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/schlessera/) [Alain Schlesser](https://profiles.wordpress.org/schlessera/) 9:19 pm _on_ August 8, 2018 Tags: [release ( 21 )](https://make.wordpress.org/cli/tag/release/), [v2.0.0 ( 2 )](https://make.wordpress.org/cli/tag/v2-0-0/)    # 󠀁[WP-CLI v2.0.0 Release Notes](https://make.wordpress.org/cli/2018/08/08/wp-cli-v2-0-0-release-notes/)󠁿 This is a big one! [**67 awesome contributors**](https://make.wordpress.org/cli/page/7/?output_format=md#contributors) have collaborated over [**364 pull requests**](https://make.wordpress.org/cli/page/7/?output_format=md#changelog) to bring you **WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) v2**! Before going over the [detailed change log](https://make.wordpress.org/cli/page/7/?output_format=md#changelog), let’s discuss a few key areas of this update in more detail. There’s also a [**“Breaking changes**](https://make.wordpress.org/cli/page/7/?output_format=md#breaking-changes)” further down in the document. ### “Framework” & “Bundle” are now two separate packages This is the main change we planned to include with version 2 of WP-CLI. From v2 onwards, the “framework” is a separate package from the “bundle” that is used to build the Phar file you can download. The framework is now contained within the [`wp-cli/wp-cli`](https://github.com/wp-cli/wp-cli) package, while the bundling has moved on to the [`wp-cli/wp-cli-bundle`](https://github.com/wp-cli/wp-cli-bundle). Agreed, this does not sound like such a big deal, but in terms of development experience and maintenance effort, it is a tremendous improvement, making almost every future change faster and simpler. #### What does that mean for users working with the Phar version of WP-CLI ? Nothing much, really. Apart from some of the debugging information containing different paths, you won’t see much of a difference. One of the goals was to not disrupt current usage more than necessary. If you only ever download the WP-CLI Phar and use that to control your sites, you should not need to care about this change. #### What does this mean for site owners using WP-CLI through Composer ? They will rejoice! The framework itself has gotten rid of most of its problematic dependencies. If you compare the [dependencies of v1.5.1](https://github.com/wp-cli/wp-cli/blob/v1.5.1/composer.json#L24-L66) with [those of v2.0.0](https://github.com/wp-cli/wp-cli/blob/v2.0.0/composer.json#L11-L17), you’ll see that the list is drastically shorter. Also, the most problematic set of the dependencies, the hard requirement on an old version of Symfony, is gone. The only Symfony component we still have (yet) is `symfony/finder`, as there’s no upper version limit for that one. Most of the more problematic dependencies actually came from the WP-CLI package manager (`wp-cli/package-command`). That command is not only optional now, there’s also no valid reason to use it at all when pulling WP-CLI in via Composer directly. This also means that you will not see WP-CLI automatically pull in all bundled commands automatically. Let’s say, you need the `wp-cli/db-command` for some maintenance tasks for your site. With v1.5.1, this would have pulled in the entire WP-CLI bundle as a dependency. With v2.0.0, it will only pull in the lean framework as a dependency, nothing more. You’ll end up with a WP-CLI active on your site that contains the commands `cli`, `help` (as the two “built-ins”) and `db`. ![](https://i0.wp.com/make.wordpress.org/cli/files/2018/08/Image-2018-08-08-at-7.03.54- PM.png?resize=776%2C676&ssl=1) As a nice side-benefit, this makes WP-CLI run much faster in such scenarios, as it only loads what is effectively needed for the site. The difference might not seem like much, but depending on how you use in in your scripts, it can make a big difference. ![](https://i0.wp.com/make.wordpress.org/cli/files/2018/08/Image-2018-08-08-at-7.16.20- PM.png?resize=776%2C64&ssl=1) #### What does this mean for developers working on third-party WP-CLI commands? Splitting everything up has provided a few additional perks for developers (see also the next section about the testing improvements). Everything is leaner, and the dependency resolutions are less problematic, as we got rid of that one nasty circular dependency (command requires framework => framework equals bundle => bundle requires command). However, dependency declarations need to be more explicit now. If you `require wp- cli/wp-cli`, this will only provide the pure framework. You cannot implicitly rely on any of the bundled commands in that case, you’ll have to explicitly `require` any additional command you might need. ### Testing framework is now a separate package One of the things that bothered me a lot while maintaining WP-CLI was the fact that the testing infrastructure was “scaffolded” into the individual command packages( just as it is into the third-party commands). This basically means that we copy- pasted the code in there, and if the code needs to change (because of a bug being fixed or an improvement being made), we have to create changes in every single package to overwrite the copy-pasted version of the testing code with an updated one. Now we have the testing infrastructure abstracted away into a separate package: [`wp-cli/wp-cli-tests`](https://github.com/wp-cli/wp-cli-tests). For this first iteration, it includes out-of-the-box support for PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. [https://www.php.net/manual/en/index.php](https://www.php.net/manual/en/index.php) linting, PHP Code SnifferPHP Code Sniffer [PHP Code Sniffer,](https://github.com/squizlabs/PHP_CodeSniffer) a popular tool for analyzing code quality. The [WordPress Coding Standards](https://github.com/WordPress/WordPress-Coding-Standards/) rely on PHPCS. checks (including the WordPress Coding StandardsWordPress Coding Standards The Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress [Coding Standards Handbook](https://developer.wordpress.org/coding-standards/). May also refer to [The collection of PHP_CodeSniffer rules](https://github.com/WordPress/WordPress-Coding-Standards/)( sniffs) used to format and validate PHP code developed for WordPress according to the PHP coding standards. and the PHP Compatibility Checks), PHPUnit unit tests and Behat functional tests. They are set up in such a way that they detect whether they should run, based on config files or test files presence. A simple `composer test` will run all of the tests in order. But you can also run them individually, through `composer lint|phpcs|phpunit|behat`. Adding further configuration flags can be done as well, but you need to remember to prepend them with a double- dash ( `--`) first, otherwise the arguments will be interpreted by Composer itself. For the most important tests, the functional Behat tests, you can also define some constants to adapt the environment in which to test. For example, testing against a specific version of WordPress can be done by providing the `WP_VERSION` constant:` WP_VERSION=4.2 composer behat`. This constant also understands `latest` and `trunk` correctly. In general, the tests are set up in such a way that you’ll face less differences between what you get locally and what you’ll get inside of the Travis CI checks. And given that the tests can now be worked on in one central location, we’re already thinking about what our next steps are to further improve them, like letting you [easily re-run only the failed scenarios from last run](https://github.com/wp-cli/wp-cli-tests/issues/12) or [automatically retrying failures on Travis](https://github.com/wp-cli/wp-cli-tests/issues/13) to make sure it was not a random intermittent timeout or similar. ### New command: `i18n make-pot` [@swissspidy](https://github.com/swissspidy) has spent countless hours working on a new command that has now finally made it into the official WP-CLI bundle. We now introduce you to the `i18n` command family and its first usable subcommand, `i18n make-pot`. What started out as an exploration at first is now a robust tool that is [already being used in production systems](https://github.com/wearerequired/traduttore) and is even [planned to replace the default translation tool bundled with WordPress Core](https://meta.trac.wordpress.org/ticket/3748). It supports both PHP and JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. [https://www.javascript.com](https://www.javascript.com/), can manipulate and put into shape multiple files and even detected bugs in the original CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tooling. This can now easily be including in whatever automated tooling you use for your site/pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress. org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party./theme development, and should make your translation work much smoother. Here’s a quick rundown of the main features: * Automatically detects plugins and themes and extracts file headers. * Allows extraction of only a specific text domain. * Supports JavaScript string extraction, even for JSX and ESNext. * Allows merging the resulting POT file with an existing one, e.g. one created by Babel. * Powerful rules to include/exclude specific directories (minified JS files, vendor,. git folder, etc.). * Supports extracting strings from WordPress core the same way it’s done today with 4 different projects. See [https://github.com/wp-cli/i18n-command/pull/69](https://github.com/wp-cli/i18n-command/pull/69) for examples. * Can warn about strings with wrong placeholders, as well as misleading or missing translator comments. This could be very useful for core but also plugin/developers to improve polyglots UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it.. A big shoutout to [@swissspidy](https://github.com/swissspidy) for the fabulous work he did on that command! ### Minor Framework enhancements #### New WordPress action: `'cli_init'` We introduced a new action `'cli_init'` that will be triggered by WP-CLI during the `'plugins_loaded'` action. This can be used as a conditional trigger for loading WP_CLI specific code, in case you don’t want to use the constants we already provide, for whatever reason. This being a WordPress action, it adds a bit more flexibility to the process of loading a WP-CLI command, like for example one plugin being able to unhook the commands of another plugin. #### New command: `config edit` Easily open your `wp-config.php` in your favorite editor (configured through the` EDITOR` environment variable). Once you save within that editor, the `wp-config. php` will be correctly updated. **Note**: This works through SSHSSH Secure SHell - a protocol for securely connecting to a remote system in addition to or in place of a password./vagrant/docker tunnels as well, but keep in mind that it will use the `EDITOR` of the remote system, which should be something like vim (=> “[how to exit the vim editor](https://stackoverflow.com/questions/11828270/how-to-exit-the-vim-editor)” 😉). ``` # Launch system editor to edit wp-config.php file $ wp config edit # Edit wp-config.php file in a specific editor $ EDITOR=vim wp config edit ``` #### New command: `config shuffle-salts` This refreshes the salts stored in your `wp-config.php` file, which are cryptographic values used for authentication and other security-related functionality. Regulary refreshing these salts could be considered “security hygiene” for a site. The command will generate the salts locally if your PHP server environment is cryptographically secure enough to do so, and falls back to the remote wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. endpoint if not. ``` # Get new salts for your wp-config.php file $ wp config shuffle-salts Success: Shuffled the salt keys. ``` #### New command: `db columns` Get a tabular view of the table schema for a given table. It shows you how the individual columns of the table have been defined, which default values they use and what extra functionality might be attached to them. ``` $ wp db columns wp_posts +-----------------------+---------------------+------+-----+---------------------+----------------+ | Field | Type | Null | Key | Default | Extra | +-----------------------+---------------------+------+-----+---------------------+----------------+ | ID | bigint(20) unsigned | NO | PRI | | auto_increment | | post_author | bigint(20) unsigned | NO | MUL | 0 | | | post_date | datetime | NO | | 0000-00-00 00:00:00 | | | post_date_gmt | datetime | NO | | 0000-00-00 00:00:00 | | | post_content | longtext | NO | | | | | post_title | text | NO | | | | | post_excerpt | text | NO | | | | | post_status | varchar(20) | NO | | publish | | | comment_status | varchar(20) | NO | | open | | | ping_status | varchar(20) | NO | | open | | | post_password | varchar(255) | NO | | | | | post_name | varchar(200) | NO | MUL | | | | to_ping | text | NO | | | | | pinged | text | NO | | | | | post_modified | datetime | NO | | 0000-00-00 00:00:00 | | | post_modified_gmt | datetime | NO | | 0000-00-00 00:00:00 | | | post_content_filtered | longtext | NO | | | | | post_parent | bigint(20) unsigned | NO | MUL | 0 | | | guid | varchar(255) | NO | | | | | menu_order | int(11) | NO | | 0 | | | post_type | varchar(20) | NO | MUL | post | | | post_mime_type | varchar(100) | NO | | | | | comment_count | bigint(20) | NO | | 0 | | +-----------------------+---------------------+------+-----+---------------------+----------------+ ``` #### New command: `db clean` We already had `db reset`, but that dropped the entire database… which is not a nice thing to do if there’s more than a default WordPress site in there 😱! The new `db clean` will only drop the tables that are actually part of the current WordPress installation and leave the rest of the database instance intact. ``` # Delete all tables that match the current site prefix. $ wp db clean --yes Success: Tables dropped. ``` #### New command: `site meta` We’ve added CRUD methods `add`, `delete`, `get`, `list`, `patch`, `pluck` and `update` for the “site metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.” entities. Oh, and while you are wondering… Yes, you are right, WordPress does not have “site meta” entities. But we didn’t lose our minds: WordPress will introduce “site meta”, together with a `wp_site_meta` table, with its 5.0 version. We just like to be prepared, that’s all… 😜 ``` # Set site meta $ wp site meta set 123 bio "Mary is a WordPress developer." Success: Updated custom field 'bio'. # Get site meta $ wp site meta get 123 bio Mary is a WordPress developer. # Update site meta $ wp site meta update 123 bio "Mary is an awesome WordPress developer." Success: Updated custom field 'bio'. # Delete site meta $ wp site meta delete 123 bio Success: Deleted custom field. ``` #### New command: `user check-password` You can now let WordPress tell you whether a given password is valid for a specific user. This is NOT an endorsement to build your authentication layer with Bash scripts! But who knows what exotic automation needs the DevOps folks will come up with… The command will let you know through a shell exit code whether the password was valid or not, so you can use it directly in `if` conditionals. ``` # Check whether given credentials are valid; exit status 0 if valid, otherwise 1 $ wp user check-password admin adminpass $ echo $? 1 # Bash script for checking whether given credentials are valid or not if ! $(wp user check-password $USER $PASSWORD); then notify-send "Invalid Credentials"; fi ``` #### New commands: `language plugin` and `language theme` They both come with the following subcommands: `install`, `update`, `uninstall`,` list` and `is-installed` (which was added to `core language` as well). You can now fully control all of the language files of your installation individually. ``` # Install the Dutch theme language pack. $ wp language plugin install hello-dolly nl_NL Success: Language installed. # Uninstall the Dutch theme language pack. $ wp language plugin uninstall hello-dolly nl_NL Success: Language uninstalled. # List installed theme language packages. $ wp language plugin list --status=installed +----------+--------------+-------------+-----------+-----------+---------------------+ | language | english_name | native_name | status | update | updated | +----------+--------------+-------------+-----------+-----------+---------------------+ | nl_NL | Dutch | Nederlands | installed | available | 2016-05-13 08:12:50 | +----------+--------------+-------------+-----------+-----------+---------------------+ ``` #### Changes to existing command * `db size` now knows about ISO size units as well * `option list` got a new `--unserialize` flag * `post generate` can now deal with `--post_date_gmt` * `user update` now allows you to `--skip-email` * `eval-file` can read from `STDIN` * Both `plugin uninstall` and `plugin delete` can now act on `--all` plugins at once * `cap list` can now `--show-grant` * `cap add` , seeing what its list sibling had done, grew a new `--grant` flag * `role list` can now print a single `--field=` * `scaffold _s` learned the new `--woocommerce` trick * `search-replace` lets you set a `--regex-limit` #### Automated README.md updates If you have ever contributed to WP-CLI and made a change to a command signature or documentation, you probably had me tell you that you needed to regenerate the` README.md` as well using the `wp scaffold package-readme . --force` command. No more! We have now added a package `wp-cli/regenerate-readme` that automates this process. It adds both a `precommit` and a `postcommit` git hook that collaborate to transparently regenerate the `README.md` file behind the scenes and then amend your commit to add the required changes automatically. This has not been deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. to all command packages yet while we still experiment with some of the finer points of its implementation, but you’ll slowly see the annoying “please regenerate README.md kthxbye” reminders from my side disappear and become forgotten artifacts of the past. #### Improved debug output The debug output was always a bit sparse for WP-CLI. This is why we took the opportunity of v2 to improve upon it and make it more useful. It will now add debug messages for the hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. that are triggered, or details about how commands are being loaded or deferred. This will be very useful for third-party command developers that ignore why their command is not properly registered. We’ll make sure to add even more useful debugging information in the future. ![](https://i0.wp.com/make.wordpress.org/cli/files/2018/08/Image-2018-08-08-at-8.03.22- PM.png?resize=776%2C398&ssl=1) _Small side note:_ To make debugging work as early as possible, it is now smart enough to just store all messages until the logger it needs to send them to becomes available. This means you don’t need to worry about the timing here, if the `WP_CLI` exits for your code, the debugger is good to go! ### Breaking changes Here are a few things you need to be aware of when moving from `^v1` to `^v2`: * An obvious breaking change is the bump to the minimum version of PHP. This will break for anyone trying to run WP-CLI on PHP 5.3. * The separation of the “framework” and the “bundle” into two separate packages will cause a breaking change if a third-party command is being pulled-in via Composer AND that third-party command relies on running bundled commands as well. This will seldom be the case and will be an easy fix. Installations using the Phar will not be impacted. * As many dependencies could be removed from the framework by not including the package manager automatically, any third-party command that relies on one of the removed Symfony packages or other dependencies AND hasn’t declared that requirement in its own Composer configuration will break. This will seldom be the case and will be an easy fix. Installations using the Phar will not be impacted as the package manager still comes with these requirements included. * The versions of some the dependencies will be bumped. If you happen to not lock WP-CLI into a specific version constraint, but do so for some of its dependencies, you might see a version constraint conflict when using Composer. * Any external code that relies on internal file structure, file naming or other internal details that are not part of the provided API could run the risk of breaking due to us moving things around from v1 to v2. This should hopefully not ever be the case, but you never know… * As a side-effect of adding the `--all` flag to `plugin uninstall`, a breaking change was introduced for consistency reasons. Whereas WP-CLI used to consider uninstalling a non-existent plugin as a “Success: Plugin already uninstalled”, it will now throw an error “Error: No plugin uninstalled”. * We did our best to avoid unnecessary breaking changes. But with a big structural change like we have here, the devil’s in the details. Let us know if you hit any other issues! ### Complete change log #### 󠀁[wp-cli/wp-cli-bundle](https://github.com/wp-cli/wp-cli-bundle/)󠁿 * Bundle `wp-cli/i18n-command` [[#9](https://github.com/wp-cli/wp-cli-bundle/pull/9)] #### 󠀁[wp-cli/wp-cli](https://github.com/wp-cli/wp-cli/)󠁿 * Add Inflector class and convenience function for pluralizing nouns [[#4881](https://github.com/wp-cli/wp-cli/pull/4881)] * Adapt regular expression in `make-phar` test to skip wiki links [[#4873](https://github.com/wp-cli/wp-cli/pull/4873)] * PHPCSPHP Code Sniffer [PHP Code Sniffer,](https://github.com/squizlabs/PHP_CodeSniffer) a popular tool for analyzing code quality. The [WordPress Coding Standards](https://github.com/WordPress/WordPress-Coding-Standards/) rely on PHPCS. Config Refresh [[#4867](https://github.com/wp-cli/wp-cli/pull/4867)] * Fix PHP version check [[#4864](https://github.com/wp-cli/wp-cli/pull/4864)] * Trigger new `'cli_init'` hook during WordPress `'plugins_loaded'` action. [[#4861](https://github.com/wp-cli/wp-cli/pull/4861)] * add template for core-command to phar [[#4854](https://github.com/wp-cli/wp-cli/pull/4854)] * Fall back to full string instead of $mode on PHP < 7 [[#4853](https://github.com/wp-cli/wp-cli/pull/4853)] * Refactoring `wp-cli/wp-cli` to represent the framework only, not the bundle [ [#4851](https://github.com/wp-cli/wp-cli/pull/4851)] * Remove WP 4.4 requirement [[#4845](https://github.com/wp-cli/wp-cli/pull/4845)] * Fix `—skip-theme` tests [[#4843](https://github.com/wp-cli/wp-cli/pull/4843)] * Fix shell scripting issues in `ci/deploy.sh` [[#4842](https://github.com/wp-cli/wp-cli/pull/4842)] * Fix shell scripting issues in `bin/wp` [[#4841](https://github.com/wp-cli/wp-cli/pull/4841)] * Additional quoting in `ci/prepare.sh` [[#4840](https://github.com/wp-cli/wp-cli/pull/4840)] * Lock `wp-completion.bash` to v1.5.1 [[#4839](https://github.com/wp-cli/wp-cli/pull/4839)] * Remove Gemnasium badge, as the service was shut down [[#4815](https://github.com/wp-cli/wp-cli/pull/4815)] * Use latest `search-replace` package to fix tests broken due to privacy policy change [[#4807](https://github.com/wp-cli/wp-cli/pull/4807)] * Turn `'latest'` into version number [[#4806](https://github.com/wp-cli/wp-cli/pull/4806)] * Update packages to fix broken tests due to WP5.0 [[#4804](https://github.com/wp-cli/wp-cli/pull/4804)] * Switch to fixed package command [[#4803](https://github.com/wp-cli/wp-cli/pull/4803)] * Bump lowest PHP version to test to 5.4 [[#4798](https://github.com/wp-cli/wp-cli/pull/4798)] * Add a missing accepted output format to `wp cli alias` [[#4765](https://github.com/wp-cli/wp-cli/pull/4765)] * Improve the descriptions of the `--skip-plugins` and `--skip-themes` flags [[#4759](https://github.com/wp-cli/wp-cli/pull/4759)] * Include sublinks in `README.md` to popular installation methods [[#4756](https://github.com/wp-cli/wp-cli/pull/4756)] * `ABSPATH` defined [[#4743](https://github.com/wp-cli/wp-cli/pull/4743)] * Skip `wp_blogmeta` table for back compat [[#4736](https://github.com/wp-cli/wp-cli/pull/4736)] * Introduce `\WP_CLI\Utils\normalize_path` function. Using it for `ABSPATH` constant.[ [#4718](https://github.com/wp-cli/wp-cli/pull/4718)] * Undo temporary one-off `@require-php-5.4` in bootstrap test. [[#4716](https://github.com/wp-cli/wp-cli/pull/4716)] * Revert “Require minimum PHP 5.4” [[#4715](https://github.com/wp-cli/wp-cli/pull/4715)] * Skip `pre-commit` hook in `auto-composer-update` [[#4711](https://github.com/wp-cli/wp-cli/pull/4711)] * Revert “update `wp cli info`” [[#4702](https://github.com/wp-cli/wp-cli/pull/4702)] * Remove `:` from cli update info check. [[#4697](https://github.com/wp-cli/wp-cli/pull/4697)] * Only check staged files during the `pre-commit` PHPCS verification [[#4696](https://github.com/wp-cli/wp-cli/pull/4696)] * Empty domain in framework test after `get_sites_by_path` change. [[#4695](https://github.com/wp-cli/wp-cli/pull/4695)] * Append `uniq_id()` when extracting file from Phar [[#4692](https://github.com/wp-cli/wp-cli/pull/4692)] * Support launching system editor with specific temp file extension [[#4691](https://github.com/wp-cli/wp-cli/pull/4691)] * Script to create the GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. [https://git-scm.com/](https://git-scm.com/)` pre-commit` hook. [[#4622](https://github.com/wp-cli/wp-cli/pull/4622)] * Update `wp cli info` [[#4613](https://github.com/wp-cli/wp-cli/pull/4613)] #### 󠀁[wp-cli/handbook](https://github.com/wp-cli/handbook/)󠁿 * Add documentation on how to troubleshoot [[#243](https://github.com/wp-cli/handbook/pull/243)] * Use as placeholder [[#242](https://github.com/wp-cli/handbook/pull/242)] * Fix typos in [[#239](https://github.com/wp-cli/handbook/pull/239)]&[ [#241](https://github.com/wp-cli/handbook/pull/241)] * Remove Dead Link [[#238](https://github.com/wp-cli/handbook/pull/238)] * Update docs for installing WP-CLI via `brew` [[#236](https://github.com/wp-cli/handbook/pull/236)] * Add quotes to the alias [[#235](https://github.com/wp-cli/handbook/pull/235)] * Adapt signing procedure to use proper key [[#232](https://github.com/wp-cli/handbook/pull/232)] * Added the `optimize` WP CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. command of the WP-Optimize Plugin [[#231](https://github.com/wp-cli/handbook/pull/231)] * Add an `updraftplus` WP CLI command [[#228](https://github.com/wp-cli/handbook/pull/228)] * Fix grammar in documentation paragraph [[#226](https://github.com/wp-cli/handbook/pull/226)] * Add a `LICENSE` file to the repo [[#224](https://github.com/wp-cli/handbook/pull/224)] * Incorporate a few strategic mentions of the `wp-cli/ideas` repo [[#223](https://github.com/wp-cli/handbook/pull/223)] * Remove the wish list from the website [[#222](https://github.com/wp-cli/handbook/pull/222)] * Document `WP_CLI_PHP_ARGS` in WP-CLI config document [[#221](https://github.com/wp-cli/handbook/pull/221)] * Mention the Docker installing method [[#220](https://github.com/wp-cli/handbook/pull/220)] * Document issue of creating a post with Latin characters in title [[#214](https://github.com/wp-cli/handbook/pull/214)] * Add BOM in `wp-config.php` as a common issue. [[#212](https://github.com/wp-cli/handbook/pull/212)] * Add `WP_CLI_PHP` to Environment variables [[#211](https://github.com/wp-cli/handbook/pull/211)] * Fix missing quote in documentation [[#210](https://github.com/wp-cli/handbook/pull/210)] * Separate non-bundled install; generate against current WP-CLI instance. [[#207](https://github.com/wp-cli/handbook/pull/207)] * Update Daniel’s relationship to the project [[#206](https://github.com/wp-cli/handbook/pull/206)] #### 󠀁[wp-cli/wp-cli.github.com](https://github.com/wp-cli/wp-cli.github.com/)󠁿 * Updated for Spanish language [[#313](https://github.com/wp-cli/wp-cli.github.com/pull/313)] * Remove Gemnasium badge [[#312](https://github.com/wp-cli/wp-cli.github.com/pull/312)] * Update `pt_BR` translation [[#311](https://github.com/wp-cli/wp-cli.github.com/pull/311)] * Add a `LICENSE` file to the repo [[#309](https://github.com/wp-cli/wp-cli.github.com/pull/309)] * Add note about only using the English version as source for translations [[#308](https://github.com/wp-cli/wp-cli.github.com/pull/308)] * Translate homepage into Spanish [[#307](https://github.com/wp-cli/wp-cli.github.com/pull/307)] * Changed `http` to `https` in all `wp-cli.org` links. [[#305](https://github.com/wp-cli/wp-cli.github.com/pull/305)] #### 󠀁[wp-cli/autoload-splitter](https://github.com/wp-cli/autoload-splitter/)󠁿 * _Package is now obsolete as of v2.0.0_ #### 󠀁[wp-cli/cache-command](https://github.com/wp-cli/cache-command/)󠁿 * Adapt package for framework v2 [[#32](https://github.com/wp-cli/cache-command/pull/32)] #### 󠀁[wp-cli/checksum-command](https://github.com/wp-cli/checksum-command/)󠁿 * Make soft changes more flexible for plugin checksums [[#43](https://github.com/wp-cli/checksum-command/pull/43)] * More flexible soft change checks (issue #34) [[#41](https://github.com/wp-cli/checksum-command/pull/41)] * Add backslash to the regex for matching Windows paths correctly [[#39](https://github.com/wp-cli/checksum-command/pull/39)] * Scaffold correct GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/) labels [[#37](https://github.com/wp-cli/checksum-command/pull/37)] * Adapt package for framework v2 [[#50](https://github.com/wp-cli/checksum-command/pull/50)] #### 󠀁[wp-cli/config-command](https://github.com/wp-cli/config-command/)󠁿 * Fix library version to `^1.2.1` [[#53](https://github.com/wp-cli/config-command/pull/53)] * Removed leftover `remove()` operation [[#52](https://github.com/wp-cli/config-command/pull/52)] * Introduce `config edit` command [[#48](https://github.com/wp-cli/config-command/pull/48)] * Add higher timeout config value [[#67](https://github.com/wp-cli/config-command/pull/67)] * Adapt package for framework v2 [[#66](https://github.com/wp-cli/config-command/pull/66)] * Ensure `file_put_contents()` writes to the `wp-config.php` path [[#63](https://github.com/wp-cli/config-command/pull/63)] * Add `shuffle-salts` command [[#62](https://github.com/wp-cli/config-command/pull/62)] * Set `WP_CACHE_KEY_SALT` [[#59](https://github.com/wp-cli/config-command/pull/59)] #### 󠀁[wp-cli/core-command](https://github.com/wp-cli/core-command/)󠁿 * Bring template files over from `wp-cli/wp-cli` [[#73](https://github.com/wp-cli/core-command/pull/73)] * Fix mustache template file path [[#77](https://github.com/wp-cli/core-command/pull/77)]&[ [#78](https://github.com/wp-cli/core-command/pull/78)] * Sanitize database at the end of install to prevent duplicate data [[#76](https://github.com/wp-cli/core-command/pull/76)] * Adapt package for framework v2 [[#81](https://github.com/wp-cli/core-command/pull/81)] #### 󠀁[wp-cli/cron-command](https://github.com/wp-cli/cron-command/)󠁿 * Adapt package for framework v2 [[#29](https://github.com/wp-cli/cron-command/pull/29)] #### 󠀁[wp-cli/db-command](https://github.com/wp-cli/db-command/)󠁿 * Add `db columns` command [[#100](https://github.com/wp-cli/db-command/pull/100)] * Count users instead of posts for the smoke test [[#98](https://github.com/wp-cli/db-command/pull/98)] * Fix test failure due to introduction of `wp_blogmeta` table [[#94](https://github.com/wp-cli/db-command/pull/94)] * Add `db clean` command [[#93](https://github.com/wp-cli/db-command/pull/93)] * Add examples for exporting certain posts [[#90](https://github.com/wp-cli/db-command/pull/90)] * pass `--column-statistics=0` to `mysqldump` command [[#105](https://github.com/wp-cli/db-command/pull/105)] * Add ISO size formats to `db size` [[#104](https://github.com/wp-cli/db-command/pull/104)] * Adapt package for framework v2 [[#110](https://github.com/wp-cli/db-command/pull/110)] #### 󠀁[wp-cli/embed-command](https://github.com/wp-cli/embed-command/)󠁿 * Adapt package for framework v2 [[#38](https://github.com/wp-cli/embed-command/pull/38)] * Scaffold missing top-level commands [[#35](https://github.com/wp-cli/embed-command/pull/35)] #### 󠀁[wp-cli/entity-command](https://github.com/wp-cli/entity-command/)󠁿 * Fix tests after Core’s introduction of a default “Privacy Policy” page [[#177](https://github.com/wp-cli/entity-command/pull/177)] * Abstract meta CRUD into methods [[#174](https://github.com/wp-cli/entity-command/pull/174)] * Remove duplicative `--user_email=` argument [[#173](https://github.com/wp-cli/entity-command/pull/173)] * Turn `latest` into actual version number [[#171](https://github.com/wp-cli/entity-command/pull/171)] * Improve the formatting of various format parameter documentation [[#168](https://github.com/wp-cli/entity-command/pull/168)] * Add `site meta` sub-command [[#159](https://github.com/wp-cli/entity-command/pull/159)] * Add `--unserialize` flag to `option list` command [[#156](https://github.com/wp-cli/entity-command/pull/156)] * Add `--from-post=` flag to create duplicate posts [[#154](https://github.com/wp-cli/entity-command/pull/154)] * Properly clone objects for comparison [[#152](https://github.com/wp-cli/entity-command/pull/152)] * Fix missing quote in documentation [[#147](https://github.com/wp-cli/entity-command/pull/147)] * Fix categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. list count [[#146](https://github.com/wp-cli/entity-command/pull/146)] * Add `user check-password` subcommand [[#144](https://github.com/wp-cli/entity-command/pull/144)] * Replace ‘install’ to ‘installation.’ [[#187](https://github.com/wp-cli/entity-command/pull/187)] * Add support for `--post_date_gmt` in `post generate` [[#184](https://github.com/wp-cli/entity-command/pull/184)] * Optional `--skip-email` flag for `wp user update` [[#155](https://github.com/wp-cli/entity-command/pull/155)] * Adapt package for framework v2 [[#192](https://github.com/wp-cli/entity-command/pull/192)] #### 󠀁[wp-cli/eval-command](https://github.com/wp-cli/eval-command/)󠁿 * Adapt package for framework v2 [[#27](https://github.com/wp-cli/eval-command/pull/27)] * Support `eval-file` from `STDIN` (implementation for #19) [[#21](https://github.com/wp-cli/eval-command/pull/21)] #### 󠀁[wp-cli/export-command](https://github.com/wp-cli/export-command/)󠁿 * Start with an empty site to avoid count issues [[#36](https://github.com/wp-cli/export-command/pull/36)] * Adapt package for framework v2 [[#44](https://github.com/wp-cli/export-command/pull/44)] #### 󠀁[wp-cli/extension-command](https://github.com/wp-cli/extension-command/)󠁿 * Add missing templates to this repository [[#107](https://github.com/wp-cli/extension-command/pull/107)] * Replace retired themes used in tests with new ones [[#105](https://github.com/wp-cli/extension-command/pull/105)] * Introduce `theme mod list` [[#100](https://github.com/wp-cli/extension-command/pull/100)] * Refresh `README.md` and test suite prior to `v1.1.10` release. [[#89](https://github.com/wp-cli/extension-command/pull/89)] * Allow for `modern-wordpress redirect` [[#85](https://github.com/wp-cli/extension-command/pull/85)] * Add `--all` flag for `plugin uninstall` command [[#84](https://github.com/wp-cli/extension-command/pull/84)] * Fix mustache file paths [[#109](https://github.com/wp-cli/extension-command/pull/109)]&[ [#112](https://github.com/wp-cli/extension-command/pull/112)] * Search: Add plugin or theme’s URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org on <[wordpress.org](https://wordpress.org/) > [[#108](https://github.com/wp-cli/extension-command/pull/108)] * Add `--all` flag to `plugin delete` [[#103](https://github.com/wp-cli/extension-command/pull/103)] * Adapt package for framework v2 [[#116](https://github.com/wp-cli/extension-command/pull/116)] #### 󠀁[wp-cli/i18n-command](https://github.com/wp-cli/i18n-command/)󠁿 * Prepare for v2 release [[#72](https://github.com/wp-cli/i18n-command/pull/72)] * WordPress Core support [[#69](https://github.com/wp-cli/i18n-command/pull/69)] * Check for more mistakes in translatable strings [[#64](https://github.com/wp-cli/i18n-command/pull/64)] * Separate translation extraction from Po file writing [[#63](https://github.com/wp-cli/i18n-command/pull/63)] * Make `PhpFunctionsScanner` extensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. [[#62](https://github.com/wp-cli/i18n-command/pull/62)] * Separate command argument handling from actual `__invoke()` [[#60](https://github.com/wp-cli/i18n-command/pull/60)] * Add `--headers` parameter [[#58](https://github.com/wp-cli/i18n-command/pull/58)] * Add `X-Generator` headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. to POT file [[#57](https://github.com/wp-cli/i18n-command/pull/57)] * Print some more helpful debug messages [[#56](https://github.com/wp-cli/i18n-command/pull/56)] * Factor directory iterator as a trait [[#54](https://github.com/wp-cli/i18n-command/pull/54)] * Text domain header [[#43](https://github.com/wp-cli/i18n-command/pull/43)] * Add `@when before_wp_load` to command namespace [[#42](https://github.com/wp-cli/i18n-command/pull/42)] * Add option to extract strings with any text domain [[#38](https://github.com/wp-cli/i18n-command/pull/38)] * Correctly pass `exclude` option to `JsCodeExtractor` [[#37](https://github.com/wp-cli/i18n-command/pull/37)] * Add warning when a string has two different translator comments [[#34](https://github.com/wp-cli/i18n-command/pull/34)] * Exclude some common directories [[#32](https://github.com/wp-cli/i18n-command/pull/32)] * Add ability to merge with existing POT file [[#31](https://github.com/wp-cli/i18n-command/pull/31)] * JavaScript String Extraction [[#26](https://github.com/wp-cli/i18n-command/pull/26)] * Don’t try to extract anything when there are no PHP files [[#24](https://github.com/wp-cli/i18n-command/pull/24)] * Add more tests related to translator comments [[#23](https://github.com/wp-cli/i18n-command/pull/23)] * Standardize file names [[#21](https://github.com/wp-cli/i18n-command/pull/21)] * Extract all supported functions. [[#13](https://github.com/wp-cli/i18n-command/pull/13)] #### 󠀁[wp-cli/import-command](https://github.com/wp-cli/import-command/)󠁿 * Adapt post/page generation to make them resilient to added privacy policy page[ [#25](https://github.com/wp-cli/import-command/pull/25)] * Adapt package for framework v2 [[#30](https://github.com/wp-cli/import-command/pull/30)] #### 󠀁[wp-cli/language-command](https://github.com/wp-cli/language-command/)󠁿 * Revert “Add plugin and theme command” [[#28](https://github.com/wp-cli/language-command/pull/28)] * Adapt package for framework v2 [[#43](https://github.com/wp-cli/language-command/pull/43)] * Use `download_url()` in language pack upgrader [[#41](https://github.com/wp-cli/language-command/pull/41)] * Enable updating languages for individual plugins and themes [[#40](https://github.com/wp-cli/language-command/pull/40)] * Warn if no plugin or theme has been specified [[#38](https://github.com/wp-cli/language-command/pull/38)] * Add `is-installed` command to check if a given language is installed [[#36](https://github.com/wp-cli/language-command/pull/36)] * Update `language core update --dry-run` message [[#32](https://github.com/wp-cli/language-command/pull/32)] * Add `language plugin` and `language theme` command. [[#29](https://github.com/wp-cli/language-command/pull/29)] #### 󠀁[wp-cli/media-command](https://github.com/wp-cli/media-command/)󠁿 * Adapt package for framework v2 [[#85](https://github.com/wp-cli/media-command/pull/85)] * Update examples in documentation [[#81](https://github.com/wp-cli/media-command/pull/81)] * Reinstate `ghostscript`/`imagick` install and fix `bmp` name in `regenerate` test. [[#69](https://github.com/wp-cli/media-command/pull/69)] * Document how to fetch attachment URL after import [[#68](https://github.com/wp-cli/media-command/pull/68)] * Clear WP object cache periodically on `media regenerate/import`. [[#62](https://github.com/wp-cli/media-command/pull/62)] #### 󠀁[wp-cli/package-command](https://github.com/wp-cli/package-command/)󠁿 * Assume default package name if `composer.json` file cannot be retrieved [[#78](https://github.com/wp-cli/package-command/pull/78)] * Avoid using Composer CA bundle if in phar. [[#73](https://github.com/wp-cli/package-command/pull/73)] * Move `test-command` to `wp-cli-test` Github organization [[#66](https://github.com/wp-cli/package-command/pull/66)] * Extract SSLSSL Secure Socket Layer - Encryption from the server to the browser and back. Prevents prying eyes from seeing what you are sending between your browser and the server. certificate from Phar first before using it in Composer[ [#83](https://github.com/wp-cli/package-command/pull/83)] * Adapt package for framework v2 [[#87](https://github.com/wp-cli/package-command/pull/87)] * Exclude broken Composer version [[#91](https://github.com/wp-cli/package-command/pull/91)] #### 󠀁[wp-cli/php-cli-tools](https://github.com/wp-cli/php-cli-tools/)󠁿 * Remove double semi-colon [[#130](https://github.com/wp-cli/php-cli-tools/pull/130)] * Fix potential endless loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. [https://codex.wordpress.org/The_Loop](https://codex.wordpress.org/The_Loop) in `prompt()` [[#129](https://github.com/wp-cli/php-cli-tools/pull/129)] * Fix off-by-1 error in progress bar examples [[#128](https://github.com/wp-cli/php-cli-tools/pull/128)] * Add optional `$msg` parameter to `cli\Progress\Bar::tick()` [[#126](https://github.com/wp-cli/php-cli-tools/pull/126)] #### 󠀁[wp-cli/rewrite-command](https://github.com/wp-cli/rewrite-command/)󠁿 * Adapt package for framework v2 [[#20](https://github.com/wp-cli/rewrite-command/pull/20)] #### 󠀁[wp-cli/role-command](https://github.com/wp-cli/role-command/)󠁿 * add `--show-grant` argument to `wp cap list` and `--grant` to `wp cap add` [[#19](https://github.com/wp-cli/role-command/pull/19)] * Add `--field=` support to listing roles [[#17](https://github.com/wp-cli/role-command/pull/17)] * Adapt package for framework v2 [[#23](https://github.com/wp-cli/role-command/pull/23)] #### 󠀁[wp-cli/scaffold-command](https://github.com/wp-cli/scaffold-command/)󠁿 * Skip PHPUnit tests for PHP 7.2+ [[#145](https://github.com/wp-cli/scaffold-command/pull/145)] * Modify `scaffold block` to create `index.js` [[#142](https://github.com/wp-cli/scaffold-command/pull/142)] * Fix theme-specific paths in scaffolded blocks [[#137](https://github.com/wp-cli/scaffold-command/pull/137)] * Add PHP 7.2 to CI templates [[#135](https://github.com/wp-cli/scaffold-command/pull/135)] * Exclude `tests/test-sample.php` via the phpunit.xml.dist file [[#134](https://github.com/wp-cli/scaffold-command/pull/134)] * Fix `sed -i` option on MacOS [[#132](https://github.com/wp-cli/scaffold-command/pull/132)] * Use correct default `$WP_TESTS_DIR` on MacOS [[#131](https://github.com/wp-cli/scaffold-command/pull/131)] * Use `phpunit` 6.5.6 for PHP 7.2 to get around core test incompat. [[#125](https://github.com/wp-cli/scaffold-command/pull/125)] * Fix WPCSWordPress Community Support A public benefit corporation and a subsidiary of the WordPress Foundation, [established](https://wordpressfoundation.org/news/2016/introducing-wordpress-community-support-a-public-benefit-subsidiary/) in 2016. in theme-tests generation [[#121](https://github.com/wp-cli/scaffold-command/pull/121)] * Switch CircleCI template to CircleCI 2.0. [[#115](https://github.com/wp-cli/scaffold-command/pull/115)] * Correct `'add_new_item'` label [[#163](https://github.com/wp-cli/scaffold-command/pull/163)] * Exclude string from escape warning [[#162](https://github.com/wp-cli/scaffold-command/pull/162)] * Update PHPCS default rule set [[#161](https://github.com/wp-cli/scaffold-command/pull/161)] * Add `--woocommerce` flag to `scaffold _s` command [[#159](https://github.com/wp-cli/scaffold-command/pull/159)] * Add PHPCompatibility sniffssniff A module for [PHP Code Sniffer](https://github.com/squizlabs/PHP_CodeSniffer) that analyzes code for a specific problem. Multiple stiffs are combined to create a PHPCS standard. The term is named because it detects [code smells](https://en.wikipedia.org/wiki/Code_smell), similar to how a dog would "sniff" out food. to scaffolded [[#154](https://github.com/wp-cli/scaffold-command/pull/154)] * Add escaping for blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. title [[#153](https://github.com/wp-cli/scaffold-command/pull/153)] * Remove `'wp-blocks'` from style dependency [[#151](https://github.com/wp-cli/scaffold-command/pull/151)] * Add `function_exists()` check to block PHP template [[#147](https://github.com/wp-cli/scaffold-command/pull/147)] * Adapt package for framework v2 [[#166](https://github.com/wp-cli/scaffold-command/pull/166)] #### 󠀁[wp-cli/search-replace-command](https://github.com/wp-cli/search-replace-command/)󠁿 * Fix tests that are broken due to the addition of a “Privacy Policy” page [[#78](https://github.com/wp-cli/search-replace-command/pull/78)] * Handle incomplete class (un)serialization gracefully [[#76](https://github.com/wp-cli/search-replace-command/pull/76)] * Handle PCRE errors gracefully [[#75](https://github.com/wp-cli/search-replace-command/pull/75)] * Remove “Site Not Found” message from multisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core. [Advanced Administration Handbook -> Create A Network.](https://developer.wordpress.org/advanced-administration/multisite/create-network/) usage [[#69](https://github.com/wp-cli/search-replace-command/pull/69)] * Fix broken GUID test [[#81](https://github.com/wp-cli/search-replace-command/pull/81)] * Improve `--regex-limit` logic [[#70](https://github.com/wp-cli/search-replace-command/pull/70)] * Adapt package for framework v2 [[#86](https://github.com/wp-cli/search-replace-command/pull/86)] * Add `--regex-limit` option. [[#62](https://github.com/wp-cli/search-replace-command/pull/62)] #### 󠀁[wp-cli/server-command](https://github.com/wp-cli/server-command/)󠁿 * Adapt package for framework v2 [[#42](https://github.com/wp-cli/server-command/pull/42)] #### 󠀁[wp-cli/shell-command](https://github.com/wp-cli/shell-command/)󠁿 * Adapt package for framework v2 [[#25](https://github.com/wp-cli/shell-command/pull/25)] * Better explain the `--basic` flag [[#23](https://github.com/wp-cli/shell-command/pull/23)] #### 󠀁[wp-cli/widget-command](https://github.com/wp-cli/widget-command/)󠁿 * Adapt package for framework v2 [[#19](https://github.com/wp-cli/widget-command/pull/19)] ### Contributors Here’s the complete list of the fantastic folks that have helped make this happen: [@2020media](https://github.com/2020media), [@abhijitrakas](https://github.com/abhijitrakas), [@ajitbohra](https://github.com/ajitbohra), [@alpipego](https://github.com/alpipego), [@austinginder](https://github.com/austinginder), [@benlk](https://github.com/benlk), [@BhargavBhandari90](https://github.com/BhargavBhandari90), [@burhandodhy](https://github.com/burhandodhy), [@chesio](https://github.com/chesio), [@CodeProKid](https://github.com/CodeProKid), [@danielbachhuber](https://github.com/danielbachhuber), [@drzraf](https://github.com/drzraf), [@emirpprime](https://github.com/emirpprime), [@ericgopak](https://github.com/ericgopak), [@erlendeide](https://github.com/erlendeide), [@felicianotech](https://github.com/felicianotech), [@felipeelia](https://github.com/felipeelia), [@fumikito](https://github.com/fumikito), [@GaryJones](https://github.com/GaryJones), [@ghost](https://github.com/ghost), [@gitlost](https://github.com/gitlost), [@greatislander](https://github.com/greatislander), [@JanVoracek](https://github.com/JanVoracek), [@janw-oostendorp](https://github.com/janw-oostendorp), [@javorszky](https://github.com/javorszky), [@jblz](https://github.com/jblz), [@jmichaelward](https://github.com/jmichaelward), [@johnbillion](https://github.com/johnbillion), [@josephfusco](https://github.com/josephfusco), [@kirtangajjar](https://github.com/kirtangajjar), [@kshaner](https://github.com/kshaner), [@lalaithan](https://github.com/lalaithan), [@lf-jeremy](https://github.com/lf-jeremy), [@libertamohamed](https://github.com/libertamohamed), [@marcovalloni](https://github.com/marcovalloni), [@marksabbath](https://github.com/marksabbath), [@miya0001](https://github.com/miya0001), [@MoisesMN](https://github.com/MoisesMN), [@montu1996](https://github.com/montu1996), [@NicktheGeek](https://github.com/NicktheGeek), [@ocean90](https://github.com/ocean90), [@pdaalder](https://github.com/pdaalder), [@pekapl](https://github.com/pekapl), [@pixolin](https://github.com/pixolin), [@pjeby](https://github.com/pjeby), [@pmbaldha](https://github.com/pmbaldha), [@ptrkcsk](https://github.com/ptrkcsk), [@ryanjbonnell](https://github.com/ryanjbonnell), [@sagarnasit](https://github.com/sagarnasit), [@salcode](https://github.com/salcode), [@sasagar](https://github.com/sasagar), [@schlessera](https://github.com/schlessera), [@spacedmonkey](https://github.com/spacedmonkey), [@spicecadet](https://github.com/spicecadet), [@stevegrunwell](https://github.com/stevegrunwell), [@strandtc](https://github.com/strandtc), [@svenkaptein](https://github.com/svenkaptein), [@swissspidy](https://github.com/swissspidy), [@terriann](https://github.com/terriann), [@thrijith](https://github.com/thrijith), [@tiagohillebrandt](https://github.com/tiagohillebrandt), [@tomjn](https://github.com/tomjn), [@torounit](https://github.com/torounit), [@wojsmol](https://github.com/wojsmol), [@wp-make-coffee](https://github.com/wp-make-coffee), [@yousan](https://github.com/yousan), [@zipofar](https://github.com/zipofar) A big thank you to all involved! ❤️ [#release](https://make.wordpress.org/cli/tag/release/), [#v2-0-0](https://make.wordpress.org/cli/tag/v2-0-0/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcli%2F2018%2F08%2F08%2Fwp-cli-v2-0-0-release-notes%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/schlessera/) [Alain Schlesser](https://profiles.wordpress.org/schlessera/) 4:39 pm _on_ July 31, 2018   # 󠀁[WP-CLI v2.0.0 release postponed](https://make.wordpress.org/cli/2018/07/31/wp-cli-v2-0-0-release-postponed/)󠁿 The upcoming WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) release v2.0.0 that was originally due to be released on July 31st is being re-scheduled for Wednesday, August 8th. This delay is due to the fact that it was [much more work to disentangle the feature tests](https://github.com/wp-cli/wp-cli/pull/4851) to split them up for the restructuring. I want to avoid hurrying the release, so I prefer to add some more time to let the dust settle and run further tests. Thanks for your patience! * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcli%2F2018%2F07%2F31%2Fwp-cli-v2-0-0-release-postponed%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/schlessera/) [Alain Schlesser](https://profiles.wordpress.org/schlessera/) 2:43 pm _on_ July 21, 2018 Tags: [Hack Day ( 4 )](https://make.wordpress.org/cli/tag/hack-day/), hackwpcli    # 󠀁[WP-CLI Hack Day Results](https://make.wordpress.org/cli/2018/07/21/wp-cli-hack-day-results/)󠁿 The first WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) Hack Day is over now and it was a great success! It created an entirely new level of interactivity to the process. **I’d like to say “Thanks!” to everyone that participated!** ❤️ It was awesome to help people get set up and then see the pull requests rolling in! Here’s a quick rundown of what we were able to achieve, and the problems we faced. We had **12 pull requests that were merged** during the event: 1. `wp-cli/scaffold-command` – [Add `--woocommerce` flag to `scaffold _s` command](https://github.com/wp-cli/scaffold-command/pull/159) 2. `wp-cli/handbook` – [Remove dead link](https://github.com/wp-cli/handbook/pull/238) 3. `wp-cli/handbook` – [Fix typo](https://github.com/wp-cli/handbook/pull/239) 4. `wp-cli/handbook` – [Fix typo in `code-review.md`](https://github.com/wp-cli/handbook/pull/241) 5. `wp-cli/wp-config-transformer` – [Remove colloquialism](https://github.com/wp-cli/wp-config-transformer/pull/6) 6. `wp-cli/language-command` – [Add `is-installed` command to check if a given language is installed](https://github.com/wp-cli/language-command/pull/36) 7. `wp-cli/handbook` – [Use `example.com`as placeholder](https://github.com/wp-cli/handbook/pull/242) 8. `wp-cli/core-command` – [Sanitize database at the end of install to prevent duplicate data](https://github.com/wp-cli/core-command/pull/76) 9. `wp-cli/core-command` – [Fix mustache template file path](https://github.com/wp-cli/core-command/pull/77) 10. `wp-cli/extension-command` – [Fix mustache files paths](https://github.com/wp-cli/extension-command/pull/109) 11. `wp-cli/scaffold-command` – [Exclude string from escape warning](https://github.com/wp-cli/scaffold-command/pull/162) 12. `wp-cli/wp-cli` – [Trigger new `'cli_init'` hook during WordPress `'plugins_loaded'` action](https://github.com/wp-cli/wp-cli/pull/4861) In addition to that, we had another **13 pull requests that were submitted** during the event but could not yet be merged: 1. `wp-cli/extension-command` – [Search: Add plugin or theme’s URL on](https://github.com/wp-cli/extension-command/pull/108) 2. `wp-cli/wp-cli` – [Add template for `core-command` to phar](https://github.com/wp-cli/wp-cli/pull/4854) 3. `wp-cli/wp-cli` – [Add templates for `extension-command` to phar](https://github.com/wp-cli/wp-cli/pull/4848) 4. `wp-cli/scaffold-command` – [Change to `.phpcs.xml.dist` and update rules](https://github.com/wp-cli/scaffold-command/pull/161) 5. `wp-cli/db-command` – [Pass `--column-statistics=0` to `mysqldump` command](https://github.com/wp-cli/db-command/pull/105) 6. `wp-cli/db-command` – [Add `db size` size formats](https://github.com/wp-cli/db-command/pull/104) 7. `wp-cli/entity-command` – [Detect post_content if `STDIN`](https://github.com/wp-cli/entity-command/pull/189) 8. `wp-cli/entity-command` – [Delete alert in case of custom post type](https://github.com/wp-cli/entity-command/pull/188) 9. `wp-cli/config-command` – [Add `shuffle-salts` command](https://github.com/wp-cli/config-command/pull/62) 10. `wp-cli/wp-cli-tests` – [Move PHPUnit tests for `behat-tags.php` over](https://github.com/wp-cli/wp-cli-tests/pull/3) 11. `wp-cli/scaffold-package-command` – [Update `circle.yml` to use its v2 API](https://github.com/wp-cli/scaffold-package-command/pull/177) 12. `wp-cli/dist-archive-command` – [Update `circle.yml` to use its v2 API](https://github.com/wp-cli/dist-archive-command/pull/25) 13. `wp-cli/handbook` – [Add documentation on how to troubleshoot](https://github.com/wp-cli/handbook/pull/243) The main reason why most of these were not merged during the event was that we had trouble with our automated tests. One problem was that many tests that depended on the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) infrastructure to download CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. files, plugins or themes had frequent timeouts. This seems to be caused by a recent move of the entire infrastructure, which made access to the content over CDN very spotty. Another problem was that Travis CI was acting up and was often stuck in “pending” state for prolonged time periods. During the last two hours of the event, we did a video chat over Zoom with all participants that wanted to join. We peaked at 13 participants to that video chat. It allowed for people to make a more personal connection, which added another dimension to the act of contributing. There was an official hashtag for the event: **[#hackwpcli](https://make.wordpress.org/cli/tag/hackwpcli/)**. [See all mentions of the hashtag #hackwpcli on Twitter](https://twitter.com/hashtag/hackwpcli). However, I initially messed up the hashtag and pointed people to the wrong one, so [some tweets have been tagged with #hackthecli instead](https://twitter.com/hashtag/hackthecli). 🤦‍♂️ We had an ambitious goal of merging 20 pull requests during the event. While we were not able to achieve that number of merged pull requests, I’d consider the event a complete success nevertheless, considering the amount of pull requests that were just waiting to get through the blocking tests to get merged. The event was also an experiment, to see whether a more direct, interactive form of contribution would attract more contributors. I think it did succeed in doing so, and I think it was a positive experience for the participants. 👉 **I would love for people to provide feedback about the event in the comments below.** 👈 I’d like to evaluate how well this type of contribution event was received and this will then shape a possible next iteration, where we’ll hopefully get even Travis& Co. to collaborate. [#hack-day](https://make.wordpress.org/cli/tag/hack-day/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcli%2F2018%2F07%2F21%2Fwp-cli-hack-day-results%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/schlessera/) [Alain Schlesser](https://profiles.wordpress.org/schlessera/) 2:18 am _on_ July 19, 2018 Tags: [v2.0.0 ( 2 )](https://make.wordpress.org/cli/tag/v2-0-0/) # 󠀁[Details on the upcoming major release](https://make.wordpress.org/cli/2018/07/19/details-on-the-upcoming-major-release/)󠁿 The upcoming major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2.( five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. of **WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) v2.0.0** is scheduled for **July 31st, 2018**. The release cycle has been a bit longer to account for the fact that some major changes are happening behind the scenes. This is what you can expect from the upcoming release: * PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. [https://www.php.net/manual/en/index.php](https://www.php.net/manual/en/index.php) version minimum will be bumped to PHP 5.4, as already [announced in December](https://make.wordpress.org/cli/2017/12/06/timing-for-v1-5-0-and-v2-0-0/)( see [#4554](https://github.com/wp-cli/wp-cli/issues/4554)). * Repository/package restructuring to separate the framework and the bundle that combines the framework with the default commands into separate packages (see [#4748](https://github.com/wp-cli/wp-cli/issues/4748)). * Removal of the Symfony dependencies from the framework package, to avoid conflicts in Composer setups (see [#4749](https://github.com/wp-cli/wp-cli/issues/4749)). * Convenience access to common contributor actions, through Composer scripts (see [#4167](https://github.com/wp-cli/wp-cli/issues/4167)). * A new standardized way of working on WP-CLI as a whole (see [#4750](https://github.com/wp-cli/wp-cli/issues/4750)). * Automate redundant work like regenerating `README.md` files (see [#4751](https://github.com/wp-cli/wp-cli/issues/4751)). * A new family of commands `wp i18n` for all your internationalization needs, brought to you by [@swissspidy](https://profiles.wordpress.org/swissspidy) (see [#4808](https://github.com/wp-cli/wp-cli/issues/4808) and [wp-](https://github.com/wp-cli/i18n-command)cli[/i18n-command](https://github.com/wp-cli/i18n-command)). * All of the small changes and bugfixes that we have been collecting since the v1.5.0 release, as most of this was skipped for v1.5.1 to keep that release “ bug-fix-only”. * Anything we might get production-ready during the upcoming [**WP-CLI Hack Day**](https://make.wordpress.org/cli/2018/07/04/wp-cli-hack-day/)! With the above restructuring, you should expect some **breaking changes**, most notably: * [#4554](https://github.com/wp-cli/wp-cli/issues/4554) will cause a breaking change for anyone trying to run WP-CLI on PHP 5.3. * [#4748](https://github.com/wp-cli/wp-cli/issues/4748) will cause a breaking change if a third-party command is being pulled-in via Composer AND that third-party command relies on running bundled commands as well. This will seldom be the case and will be an easy fix. Installations using the Phar will not be impacted. * [#4749](https://github.com/wp-cli/wp-cli/issues/4749) will cause a breaking change if a third-party command relies on one of the removed Symfony packages AND hasn’t declared that requirement in its own Composer configuration. This will seldom be the case and will be an easy fix. Installations using the Phar will not be impacted as the package manager still comes with these requirements included. * The versions of some the dependencies will be bumped. If you happen to not lock WP-CLI into a specific version constraint, but do so for some of its dependencies, you might see a version constraint conflict. * Any external code that relies on internal file structure, file naming or other internal details that are not part of the provided APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. could run the risk of breaking due to us moving things around from v1 to v2. This should hopefully not ever be the case, but you never know…     [#v2-0-0](https://make.wordpress.org/cli/tag/v2-0-0/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcli%2F2018%2F07%2F19%2Fdetails-on-the-upcoming-major-release%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/schlessera/) [Alain Schlesser](https://profiles.wordpress.org/schlessera/) 10:16 am _on_ July 14, 2018 Tags: contributing    # 󠀁[Contributing to WP-CLI](https://make.wordpress.org/cli/2018/07/14/contributing-to-wp-cli/)󠁿 ⌊Drawing of female freelancer sitting in front of their laptop⌉⌊Drawing of female freelancer sitting in front of their laptop⌉Does WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) save you effort and time while working on the sites you manage? Do you use WP-CLI to automate your infrastructure or deployments? Do you feel positive about the WP-CLI project and its mission? This guide will tell you about the many possibilities you have to get involved and play a role in this official WordPress team. ### Introduction First of all, thank you very much! If you’ve read this far, it must mean you are taking the initiative to contribute to WP-CLI. It’s because of you, and the community around you, that WP-CLI is such a great project. It not only makes for a fabulous tool people can use in a reliable manner, it also makes for a fun and rewarding project to collaborate on. Contributing can take many forms, and we will discuss the most prominent ones. Before we start, though, here’s a list of what contributing is not: * **Contributing is not limited to code.** * **Contributing does not require committing to a specific amount of time.** * **Contributing does not require expert knowledge in any of the areas it touches.** ⌊Drawing of a man hanging from a rope to work on a computer.⌉⌊Drawing of a man hanging from a rope to work on a computer.⌉We encourage you to contribute in the way that best fits your interests and abilities. If at any point, you’re not sure how to proceed with whatever you are doing or feel you’re in over your head, help & support is just a chat message away! Please don’t hesitate at any point to just ask questions or let us know about the issue you’re facing. Also, please do know that there are no expectations you need to fulfill or requirements you need to meet. This is meant to be an enjoyable, collaborative experience. So make sure you don’t put pressure on yourself and rectify your course of action if you feel that you’re not actually enjoying it anymore. Now, with that clarification out of the way, let’s try to cover some of the most common ways of contributing to WP-CLI. ### Spreading the message ⌊Drawing of a woman watering plants that look like social media network logos.⌉⌊ Drawing of a woman watering plants that look like social media network logos.⌉Not everyone knows about WP-CLI or how it can help improve how you interact with a WordPress site. There are multiple ways of how you can help spread the message about WP-CLI: * Post clever uses as tips to social media (tagging [@wpcli on Twitter](https://twitter.com/wpcli) is always appreciated). * Submit conference talks about usage and best practices. * Publish tutorials on your blog. * Give a demo at your local meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through [https://www.meetup.com/](https://www.meetup.com/). A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area.. WordPress.TV already contains [many examples of people sharing their knowledge about WP-CLI](https://wordpress.tv/?s=wp-cli). **Note**: You can request free stickers to distribute at events → [read about the requirements](https://make.wordpress.org/cli/2017/08/16/free-wp-cli-stickers-for-your-event/). ### Supporting users ⌊Drawing of a typing indicator in a chat system.⌉⌊Drawing of a typing indicator in a chat system.⌉A great way to learn more about WP-CLI yourself and to help other people make progress is to jump into one of the support channels and try to answer questions other people have posted. Doing the detective’s work, understanding how the moving pieces work and finally getting to the bottom of a user’s problem can be very rewarding, and you learn all kinds of internal details along the way. There are three main avenues where people can request support: * [#cli](https://make.wordpress.org/chat/)[ channel in the WordPress.org Slack team](https://make.wordpress.org/chat/) * [Threads tagged ](https://wordpress.org/support/topic-tag/wp-cli/)[WP_CLI](https://wordpress.org/support/topic-tag/wp-cli/) [ in the WordPress.org support forum](https://wordpress.org/support/topic-tag/wp-cli/) * [Questions tagged](https://wordpress.stackexchange.com/questions/tagged/wp-cli) [‘WP-CLI’](https://wordpress.stackexchange.com/questions/tagged/wp-cli)[ in the WordPress StackExchange](https://wordpress.stackexchange.com/questions/tagged/wp-cli) Any open issue/question/thread you can find in these locations are open for anyone to contribute an answer or to ask further questions to help diagnose the issue. ### Improving documentation ⌊Drawing of a woman filing notes.⌉⌊Drawing of a woman filing notes.⌉Is documentation your strength? Take a look at the currently open [documentation issues](https://github.com/issues?q=is%3Aopen+sort%3Aupdated-desc+org%3Awp-cli+label%3Ascope%3Adocumentation) and see if you can tackle any of those, or create a new issue if you’ve read through the documentation and found it lacking in a specific area. There are a couple different types of documentation currently part of WP-CLI: * Documentation for individual WP-CLI commands (anything underneath [developer.wordpress.org/commands](https://developer.wordpress.org/cli/commands/)) is contained in the PHPDoc for each command. This means that to edit the documentation for a command, you will need to edit the file that actually provides the functionality for that command. The web documentation is generated from these files at the time of release, so you may not see your changes until the next release. * Individual documentation pages (anything under [make.wordpress.org/cli/handbook](https://make.wordpress.org/cli/handbook/)) can be edited by contributing to the [handbook repository on GitHub](https://github.com/wp-cli/handbook/). You don’t necessarily need to navigate the GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the‘ pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/) repo though; any page that is part of this repository will have an `Edit` link in the top right of the page which will take you to the corresponding file on GitHub. Just clicking on that link brings you to a live editor which will generate a pull request out of your changes. ### Localization ⌊Drawing of multiple windows showing the same basic content.⌉⌊Drawing of multiple windows showing the same basic content.⌉WP-CLI is in a special position when it comes to localization. Its main output is not supposed to be localized, as it is used for scripting purposes. If your scripts depend on a given string to be printed to the console, translating that string into a different language will, of course, break these scripts. What should be translated, though, is the different types of documentation we have. Unfortunately, we are currently lacking the infrastructure support on make.wordpress. orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/)/cli to properly support translated versions of the handbook or command reference. What can be translated right now and is open for contributors is the README file shown as the frontpage on `wp-cli.org`. The different language versions can be found in subfolders in the [wp-cli/wp-cli.github.com repository](https://github.com/wp-cli/wp-cli.github.com). Please use the [English source version](https://github.com/wp-cli/wp-cli.github.com/blob/master/index.md) as the reference source, as it is the only one to be guaranteed to be up-to-date at any time. ### Reporting security issues ⌊Drawing of a man manipulating a security shield.⌉⌊Drawing of a man manipulating a security shield.⌉**Don’t publicly disclose a security issue you’ve just found!** The WP-CLI team and the WordPress community take security bugs seriously. We appreciate your efforts to responsibly disclose your findings and will make every effort to acknowledge your contributions. To report a security issue in a responsible way, please visit the [WordPress HackerOne](https://hackerone.com/wordpress) program. You will be able to submit details about the security vulnerability in a confidential way, to avoid malicious users immediately exploiting the vulnerability on live sites. You will be contacted by the WordPress security team about next steps as soon as possible. ### Reporting a bug ⌊Drawing of a computer screen showing an alert.⌉⌊Drawing of a computer screen showing an alert.⌉Think you’ve found a bug? We’d love for you to help us get it fixed. Before you create a new issue, you should [search existing issues](https://github.com/issues?utf8=%E2%9C%93&q=sort%3Aupdated-desc+org%3Awp-cli+label%3Abug)(*) to see if there’s an existing resolution to it, or if it’s already been fixed in a newer version of WP-CLI. You should also check our [documentation on common issues and their fixes](https://make.wordpress.org/cli/handbook/common-issues/). Once you’ve done a bit of searching and discovered there isn’t an open or fixed issue for your bug, please [follow our guidelines for submitting a bug report](https://make.wordpress.org/cli/handbook/bug-reports/) to make sure it gets addressed in a timely manner. ### Requesting a new feature ⌊Drawing of a man rearranging post-its on a whiteboard.⌉⌊Drawing of a man rearranging post-its on a whiteboard.⌉To request a new feature, please create a new issue in the [issue tracker of the wp-](https://github.com/wp-cli/ideas/issues)cli[/ideas repository](https://github.com/wp-cli/ideas/issues). This is the very first step that any new functionality should take. It will be further fleshed out within this issue until a decision has been made about whether the feature is a good fit for the official WP-CLI bundle and how the technical implementation should be handled. At that point, the issue will move into the repository where its code will finally reside. ### Working on the code Before you can start writing code, you need to decide what you plan on working on. * **Good first issues** To get your feet wet with working on the WP-CLI codebase, you should star with one of the [issues that are marked as ](https://make.wordpress.org/cli/good-first-issues/) [good-first-issues](https://make.wordpress.org/cli/good-first-issues/). These issues usually require less historical knowledge and are very limited in scope and complexity. Often times, you’ll find the proper approach to solve the issue directly explained within the issue conversation. * **Fixing a bug** Even though we spend a lot of time writing tests and reviewing code, we cannot completely avoid bugs in a codebase of this complexity. If you want to see a list of known bugs and help fix them, you can use [this GitHub search](https://github.com/issues?utf8=%E2%9C%93&q=sort%3Aupdated-desc+org%3Awp-cli+label%3Abug)(*). * **Implementing a new feature** You can find the collection of submitted feature requests in the issue tracker of the wp-cli/ideas repository. There are labels that define what the current state of a feature request is: - `state:approved`: This feature request has already been accepted in principle and only needs someone that can invest the time to make it happen. - `state:considering`: This feature request seems to be useful and a good fit for the project, but additional discussion and fleshing out is needed before a final decision can be made. - `state:unlikely`: This feature request was deemed not to be a good fit for the project. The reason for this is probably stated in the issue conversation. An implementation of this feature is unlikely to be accepted for bundling into an official release. Note: This might still be a useful third-party command in its own right. - In case there is no state label associated with the issue, it probably needs more extensive discussion still to find out how it relates to the official WP-CLI code. ⌊Drawing of a software developer working on their laptop.⌉⌊Drawing of a software developer working on their laptop.⌉Once you’ve decided to commit the time to seeing your pull request through, please [follow our guidelines for creating a pull request](https://make.wordpress.org/cli/handbook/pull-requests/) to make sure it’s a pleasant experience. See “[Setting](https://make.wordpress.org/cli/handbook/pull-requests/#setting-up) [ up](https://make.wordpress.org/cli/handbook/pull-requests/#setting-up)” for details on making local modifications to WP-CLI. Keep in mind pull requests are [expected to have tests](https://make.wordpress.org/cli/handbook/pull-requests/#running-and-writing-tests) covering the scope of the change. Read through [our code review guidelines](https://make.wordpress.org/cli/handbook/code-review/) for a better understanding of how your pull request will be evaluated. ### Anything missing? Hopefully, this short guide has presented many different ways of how users and fans of WP-CLI can contribute to the project’s continued success. **If you think we missed anything, please tell us so in the comments below!** We’d love to hear your feedback and are curious about yet other ways of contributing to WP-CLI. --- _(*) Link requires you to be logged into Github, otherwise it will show a 404. All images provided by [unDraw](https://undraw.co/illustrations) and [licensed under the MIT license](https://undraw.co/license). [#contributing](https://make.wordpress.org/cli/tag/contributing/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcli%2F2018%2F07%2F14%2Fcontributing-to-wp-cli%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/schlessera/) [Alain Schlesser](https://profiles.wordpress.org/schlessera/) 7:14 pm _on_ July 4, 2018 Tags: [Hack Day ( 4 )](https://make.wordpress.org/cli/tag/hack-day/) # 󠀁[WP-CLI Hack Day](https://make.wordpress.org/cli/2018/07/04/wp-cli-hack-day/)󠁿 We’re currently planning the first ever **WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) Hack Day**! 🤓🎈 On 🗓 **Friday, 20th July 2018** we’ll officially kick off the WP-CLI Hack Day at 🕗 **08:00 CEST**. From that point on, I’ll be generally available in [Slack #cli channel](https://wordpress.slack.com/messages/C02RP4T41) and on the [GitHub `wp-cli` organization](https://github.com/wp-cli/) to onboard new contributors, help people pick issues to work on and remove hurdles that keep them from finishing their PRs. This will continue more or less without interruption during the entire event. From 🕓 **16:00-18:00 CEST** we’ll have an open video chat that everyone can join, where we can discuss remaining issues live and chat about the progress we’ve made. This extended video chat session will then conclude the event. Shortly after 🕕 ** 18:00 CEST**, I will post a [make/cli](https://make.wordpress.org/cli/) blog post about the progress we were able to make during the allotted time frame. The 🎯 **goal** for this first WP-CLI Hack Day is both simple and ambitious: **Finish the day with 2️⃣0️⃣ pull requests that have been merged during the event ❗️** Everyone is welcome to participate! This event is supposed to be fun and inspiring, and we expect people to help each other make progress along the way.   **Let’s make this happen! 👍**   **Update**: the official hashtag for the event is [#hackwpcli](https://twitter.com/hashtag/hackwpcli?src=hash) 📣 --- _**Note on times:**_ The times are in CEST timezone to fit my schedule. ( ⇒ [See time range and copy into calendar](https://www.worldtimebuddy.com/?qm=1&lid=2950159,5391959,1850147&h=2950159&date=2018-7-20&sln=8-18)) I’m fully aware this is not ideal for everyone around the globe. Hopefully, this first try at such an event will be a big success, and we’ll try it again with more helpers and an extended time zone at a later date. [#hack-day](https://make.wordpress.org/cli/tag/hack-day/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcli%2F2018%2F07%2F04%2Fwp-cli-hack-day%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/schlessera/) [Alain Schlesser](https://profiles.wordpress.org/schlessera/) 4:02 pm _on_ May 31, 2018 Tags: gpg, key, [release ( 21 )](https://make.wordpress.org/cli/tag/release/), signing    # 󠀁[GPG Signature Change](https://make.wordpress.org/cli/2018/05/31/gpg-signature-change/)󠁿 Starting from May 31st, 2018 (from WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) version 1.5.1 onwards), the GPG key that is used to sign the releases has changed. Here’s the new public key for signed releases: ``` -----BEGIN PGP PUBLIC KEY BLOCK----- mQENBFsQEBkBCADfGAhxQ71XaIk31SjD8dNH3uVNtPh/2SIIhYbObMvEG6uoMucP t3jCsnkh/veKBkJ+HJ/XcARGoFYdaCZo5PTORBWOwHmeWPbu7aiAM4v3EKPc8wZP jabtEejwZrRFlSlAu5YL25ldz5KNgvGOBdje9jUi2iovQ4lfjMEuH2sXhmDQPbDW 22Fb2xinvmlnyf5kJn9ADiWm6VEnaNvaL96TCC1iUrMJmYI0m29j2sVbKJIq8ZBO CgtY4llPC7QskWw8VXEAq2WnQeZMVLqxOSoRDy/qUvw0RR+DfiXsrHjBxAH4uvHK zUdnMl1Qbh2A/rfcsIaJubXg5pUXwF7TCvSPABEBAAG0JVdQLUNMSSBSZWxlYXNl cyA8cmVsZWFzZXNAd3AtY2xpLm9yZz6JAU4EEwEIADgCGwMFCwkIBwIGFQgJCgsC BBYCAwECHgECF4AWIQRjr3qhUGfAVhb93YijoujyJvC8BgUCWxAQ7AAKCRCjoujy JvC8BmYTCACPEYQr89U/H/iQcI012UaOSLYLx+Qj9oA7p9gv2mZSBHNSijzhnizo QBEg7q7BXF8B8UqL9ZhUWfG9PiR8kkFbBN1sIY0RM5cFltb3cJthVH4ZV8SUiGW6 zIOd8m5JXVnekmZyJFpufxDHms6F3Z2RNUbdZSp2Mj+5p/a4GtJhfGGpfYBbXOxG gdx5dmipjlxfP5M3YL4QCJoySB+sY92de5b3S3tqmj7ldb/GRvN/7XjoMDwbRso6 jrhGtk8TjtAV0l/VdjebpI6zivrDLYDQq5vwi6hGPl7k88ElU47vaJiJX5yXaJ/k LFQ3g8raFQq69nqcDjJLGds+Y+lAXrtzuQENBFsQEBkBCAC9ZUHiXbBLvCejMXKK vFpKaVsovI6RBU8l0sC+00yvpP+TJmRXracnesTqHyTlhAUMhpbFvG0mBMBdROt5 IPRZ2S9JdJKZFVqO7Nop0elO8wUe6rsEHisUbEP49BcqDHGxfEnB/MubnJO1hHEH 1ftnZBEQW3jNagOTikki9675qF4ONvaSeCY9DkHa4lbau24SzePvtWuxYGsdX+Jf ikFxq8N2ArPlSoVv/DKEbl5dgz1hYFJ9qBKoXSbaKk1TxZ4bA8nxcznZHS+8Lirv tEjB8Z68Hz+pXIFJBbchC/FMatZC2hjFobedc4dT3nxf5iiH9XsHI5bqp3UEsPlx 8LP5ABEBAAGJATYEGAEIACACGwwWIQRjr3qhUGfAVhb93YijoujyJvC8BgUCWxAR IQAKCRCjoujyJvC8BhGMCACkNhkshrOYDRoOwny8m1mI2nSIU0KnjEruaeAXrY2T 5VHNfLkTX3wD2HYO97r1CvUNBUWpmTwSicK0Z6TCDp4A9Oi+z5CA/5zBT/iydC6E czNAPUehdLKka9Qs0vrVq22S0dDiA4xXZUvQpoo8VUKlvau9igF98mbd56U89s3L gg7O72A/4x7rhDO0Q+U8SIBJtFmEHIcu6gHkooQW3d7opHKCjbnyqxDQ/iUY3b8o n75TXnDJWbjCFTiTMyVTeyQfK0Us8FbJNXhMMagalRQu/sBH56S7Cg2OLciQB1B2 sLbhbfYDXYriI/OGVIPvCEIH6FX4+KiFy7RS+0JthI0R =fQDM -----END PGP PUBLIC KEY BLOCK----- ``` You can find the above current (as well as the old) key in the [`README.md` file of the `wp-cli/builds` repository](https://github.com/wp-cli/builds/blob/gh-pages/README.md), as well as in the form of a downloadable file in that same repository: [`wp-cli/builds/wp-cli.pgp`](https://github.com/wp-cli/builds/blob/gh-pages/wp-cli.pgp). The new key is configured to be the following user: `WP-CLI Releases (releases@wp-cli.org)` The new key will not expire. In case you have problems with using this key, please open an issue in [`wp-cli/wp-cli`](https://github.com/wp-cli/wp-cli/issues/new). [#gpg](https://make.wordpress.org/cli/tag/gpg/), [#key](https://make.wordpress.org/cli/tag/key/), [#release](https://make.wordpress.org/cli/tag/release/), [#signing](https://make.wordpress.org/cli/tag/signing/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcli%2F2018%2F05%2F31%2Fgpg-signature-change%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/schlessera/) [Alain Schlesser](https://profiles.wordpress.org/schlessera/) 9:59 am _on_ April 21, 2018 Tags: [release ( 21 )](https://make.wordpress.org/cli/tag/release/), [v1.5.1 ( 2 )](https://make.wordpress.org/cli/tag/v1-5-1/)    # 󠀁[Version 1.5.1 released](https://make.wordpress.org/cli/2018/04/21/version-1-5-1-released/)󠁿 A new release is upon us! We’re excited to bring you WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) v1.5.1, an intermediary bugfix release with a total of 52 merged pull requests since v1.5.0 in January 2018. ## About this release This is a bugfix release, which means that you shouldn’t expect major feature enhancements. We’re working hard on v2.0.0 which is planned for the summer, and all new features will have to wait for that big one. ## Notable features Yes, I just said not to expect any new features. However, a small number of features managed to sneak into this release nevertheless. ### Edit your config files with ease The `config` command now has a new `config edit` function that opens the `wp-config. php` file in your favorite editor for easy changes. You can configure the editor to be used through the `EDITOR` environment variable [[#48](https://github.com/wp-cli/config-command/pull/48)]. ### Get better insight into your capabilities Although WordPress is able to have a capability be set to `false`, to effectively mean an explicit  “deny” of that capability, WP-CLI did not yet show that distinction. It only let you know that the capability was defined, but not whether it was negated, giving the false impression of it being “allowed” instead. This has now changed, and you can get a complete picture of how the capabilities are set by adding the `--show-grant` to the `cap list` command [[#19](https://github.com/wp-cli/role-command/pull/19)]. **Breaking change**: Note that the default behavior of `cap list` has slightly changed because of that. Whereas the previous version showed a capability set to `false` alongside the normal capabilities, a simple `cap list` without the new `--show-grant` flag will now hide the capabilities that are set to `false`, effectively returning only the capabilities that are actually “granted”. ## Bugs that were fixed **Framework** * Show help text even when `proc_(open|close)` aren’t available [[#4758]](https://github.com/wp-cli/wp-cli/pull/4758) * Normalize Mac `tar` output [[#4674]](https://github.com/wp-cli/wp-cli/pull/4674) * Tests should not depend on external commands [[#4673]](https://github.com/wp-cli/wp-cli/issues/4673) * Fix `phpunit` extractor, glob, behat tests [[#4672]](https://github.com/wp-cli/wp-cli/pull/4672) * Move `phpunit` PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. [https://www.php.net/manual/en/index.php](https://www.php.net/manual/en/index.php) directive tests to behat [[#4675]](https://github.com/wp-cli/wp-cli/pull/4675) * Only run `phpcs` against PHP files on pre-commit hook [[#4755]](https://github.com/wp-cli/wp-cli/pull/4755) **Commands** * `plugin verify-checksums` - Make soft change detection more flexible [[#41](https://github.com/wp-cli/checksum-command/pull/41)] - Add backslash to the regex for matching Windows paths correctly [[#39](https://github.com/wp-cli/checksum-command/pull/39)] * `config` - Escape `$n` and `\\n` sequences in `preg_replace()` values [[wp-cli-transformer #3](https://github.com/wp-cli/wp-config-transformer/pull/3)] * `package` - Assume default package name if `composer.json` file cannot be retrieved [[#78](https://github.com/wp-cli/package-command/pull/78)] - Avoid using Composer CA bundle if in phar [[#72](https://github.com/wp-cli/package-command/issues/72)] * `scaffold block` - Fix theme-specific paths in scaffolded blocks [[#137](https://github.com/wp-cli/scaffold-command/pull/137)] - Modify `scaffold block` to create `index.js` [[#142](https://github.com/wp-cli/scaffold-command/pull/142)] * `scaffold plugin` - Exclude `tests/test-sample.php` via the `phpunit.xml.dist` file [[#134](https://github.com/wp-cli/scaffold-command/pull/134)] * `scaffold plugin-tests | theme-tests` - Fix WPCSWordPress Community Support A public benefit corporation and a subsidiary of the WordPress Foundation, [established](https://wordpressfoundation.org/news/2016/introducing-wordpress-community-support-a-public-benefit-subsidiary/) in 2016. in theme-tests generation [[#121](https://github.com/wp-cli/scaffold-command/pull/121)] - Use correct default `$WP_TESTS_DIR` on MacOS [[#131](https://github.com/wp-cli/scaffold-command/pull/131)] - Fix `sed -i` option on MacOS [[#132](https://github.com/wp-cli/scaffold-command/pull/132)] - Switch CircleCI template to CircleCI 2.0 [[#115](https://github.com/wp-cli/scaffold-command/pull/115)] - Add PHP 7.2 to CI templates [[#135](https://github.com/wp-cli/scaffold-command/pull/135)] * `search-replace` - Handle incomplete class (un)serialization gracefully [[#76](https://github.com/wp-cli/search-replace-command/pull/76)] - Handle PCRE errors gracefully [[#75](https://github.com/wp-cli/search-replace-command/pull/75)] - Remove “Site Not Found” message from multisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core. [Advanced Administration Handbook -> Create A Network.](https://developer.wordpress.org/advanced-administration/multisite/create-network/) usage [[#69](https://github.com/wp-cli/search-replace-command/pull/69)] **Contributors to this release (15 total)** [danielbachhuber](https://github.com/danielbachhuber), [emirpprime](https://github.com/emirpprime), [ericgopak](https://github.com/ericgopak), [felicianotech](https://github.com/felicianotech), [gitlost](https://github.com/gitlost), [johnbillion](https://github.com/johnbillion), [kshaner](https://github.com/kshaner), [lalaithan](https://github.com/lalaithan), [pdaalder](https://github.com/pdaalder), [ptrkcsk](https://github.com/ptrkcsk), [salcode](https://github.com/salcode), [schlessera](https://github.com/schlessera), [stevegrunwell](https://github.com/stevegrunwell), [thrijith](https://github.com/thrijith), [torounit](https://github.com/torounit) [#release](https://make.wordpress.org/cli/tag/release/), [#v1-5-1](https://make.wordpress.org/cli/tag/v1-5-1/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcli%2F2018%2F04%2F21%2Fversion-1-5-1-released%2F%23respond&locale=en_US) ## Post navigation [← Older posts](https://make.wordpress.org/cli/page/8/?output_format=md) [Newer posts →](https://make.wordpress.org/cli/page/6/?output_format=md)