A new release 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/ https://make.wordpress.org/cli/ is available as of today: WP-CLI v2.6.0. For this release, we had 57 contributors collaborate to get 311 pull requests merged. 🎉

The pandemic is still controlling our daily lives, and as a side-effect we still notice a significant reduction in contributors to WP-CLI, probably due to the lack of in-person contributor days.

As always, big thanks to the WP-CLI sponsors that make the continued maintenance possible – even with a reduced number of contributors. ❤️

Apart from the numerous bug fixes that were included in this release, we also managed to snuggle in a few new features that add to the power or convenience of your CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. experience, so I want to spend a few paragraphs going over some of the noteworthy changes. As always, you can also skip directly to the detailed changelog if you prefer.

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. http://php.net/manual/en/intro-whatis.php. 8.1 Support

WP-CLI now officially supports PHP 8.1. All commands are being extensively tested against PHP 8 and the actual development is currently being done on PHP 8.1 as well.

However, keep in mind that PHP 8.1 support is not fully there for WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., and especially for a large part of plugins and themes. Due to the nature of the changes that PHP 8.1 brings about, it is very easy to break perfectly compatible WordPress Core or WP-CLI via the actions/filters system. Keep this in mind when trying to diagnose PHP 8.1 compatibility issues and trying to deduce where the erroneous code is to be found.

For those of you who are not closely following the PHP release cycles, please be aware that only PHP 8.0 and 8.1 are currently actively supported versions. WP-CLI sticks with the WordPress Core PHP support policy (+ 1 year), which means we’re still spending huge amounts of efforts to keep everything running all the way down to PHP 5.6 at the moment.

If you want to help the maintainers in their work, please ensure that all your sites run on the latest PHP versions, and nag your hosting providers to move everything over to the latest and greatest. WordPress will only bump the minimum version when the number of active sites on PHP 5.6 has dropped to an insignificant amount.

New commands for managing application passwords

The following commands were added to allow CLI users to create and manage WordPress application passwords:

• wp user application-password list
• wp user application-password get
• wp user application-password exists
• wp user application-password update
• wp user application-password record-usage
• wp user application-password create
• wp user application-password delete

Although you could technically already work with application passwords by directly controlling the WordPress user-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. table, this now provides a clean 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. that abstracts away the technical implementation. See the Application Passwords: Integration Guide to find out more about how to use them.

New global flag: --context

A new global flag --context=<context> was added which allows users to select the WordPress context in which WP-CLI is supposed to execute its command(s).

One of the main goals is to allow WP-CLI to run updates on premium plugins and themes without requiring any special setup. From our initial testing, this allows a large range of popular premium extensions to just work™️ with WP-CLI in terms of their update procedures.

Possible values for this flag with this initial release:

• cli: The context which has been the default before introduction of this flag. This is something in-between a frontend and an admin request, to get around some of the quirks of WordPress when running on the console.
• admin: A context that simulates running a command as if it would be executed in the administration backend. This is meant to be used to get around issues with plugins that limit functionality behind an is_admin() check.
• auto: Switches between cli and admin depending on which command is being used. For this initial release, all wp plugin * and wp theme * commands will use admin, while all other commands will use cli.
• frontend: [WIP] This does nothing yet.

Roadmap: By default, the --context flag will be set to cli with this initial release (v2.6.0). With WP-CLI v2.7.0, the default will change to auto. This gradual deployment will allow hosters and site owners to run tests on v2.6.0 by manually setting the context before the default behavior is changed.

If you want to use the future default of --context=auto right away in your present operations, you can do so by adding the necessary context: auto line to your global wp-cli.yml configuration file. Feel free to check the documentation on WP-CLI configuration files if this is new to you.

We also have a new hook to support this new global flag: before_registering_contexts. This hook behaves like a filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. with one argument: array<string, Context> $contexts. When hooking into this hook, the callback should return (a potentially modified) $contexts value. This can be used to remove or override bundled contexts or add new ones.

To make this work, the hook functionality in WP-CLI (provided via WP_CLI::do_hook()) was modified to return the first argument if arguments were provided.

Thanks to Cloudways for the special support and testing of this new flag with the goal of solving the “premium updates problem” for everyone.

Configurable WP-CLI cache settings

The WP-CLI file cache can now be configured via the following environment variables:

• WP_CLI_CACHE_DIR – Directory in which to store the cached files. Default value: "$home/.wp-cli/cache".
• WP_CLI_CACHE_EXPIRY – Time after which cached files are automatically purged, in seconds. Default value: 15552000 (6 months).
• WP_CLI_CACHE_MAX_SIZE – Total size of the file cache after which older files are purged, in bytes. Default value: 314572800 (300 MB).

This not only allows you to fine-tune the WP-CLI cache behavior for the best balance between available storage and bandwidth usage, it could also be used to share cache storage between installations/users (beware the security implications, though!).

Use custom names/locations for the wp-config.php file

The different config * commands now accept a new flag --config-file=<filepath> that allow you point the different manipulations towards a custom location, that might not even fully adhere to conventions for the WordPress wp-config.php file.

This allows you for example to use the config set command for a configuration file outside of the WordPress document root (and parent folder).

Keep in mind that you’re on your own when it comes to making WordPress understand the structure and bootstrap correctly!

Generate a dotenv file from your existing wp-config.php file

For all the 12-factor app fans out there, WP-CLI has learnt a new format for its config list command: --format=dotenv. This will take the existing configuration key/value pairs in your wp-config.php file and render them in a format that you can use in a .env file.

Combine with the previously mentioned --config-file to extract the dotenv file from an arbitrary location, even without a WordPress installation present.

Allow 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/ or can be cost-based plugin from a third-party/theme enumeration without forcing an update check

Previously, when you run plugin list or theme list, WP-CLI would automatically run a check in the background to see if updates are available. This is slow and expensive to do, and might not always be what is needed, especially in scripting scenarios.

This automatic check for updates can now be disabled for these two commands with the --skip-update-check flag. This can drastically speed up some scripts and make them more reliable.

New flag --strict for adapting the filtering of taxonomies by post type

When retrieving taxonomies for a given post type, the old default behavior of WordPress (through the use of get_taxonomies()) is to only show those taxonomies that have as a sole associated post type the requested one. Taxonomies that have multiple associated post types, including the requested one, are not returned.

WordPress had added a newer mechanism via get_object_taxonomies() that would return all taxonomies that are in some way associated with the requested post type, even if other post types are associated as well.

WP-CLI now has a new --strict flag for the taxonomy list command that defines whether the strict filtering (the old default) should be used, or the more sensible inclusive approach should be used via --no-strict (or --strict=false).

We’ve opted to make this new, more sensible approach (i.e. --no-strict) the new default, so be mindful of that if you’re using taxonomy list in a script somewhere.

Another round of improvements to the i18n * commands

As with all of the recent releases, the i18n * commands have received yet another round of overall improvements to keep in sync with the localisation requirements of WordPress Core.

From new flags like --subtract-and-merge, --update-mo-files & --location and multiple improvements to the way 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/. syntax is parsed all the way up to the support for the new theme.json format, all your localization needs should be accounted for (at least for now).

Make your to check out the detailed logs to find out more and play around with the new functionality when you get the chance!

With super admin permissions come super admin consequences!

WP-CLI now mirrors the behavior of WordPress core and triggers various 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. when you grant or revoke the super admin status to users.

The following actions are being triggered now but the super-admin add & super-admin remove commands:

• grant_super_admin (before changes, always executed)
• granted_super_admin (after changes, executed only on success)
• revoke_super_admin (before changes, always executed)
• revoked_super_admin (after changes, executed only on success)

Changes to the default branches

In order to make the language used in the code and documentation of WP-CLI more inclusive, work has started to change the name of default branch across all repositories. From now on, the default branch name across the WP-CLI 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 be the repository owner. https://github.com/ organization is main.

This change is currently a work in progress, as it unfortunately causes open pull requests to be automatically closed and often become unsalvageable. The current progress of this effort can be monitored here: wp-cli/wp-cli#5598.

Keep this in mind when you want to check out the latest development state of a repository or contribute by creating a PR!

Detailed change log

To avoid too much noise in the list above, the following types of pull requests have been omitted:

• PRs that only bumped dependencies to their latest version.
• PRs that only fixed a typo in the documentation.
• PRs that add an allow-plugins rule to Composer

wp-cli/wp-cli-bundle

• Disable deployments on forks [#389]
• DeployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. from main branch [#385]
• Revert usage of Mustache fork [#373]
• Use latest branch for Roave security advisories [#357]
• Add DEB build workflow [#345]
• Add RPM build workflow [#344]
• Switch to dev-master for wp-cli framework [#333]

wp-cli/wp-cli

• Adapt VERSION from 2.5.1-alpha to 2.6.0-alpha [#5605]
• Fix Composer stack tests [#5599]
• Detect and ignore BOMs [#5597]
• Check github.repository_owner in automerge workflow [#5591]
• Revert addition of the Mustache PHP 8.1 workaround and update dependency [#5590]
• Use Mustache work-around for PHP 8.1 compat [#5588]
• Use fork on schlessera for Mustache PHP 8.1 fix [#5587]
• Re-add subcommands on all composite commands that are overwritten [#5584]
• Fix default mysqli error reporting mode for PHP 8.1+ [#5582]
• Add --context flag [#5581]
• Make cache size and expiry configurable via environment variables [#5576]
• Updated default branch for roave/security-advisories [#5575]
• Fix wrong variable name used in argument parsing [#5564]
• Fix regression that broke extending existing commands [#5563]
• Add a SECURITY.md file [#5562]
• Update credits [#5556]
• Pass in arguments to before_run_command hook [#5554]
• Change “Fake Site” site name to “WordPress” in core multisite-install command [#5552]
• Add missing docblocks [#5551]
• Make logger accessible and add colorization control to Quiet logger [#5549]
• Fix OOM issues when exporting to STDOUT [#5546]
• Allow WP_DEBUG_LOG to override the debug.log location [#5511]

wp-cli/handbook

• Document the exec global parameter [#397]
• Provide example of optional positional arguments [#390]
• Added create table statement. [#389]

wp-cli/wp-cli.github.com

• Update zh-cn translation file [#422]
• Update build status badge [#416]
• Fix quick links anchors in German translation [#415]

wp-cli/cache-command

• Add PHP 8.1 support [#72]

wp-cli/checksum-command

• Add PHP 8.1 support [#89]

wp-cli/config-command

• Add PHP 8.1 support [#135]
• Document special EOF anchor [#136]
• Add --config-file argument to process custom configuration files [#104]
• Add dotenv format option to config get command [#102]
• Escape values to avoid breaking them within single quotes [#95]
• Update the wp-config.php template [#139]

wp-cli/core-command

• Update download_package() function signature [#197]
• Support case-insensitive filesystems when pruning files after update [#196]
• Do not exit on error but pass on error [#193]

wp-cli/cron-command

• Add PHP 8.1 support [#77]
• Adapt feature test to use HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. with example.com [#78]
• Promote a non-200 response from the cron spawn test to an error [#66]

wp-cli/db-command

• Refactor --defaults flag handling [#205]
• Adapt mysqldump message string to check for in tests [#201]
• Set 'utf8mb4' when exporting without '--default-character-set' option [#199]
• Add decimal numbers to wp db size [#163]
• Add --defaults flag to remaining commands [#206]
• Add PHP 8.1 support [#214]
• Fix table existence check in db columns [#210]
• Adapt feature test to use HTTPS with example.com [#216]
• Fix “WP_DEBUG already defined” test failure [#220]

wp-cli/embed-command

• Add PHP 8.1 support [#65]

wp-cli/entity-command

• Support PHP 8.1 [#331]
• Update example input to reflect example output [#326]
• Document default post type filtering for post list command [#321]
• Correct the home URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org when listing sites [#312]
• Adapt http => https URLs [#339]
• Add application password commands [#330]
• Better error message when trying to delete super admin [#304]
• Recalculate menu order on insertion or deletion [#275]
• Add strict/no-strict mode for taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. list [#256]

wp-cli/eval-command

• Add PHP 8.1 support [#60]

wp-cli/export-command

• Ensure post attachment meta is exported correctly [#89]
• Only add needed user when filtering by --author [#88]
• Adapt tests [#87]
• Fix categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., tag and term names missing in export [#86]
• Add the_title_export filter and cdata for item title to export [#77]
• Add PHP 8.1 support [#93]
• Adapt feature test to use HTTPS with example.com [#94]

wp-cli/extension-command

• Fix test issues [#293]
• Fix incorrect examples [#290]
• Check for WP_Error on bulk updates [#294]
• Add support for PHP 8.1 [#306]
• Replace one-time-login with a sample plugin in the tests [#302]
• Add --skip-update-check flag to plugin list and theme list commands [#300]
• Ensure bundled themes don’t interfere with update tests [#311]

wp-cli/i18n-command

• Fix tests [#268]
• Add subtract-and-merge flag [#267]
• Use more inclusive language in argument description [#266]
• Add new --update-mo-files flag to make-json [#265]
• Add new --location flag to omit source code references [#264]
• Add ext-mbstring to list of suggested dependencies [#263]
• Prevent adding JS comments to multiple strings [#261]
• Fix string extraction when using template literals [#260]
• Update version constraint for mck89/peast [#259]
• Fix plural extraction in JS [#258]
• Remove now unneeded workaround in JS scanner [#256]
• Extract strings for translation from theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. [#254]
• Fix string extraction from block.json [#253]
• Add support to IterableCodeExtractor for symlinks. [#249]
• Add PHP 8.1 support [#293]
• Add new field to translate in theme.json [#292]
• Fix JS string extraction with unsupported argument type [#296]

wp-cli/import-command

• Add PHP 8.1 support [#71]

wp-cli/language-command

• Add PHP 8.1 support [#111]

wp-cli/maintenance-mode-command

• Add PHP 8.1 support [#20]

wp-cli/media-command

• Add PHP 8.1 support [#153]
• Add missing intermediate_image_sizes_advanced filter argument for WP 5.3+ [#150]

wp-cli/package-command

• Only allow secure Composer versions [#144]
• Support PHP 8.1 [#143]
• Fetch default branch for GitHub packages [#146]
• Support common default development branches [#148]

wp-cli/php-cli-tools

• Update TTY checks [#145]

wp-cli/rewrite-command

• Add PHP 8.1 support [#54]

wp-cli/role-command

• Add PHP 8.1 support [#49]

wp-cli/scaffold-command

• Fix testing on WordPress trunk version [#297]
• Ignore .github directory in .distignore [#295]
• Allow for diverging PHPUnit version specifics in tests [#304]
• Add PHP 8.1 support [#301]

wp-cli/search-replace-command

• Fix offset handling when doing chunked replacements [#162]
• Add strict comparisons for color tests [#163]
• Add PHP 8.1 support [#166]
• Adapt feature test to use HTTPS with example.com [#167]

wp-cli/server-command

• Add PHP 8.1 support [#72]

wp-cli/shell-command

• Add PHP 8.1 support [#58]

wp-cli/super-admin-command

• Add PHP 8.1 support [#48]
• Trigger core actions when granting or revoking super-admin permissions [#20]

wp-cli/widget-command

• Append new widgets to the bottom of a sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. [#52]
• Decouple tests from default theme widgets [#51]
• Add PHP 8.1 support [#53]

wp-cli/wp-config-transformer

• Adapt tests for polyfilled test case [#36]

Contributors

@bgturner, @BhargavBhandari90, @CodeProKid, @connerbw, @dd32, @dh-programacion, @dlind1, @drzraf, @felixarntz, @gedex, @gitlost, @grappler, @greatislander, @herregroen, @imadphp, @janw-me, @jenkoian, @jmdodd, @johnbillion, @johnjago, @jrfnl, @kapilpaul, @KarlAustin, @l3ku, @localheinz, @matzeeable, @mbuxsoomro, @michaelzangl, @mircobabini, @mn7zDev, @mrkaluzny, @nickdaugherty, @Nikschavan, @oandregal, @ocean90, @pbiron, @pdaalder, @petruchek, @pmbaldha, @ponsfrilus, @ryotsun, @saz, @schlessera, @seatonjiang, @siliconforks, @skeltoac, @stefanpejcic, @stodorovic, @swissspidy, @tammelin, @thomasplevy, @Tug, @tyrann0us, @UVLabs, @wojsmol, @wpamitkumar, @yousan

#release, #v2-6-0

The long-awaited release v2.5.0 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/ https://make.wordpress.org/cli/ is scheduled to be published on Wednesday, May 19th, 2021.

I won’t go into too much detail about why the release was so long in the making, but let me nevertheless add a link to an article in which Juliette Reinders Folmer eloquently talks about some of the reasons: https://24daysindecember.net/2020/12/21/a-perfect-storm/. Add to this the fact that the pandemic situation has drastically reduced the pool of contributors, as well as Travis CI deciding to effectively drop OSS support (forcing me to switch both testing and deployments to 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 be the repository owner. https://github.com/ Actions), and we’re in a situation that I’m glad will finally be resolved again soon.

Thanks to all the sponsors of the project that make it possible to work on WP-CLI with the persistence and staying power it requires.

Also big thanks to the contributors to the project that kept helping me figure out bugs and come up with solutions! I truly appreciate all your assistance.

And in case you’re one of the many people who created an issue in recent times that hasn’t been resolved yet, know that getting v2.5.0 out was an absolute priority, but I’ll slowly work off the backlog again once the pressing compatibility issues have been taken care of.

#release, #v2-5-0

‘Tis the season to celebrate a new release 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/ https://make.wordpress.org/cli/! 🎄 A total of 39 contributors has collaborated on this release to have a staggering 293 pull requests merged. We’ll go over the main areas now, but you also skip directly to the detailed changelog or ponder over the breaking changes section if you’re impatient.

i18n – round two!

The recent i18n make-pot command has replace the old make-pot tool in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and is now the official translation build tool for the Core. This effort has lead to numerous improvements to make it both more robust and more flexible. Amongst the more notable changes, it can now parse 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/. in addition to the 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. http://php.net/manual/en/intro-whatis.php. files, and together with the new i18n make-json command that lets you produce separate JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. files, you’re all set to make your GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ blocks translatable!

Translation pack improvements

We didn’t stop there with regards to making WordPress an “international success”… the language family of commands got several improvements and fixes. The most notable one is that language plugin|theme update now understands an --all flag, so you can update language packs for all your installed plugins/themes in one go.

# Update the language packs for all plugins.
$ wp language plugin update --all
Updating 'Japanese' translation for Akismet 3.1.11...
Downloading translation from https://downloads.wordpress.org/translation/plugin/akismet/3.1.11/ja.zip...
Translation updated successfully.
Updating 'Japanese' translation for Contact Forms 7 4.2.1...
https://downloads.wordpress.org/translation/plugin/contact-form-7/4.2.1/ja.zip...
Translation updated successfully.
Success: Updated 2/2 translation.

Partial prompting

The lesser known --prompt global parameter has now become even more useful. Instead of always prompting for all arguments, it skips those that were already provided, as you would probably already have expected. One way this can be used is to prefill all arguments that you can remember and then use --prompt to help you with the more arcane flags. More importantly, though, you can now prefill all the arguments that are already known inside of a script, and then add the --prompt argument to let the script query the remaining information from the user.

Manage the WP-CLI cache

We added two additional commands that let you manage the WP-CLI internal cache. cli cache clear will clear the entire cache, whereas cli cache prune will only clear the elements known to be stale. This latter will for example remove all the versions of WP core that you downloaded except for the most recent one.

# Remove all cached files.
$ wp cli cache clear
Success: Cache cleared.

# Remove all cached files except for the newest version of each one.
$ wp cli cache prune
Success: Cache pruned.

Better control over transients

You can now list the current transients on your site or network using the filterable transient list command. You can search for specific transients or exclude the ones you want to hide. You can even choose whether you want the expiration to be displayed in a human-readable or machine-parseable format.

# List all transients
$ wp transient list
+------+-------+---------------+
| name | value | expiration    |
+------+-------+---------------+
| foo  | bar   | 39 mins       |
| foo2 | bar2  | no expiration |
| foo3 | bar2  | expired       |
| foo4 | bar4  | 4 hours       |
+------+-------+---------------+

Furthermore, transients are now handled more consistently across 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.https://codex.wordpress.org/Create_A_Network. networks, and allow you to properly distinguish between regular transients and site transients.

Database management improvements

Also, the db size loved the idea of a --human-readable flag like in the transient list command so much that it got its own version. This will always use the unit that is best adapted to convey the information.

# List the size of the database in a human-readable form
$ wp db size --tables --human-readable
+---------+--------+
| Name    | Size   |
+---------+--------+
| my_site | 117 MB |
+---------+--------+

Furthermore, the db import command now understands all the flags that the mysql binary does, so that you can get past errors in SQL exports or adapt the result you want to see in your target site.

# Import an SQL export file that contains errors, by
# passing the --force argument to mysql binary.
$ wp db import export-with-errors.sql --force
Success: Imported from 'export-with-errors.sql'.

Smarter configuration

The config commands are now smarter. They not only allow you to edit the wp-config.php even on a broken WordPress installation, but you’re also able to retrieve the individual settings in whatever format best fits your scripting needs. Finally, adding new configuration values or updating existing ones will now only throw errors in the most ambiguous scenarios, while they just work for the majority use cases without the need to explicitly specify a --type.

Checking the existence of a post

You can now check whether a given post exists by using the new post exists command. It returns a shell exit code, so you can use it directly in shell conditionals.

if wp post exists 42; then
   echo "Skipping post import for ID 42, it already exists."
else
   echo "Importing post with ID 42..."
   # ...
fi

Breaking changes

• While we had already bumped the minimum PHP version in v2.0.0 and started using PHP 5.4+ code in some places, we now actively enforce this requirement in the bootstrapping code [wp-cli#5039](https://github.com/wp-cli/wp-cli/pull/5039).
• The restructuring of the packages in v2.0.0 produced a regression which caused overrides through the package manager to not work anymore. We fixed this by completely ripping the framework out of the regular Composer autoload flow. This should now lead to less surprises when rearranging the Composer compositions, but might have side-effects in some exotic Composer setups [wp-cli#5010](https://github.com/wp-cli/wp-cli/pull/5010).
• The breaking change from v2.0.1 to throw an error for non-lowercase theme slugs was reverted, as it broke far more than we anticipated. That’s why we now break the breaking change to get back to the original behavior [extension-command#137](https://github.com/wp-cli/extension-command/pull/137). 😛
• WP-CLI tries to speak proper English now. To achieve this, we changed the output to use the real world “installation” where we were using the fantasy term “install” before [wp-cli#4946](https://github.com/wp-cli/wp-cli/pull/4946).

Complete change log

wp-cli/wp-cli-bundle

• Bump PHP version to 5.4+ for PHP Compatibility Checker [#63]
• Bump included package-command to v2.0.3 [#35]
• Remove .behat-progress.log [#25]
• Use dev-master for framework instead of tagged release [#24]
• Add replace-label maintenance command [#17]

wp-cli/wp-cli

• Properly reorder synopsis passed in via $args [#5049]
• Bump PHP version check in bootstrap code to v5.4+ [#5039]
• Remove ext-posix requirement from Composer file [#5038]
• Fix override test on Composer stack [#5036]
• PHP 7.0+: allow for changed list assignment order [#5021]
• Skip associative arguments that were already provided on --prompt [#5015]
• Bump PHP version to 5.4+ for PHP Compatibility Checker [#5014]
• Use custom autoloader to load framework [#5010]
• Add extension requirements to composer.json file [#5001]
• Add ext-zip as suggested extension [#4998]
• Fix parsing of arguments for WP_CLI::runcommand() with launch=false [#4989]
• Match the way WordPress Core locates wp-config.php [#4984]
• Use dirname() instead of .. to locate wp-config.php to match Core behavior [#4963]
• Update README to account for the 280-character limit on Twitter [#4962]
• Use “installation” instead of “install” in documentation [#4960]
• Bump included package-command to v2.0.3 [#4957]
• Reattach existing subcommands from namespace to replacing command [#4951]
• Convert ‘install’ to ‘installation’ [#4946]
• Add sibling vendor folder location [#4938]
• Check and display help command if requested [#4928]
• Fix var_export return in WP_CLI::print_value [#4926]
• Adapt README.md file for v2.0.1 release [#4924]
• Bump version to 2.1.0-alpha [#4898]
• Added cli cache prune & cli cache clear commands [#4787]

wp-cli/handbook

• Add Savvii to hosting companies [#267]
• Update hosting-companies.md [#266]
• Update the set up and testing flow [#265]
• History | grep = even better than ctrl-r [#263]
• Please add One.com to the list [#261]
• Add lima-city to hosting companies [#258]
• Add 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/ or can be cost-based plugin from a third-party Simple History [#257]
• Update running-commands-remotely.md to add ~/bin approach [#256]
• Use “installation” instead of “install” [#255]
• Fix issue with broken filename [#253]
• Document root cause to STDOUT PHP notice [#252]
• Update with v2 changes [#251]
• Remove WP_CLI_Command class [#250]
• Include the cron jobs in the governance document [#248]

wp-cli/wp-cli.github.com

• Updated index.md – Spanish version [#316]
• Adapt index.md file for v2.0.1 release [#315]

wp-cli/cache-command

• Rename transient list method to be consistent with other list commands [#49]
• Introduce a list command to list all transients [#48]
• Make output of transient type generic to include multisite behaviour [#47]
• Replace usage of global with wp_using_ext_object_cache() [#45]
• Improve deleting site transients [#42]

wp-cli/checksum-command

• Use command namespaces instead of conditional addition [#54]

wp-cli/config-command

• Permit use of wp config edit when WP isn’t functional [#71]
• Use constant as default type when adding new keys [#80]
• Add --format option for config get command [#79]
• Use print_value() instead of log() for output of config get [#78]

wp-cli/core-command

• Switch to wp-cli@dev [#92]
• Adapt install => installation in tests [#90]
• Fix tests for uncached nightly downloads [#100]
• Adapt framework requirement [#101]

wp-cli/cron-command

• Make sure WP Cron is enabled for cron tests [#36]

wp-cli/db-command

• Fix comment argument test [#127]
• Adds --human-readable parameter to db size command [#124]
• Support all mysql flags while importing database [#123]
• Add search and delete example [#122]
• Add new db clean to README.md and configuration files [#119]
• Fix combination of --format & --size_format flags [#118]
• Add links to mysqlMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. documentation [#117]

wp-cli/entity-command

• Update readme [#204]
• Bump site meta test requirement to WP 5.1+ [#225]
• Add missing --description flag logic for user create [#217]
• Expose the available query variables for comment and post queries [#213]
• Use “installation” instead of “install” [#212]
• List all entities in the package description [#208]
• Bail with a warning when deleting custom post types without --force [#188]
• Add post exists command [#182]

wp-cli/eval-command

• Adapt install => installation in tests [#33]

wp-cli/extension-command

• Throw error in theme fetcher on non-lowercase slugs [#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]
• Revert “Throw error in theme fetcher on non-lowercase slugs” [#137]
• Failed plugin updates now throw errors [#143]
• Use “installation” instead of “install” [#139]
• plugin delete <plugin-name> not working if path has a space or & in it [#138]

wp-cli/i18n-command

• Require framework as hard dependency [#78]
• Add Composer config settings [#74]
• Improve detection of translator’s comments [#101]
• Improve regex replacement [#100]
• Replace regexes Peast can’t parse [#99]
• Allow skipping strings audit [#94]
• Update file-comment argument docs [#93]
• Set a placeholder PO-Revision-Date 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. [#92]
• Remove ‘foo’ file [#88]
• Include should override exclude instead of the other way around [#87]
• Support parsing minified JS files created by WebPack [#85]
• Add unit test cases for include/exclude options [#83]
• Allow passing an empty file comment [#82]
• Determine includes and excludes based on scores [#104]
• Add parsing of .js.map files to improve reliability of JS translations [#103]
• Remove second argument to WP_CLI::success() [#112]
• Normalize paths [#111]
• Normalize paths [#110]
• Add i18n make-json command [#109]

wp-cli/language-command

• Make sure upgrader strings are always in English [#54]
• Slug fixes [#53]
• Change access to activate_language() to private [#47]
• Don’t error when a translation is not yet available [#69]
• Check if array key exists to prevent undefined index notices [#67]
• Support installing translations for all installed plugins/themes [#64]
• Make use of report_batch_operation_results() for install commands [#63]
• Continue if $available_updates is not a array [#62]
• Add tests for wp site switch-language [#57]

wp-cli/media-command

• Fix SVG regeneration test by adding an XML header to fake SVG file [#98]

wp-cli/package-command

• Make tests work with both install and installation strings [#100]

wp-cli/php-cli-tools

• Use forced width attribution as fallback only to avoid scrapping manual widths [#136]
• Fix incorrect namespace for cli\notify\xxx [#137]

wp-cli/scaffold-command

• PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. template: fix XML error in ruleset [#171]
• Add textdomain to 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. strings and update tests accordingly [#187]
• Use branch for WP_TEST_TAG for RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. and betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. [#186]
• Missing text domain in post_type_extended.mustache [#184]
• Work around Travis CI issue with _s download certificate [#182]
• Fix typo in Travis config [#180]
• Ignore ‘node_modules’ in PHPCS XML file [#178]
• Allow for installation as well as install [#177]
• Fix syntax error in block-php.mustache [#176]
• Inc ‘menu_position’ when scaffolding a post type [#173]
• Remove Inflector Class [#172]
• Run docker-php-ext-install with sudo -E in CircleCI [#188]
• Split up the list of expected files to allow for WP 5.0+ changes [#195]

wp-cli/search-replace-command

• Corrects NULL export values. [#93]

wp-cli/server-command

• Set SERVER_ADDR for the built-in webserver [#49]

wp-cli/wp-config-transformer

• Add regression test for #5 [#8]
• Remove colloquialism [#6]
• Preserve leading whitespace characters on config update [#5]
• Fix regex for closing syntax in string [#9]
• Use real config filename in Exception messages [#11]

Contributors

Please give a big round of applause to these fine folks that have contributed their time and expertise to make this release possible: @abhijitrakas, @antigenius, @austinginder, @BhargavBhandari90, @birkestroem, @bitwombat, @bonny, @Calinou, @danielbachhuber, @dgroddick, @emirpprime, @fjarrett, @frozzare, @GaryJones, @Grucqq, @henrywright, @herregroen, @insomnux, @jrfnl, @KushibikiMashu, @markjaquith, @MoisesMN, @Mte90, @ocean90, @phillipp, @pmgarman, @rmccue, @siliconforks, @soulseekah, @swissspidy, @szepeviktor, @thrijith, @torounit, @tsmith1, @VladimirAus, @wojsmol, @yahilmadakiya, @yousan Thank you! ❤️

#release, #v2-1-0

This is a big one! 67 awesome contributors have collaborated over 364 pull requests 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/ https://make.wordpress.org/cli/ v2!

Before going over the detailed change log, let’s discuss a few key areas of this update in more detail. There’s also a “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 package, while the bundling has moved on to the 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 with those of v2.0.0, 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.

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.

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. 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. http://php.net/manual/en/intro-whatis.php. linting, PHP Code SnifferPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The 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. May also refer to The collection of PHP_CodeSniffer rules (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 or automatically retrying failures on Travis to make sure it was not a random intermittent timeout or similar.

New command: i18n make-pot

@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 and is even planned to replace the default translation tool bundled with WordPress Core. 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/., 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/ 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 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 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” 😉).

# 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/ 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=<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.

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

• Bundle wp-cli/i18n-command [#9]

wp-cli/wp-cli

• Add Inflector class and convenience function for pluralizing nouns [#4881]
• Adapt regular expression in make-phar test to skip wiki links [#4873]
• PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. Config Refresh [#4867]
• Fix PHP version check [#4864]
• Trigger new 'cli_init' hook during WordPress 'plugins_loaded' action. [#4861]
• add template for core-command to phar [#4854]
• Fall back to full string instead of $mode on PHP < 7 [#4853]
• Refactoring wp-cli/wp-cli to represent the framework only, not the bundle [#4851]
• Remove WP 4.4 requirement [#4845]
• Fix —skip-theme tests [#4843]
• Fix shell scripting issues in ci/deploy.sh [#4842]
• Fix shell scripting issues in bin/wp [#4841]
• Additional quoting in ci/prepare.sh [#4840]
• Lock wp-completion.bash to v1.5.1 [#4839]
• Remove Gemnasium badge, as the service was shut down [#4815]
• Use latest search-replace package to fix tests broken due to privacy policy change [#4807]
• Turn 'latest' into version number [#4806]
• Update packages to fix broken tests due to WP5.0 [#4804]
• Switch to fixed package command [#4803]
• Bump lowest PHP version to test to 5.4 [#4798]
• Add a missing accepted output format to wp cli alias [#4765]
• Improve the descriptions of the --skip-plugins and --skip-themes flags [#4759]
• Include sublinks in README.md to popular installation methods [#4756]
• ABSPATH defined [#4743]
• Skip wp_blogmeta table for back compat [#4736]
• Introduce \WP_CLI\Utils\normalize_path function. Using it for ABSPATH constant. [#4718]
• Undo temporary one-off @require-php-5.4 in bootstrap test. [#4716]
• Revert “Require minimum PHP 5.4” [#4715]
• Skip pre-commit hook in auto-composer-update [#4711]
• Revert “update wp cli info” [#4702]
• Remove : from cli update info check. [#4697]
• Only check staged files during the pre-commit PHPCS verification [#4696]
• Empty domain in framework test after get_sites_by_path change. [#4695]
• Append uniq_id() when extracting file from Phar [#4692]
• Support launching system editor with specific temp file extension [#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/. pre-commit hook. [#4622]
• Update wp cli info [#4613]

wp-cli/handbook

• Add documentation on how to troubleshoot [#243]
• Use <example.com> as placeholder [#242]
• Fix typos in <code-review.md> [#239] & [#241]
• Remove Dead Link [#238]
• Update docs for installing WP-CLI via brew [#236]
• Add quotes to the alias [#235]
• Adapt signing procedure to use proper key [#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]
• Add an updraftplus WP CLI command [#228]
• Fix grammar in documentation paragraph [#226]
• Add a LICENSE file to the repo [#224]
• Incorporate a few strategic mentions of the wp-cli/ideas repo [#223]
• Remove the wish list from the website [#222]
• Document WP_CLI_PHP_ARGS in WP-CLI config document [#221]
• Mention the Docker installing method [#220]
• Document issue of creating a post with Latin characters in title [#214]
• Add BOM in wp-config.php as a common issue. [#212]
• Add WP_CLI_PHP to Environment variables [#211]
• Fix missing quote in documentation [#210]
• Separate non-bundled install; generate against current WP-CLI instance. [#207]
• Update Daniel’s relationship to the project [#206]

wp-cli/wp-cli.github.com

• Updated <index.md> for Spanish language [#313]
• Remove Gemnasium badge [#312]
• Update pt_BR translation [#311]
• Add a LICENSE file to the repo [#309]
• Add note about only using the English version as source for translations [#308]
• Translate homepage into Spanish [#307]
• Changed http to https in all wp-cli.org links. [#305]

wp-cli/autoload-splitter

• Package is now obsolete as of v2.0.0

wp-cli/cache-command

• Adapt package for framework v2 [#32]

wp-cli/checksum-command

• Make soft changes more flexible for plugin checksums [#43]
• More flexible soft change checks (issue #34) [#41]
• Add backslash to the regex for matching Windows paths correctly [#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 be the repository owner. https://github.com/ labels [#37]
• Adapt package for framework v2 [#50]

wp-cli/config-command

• Fix library version to ^1.2.1 [#53]
• Removed leftover remove() operation [#52]
• Introduce config edit command [#48]
• Add higher timeout config value [#67]
• Adapt package for framework v2 [#66]
• Ensure file_put_contents() writes to the wp-config.php path [#63]
• Add shuffle-salts command [#62]
• Set WP_CACHE_KEY_SALT [#59]

wp-cli/core-command

• Bring template files over from wp-cli/wp-cli [#73]
• Fix mustache template file path [#77] & [#78]
• Sanitize database at the end of install to prevent duplicate data [#76]
• Adapt package for framework v2 [#81]

wp-cli/cron-command

• Adapt package for framework v2 [#29]

wp-cli/db-command

• Add db columns command [#100]
• Count users instead of posts for the smoke test [#98]
• Fix test failure due to introduction of wp_blogmeta table [#94]
• Add db clean command [#93]
• Add examples for exporting certain posts [#90]
• pass --column-statistics=0 to mysqldump command [#105]
• Add ISO size formats to db size [#104]
• Adapt package for framework v2 [#110]

wp-cli/embed-command

• Adapt package for framework v2 [#38]
• Scaffold missing top-level commands [#35]

wp-cli/entity-command

• Fix tests after Core’s introduction of a default “Privacy Policy” page [#177]
• Abstract meta CRUD into methods [#174]
• Remove duplicative --user_email=<user-email> argument [#173]
• Turn latest into actual version number [#171]
• Improve the formatting of various format parameter documentation [#168]
• Add site meta sub-command [#159]
• Add --unserialize flag to option list command [#156]
• Add --from-post=<post_id> flag to create duplicate posts [#154]
• Properly clone objects for comparison [#152]
• Fix missing quote in documentation [#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]
• Add user check-password subcommand [#144]
• Replace ‘install’ to ‘installation.’ [#187]
• Add support for --post_date_gmt in post generate [#184]
• Optional --skip-email flag for wp user update [#155]
• Adapt package for framework v2 [#192]

wp-cli/eval-command

• Adapt package for framework v2 [#27]
• Support eval-file from STDIN (implementation for #19) [#21]

wp-cli/export-command

• Start with an empty site to avoid count issues [#36]
• Adapt package for framework v2 [#44]

wp-cli/extension-command

• Add missing templates to this repository [#107]
• Replace retired themes used in tests with new ones [#105]
• Introduce theme mod list [#100]
• Refresh README.md and test suite prior to v1.1.10 release. [#89]
• Allow for modern-wordpress redirect [#85]
• Add --all flag for plugin uninstall command [#84]
• Fix mustache file paths [#109] & [#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> [#108]
• Add --all flag to plugin delete [#103]
• Adapt package for framework v2 [#116]

wp-cli/i18n-command

• Prepare for v2 release [#72]
• WordPress Core support [#69]
• Check for more mistakes in translatable strings [#64]
• Separate translation extraction from Po file writing [#63]
• Make PhpFunctionsScanner extensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. [#62]
• Separate command argument handling from actual __invoke() [#60]
• Add --headers parameter [#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]
• Print some more helpful debug messages [#56]
• Factor directory iterator as a trait [#54]
• Text domain header [#43]
• Add @when before_wp_load to command namespace [#42]
• Add option to extract strings with any text domain [#38]
• Correctly pass exclude option to JsCodeExtractor [#37]
• Add warning when a string has two different translator comments [#34]
• Exclude some common directories [#32]
• Add ability to merge with existing POT file [#31]
• JavaScript String Extraction [#26]
• Don’t try to extract anything when there are no PHP files [#24]
• Add more tests related to translator comments [#23]
• Standardize file names [#21]
• Extract all supported functions. [#13]

wp-cli/import-command

• Adapt post/page generation to make them resilient to added privacy policy page [#25]
• Adapt package for framework v2 [#30]

wp-cli/language-command

• Revert “Add plugin and theme command” [#28]
• Adapt package for framework v2 [#43]
• Use download_url() in language pack upgrader [#41]
• Enable updating languages for individual plugins and themes [#40]
• Warn if no plugin or theme has been specified [#38]
• Add is-installed command to check if a given language is installed [#36]
• Update language core update --dry-run message [#32]
• Add language plugin and language theme command. [#29]

wp-cli/media-command

• Adapt package for framework v2 [#85]
• Update examples in documentation [#81]
• Reinstate ghostscript/imagick install and fix bmp name in regenerate test. [#69]
• Document how to fetch attachment URL after import [#68]
• Clear WP object cache periodically on media regenerate/import. [#62]

wp-cli/package-command

• Assume default package name if composer.json file cannot be retrieved [#78]
• Avoid using Composer CA bundle if in phar. [#73]
• Move test-command to wp-cli-test Github organization [#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]
• Adapt package for framework v2 [#87]
• Exclude broken Composer version [#91]

wp-cli/php-cli-tools

• Remove double semi-colon [#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. in prompt() [#129]
• Fix off-by-1 error in progress bar examples [#128]
• Add optional $msg parameter to cli\Progress\Bar::tick() [#126]

wp-cli/rewrite-command

• Adapt package for framework v2 [#20]

wp-cli/role-command

• add --show-grant argument to wp cap list and --grant to wp cap add [#19]
• Add --field=<field> support to listing roles [#17]
• Adapt package for framework v2 [#23]

wp-cli/scaffold-command

• Skip PHPUnit tests for PHP 7.2+ [#145]
• Modify scaffold block to create index.js [#142]
• Fix theme-specific paths in scaffolded blocks [#137]
• Add PHP 7.2 to CI templates [#135]
• Exclude tests/test-sample.php via the phpunit.xml.dist file [#134]
• Fix sed -i option on MacOS [#132]
• Use correct default $WP_TESTS_DIR on MacOS [#131]
• Use phpunit 6.5.6 for PHP 7.2 to get around core test incompat. [#125]
• Fix WPCSWPCS The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the WordPress Coding Standards. May also be an acronym referring to the Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. in theme-tests generation [#121]
• Switch CircleCI template to CircleCI 2.0. [#115]
• Correct 'add_new_item' label [#163]
• Exclude string from escape warning [#162]
• Update PHPCS default rule set [#161]
• Add --woocommerce flag to scaffold _s command [#159]
• Add PHPCompatibility sniffssniff A module for PHP Code Sniffer 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, similar to how a dog would "sniff" out food. to scaffolded [#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]
• Remove 'wp-blocks' from style dependency [#151]
• Add function_exists() check to block PHP template [#147]
• Adapt package for framework v2 [#166]

wp-cli/search-replace-command

• Fix tests that are broken due to the addition of a “Privacy Policy” page [#78]
• Handle incomplete class (un)serialization gracefully [#76]
• Handle PCRE errors gracefully [#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.https://codex.wordpress.org/Create_A_Network. usage [#69]
• Fix broken GUID test [#81]
• Improve --regex-limit logic [#70]
• Adapt package for framework v2 [#86]
• Add --regex-limit option. [#62]

wp-cli/server-command

• Adapt package for framework v2 [#42]

wp-cli/shell-command

• Adapt package for framework v2 [#25]
• Better explain the --basic flag [#23]

wp-cli/widget-command

• Adapt package for framework v2 [#19]

Contributors

Here’s the complete list of the fantastic folks that have helped make this happen:

@2020media, @abhijitrakas, @ajitbohra, @alpipego, @austinginder, @benlk, @BhargavBhandari90, @burhandodhy, @chesio, @CodeProKid, @danielbachhuber, @drzraf, @emirpprime, @ericgopak, @erlendeide, @felicianotech, @felipeelia, @fumikito, @GaryJones, @ghost, @gitlost, @greatislander, @JanVoracek, @janw-oostendorp, @javorszky, @jblz, @jmichaelward, @johnbillion, @josephfusco, @kirtangajjar, @kshaner, @lalaithan, @lf-jeremy, @libertamohamed, @marcovalloni, @marksabbath, @miya0001, @MoisesMN, @montu1996, @NicktheGeek, @ocean90, @pdaalder, @pekapl, @pixolin, @pjeby, @pmbaldha, @ptrkcsk, @ryanjbonnell, @sagarnasit, @salcode, @sasagar, @schlessera, @spacedmonkey, @spicecadet, @stevegrunwell, @strandtc, @svenkaptein, @swissspidy, @terriann, @thrijith, @tiagohillebrandt, @tomjn, @torounit, @wojsmol, @wp-make-coffee, @yousan, @zipofar

A big thank you to all involved! ❤️

#release, #v2-0-0