This is a big one! 67 awesome contributors have collaborated over 364 pull requests to bring you WP-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
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
help (as the two “built-ins”) and
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 PHP 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 Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. checks (including the WordPress Coding Standards A collection of PHP_CodeSniffer rules (sniffs) to validate code developed for WordPress. It ensures code quality and adherence to coding conventions, especially the official standards for WordPress Core. 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.
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=4.2 composer behat. This constant also understands
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.
@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,
This can now easily be including in whatever automated tooling you use for your site/plugin 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.
- 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 UX 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:
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.
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 SSH 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
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.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/ API 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.
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 | |
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 😱!
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.
We’ve added CRUD methods
update for the “site meta 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.
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
# Check whether given credentials are valid; exit status 0 if valid, otherwise 1
$ wp user check-password admin adminpass
$ echo $?
# Bash script for checking whether given credentials are valid or not
if ! $(wp user check-password $USER $PASSWORD); then
notify-send "Invalid Credentials";
language plugin and
They both come with the following subcommands:
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
post generate can now deal with
user update now allows you to
eval-file can read from
plugin uninstall and
plugin delete can now act on
--all plugins at once
cap list can now
cap add , seeing what its list sibling had done, grew a new
role list can now print a single
scaffold _s learned the new
search-replace lets you set a
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 deployed 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 hooks 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!
Here are a few things you need to be aware of when moving from
- 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
- Add Inflector class and convenience function for pluralizing nouns [#4881]
- Adapt regular expression in
make-phar test to skip wiki links [#4873]
- PHPCS 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]
wp-cli/wp-cli to represent the framework only, not the bundle [#4851]
- Remove WP 4.4 requirement [#4845]
—skip-theme tests [#4843]
- Fix shell scripting issues in
- Fix shell scripting issues in
- Additional quoting in
wp-completion.bash to v1.5.1 [#4839]
- Remove Gemnasium badge, as the service was shut down [#4815]
- Use latest
'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-themes flags [#4759]
- Include sublinks in
README.md to popular installation methods [#4756]
ABSPATH defined [#4743]
wp_blogmeta table for back compat [#4736]
\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]
pre-commit hook in
- Revert “update
wp cli info” [#4702]
: 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]
uniq_id() when extracting file from Phar [#4692]
- Support launching system editor with specific temp file extension [#4691]
- Script to create the Git 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]
wp cli info [#4613]
- 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
- Add quotes to the alias [#235]
- Adapt signing procedure to use proper key [#232]
- Added the
optimize WP CLI 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]
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]
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]
- Updated <index.md> for Spanish language [#313]
- Remove Gemnasium badge [#312]
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]
https in all
wp-cli.org links. [#305]
- Package is now obsolete as of v2.0.0
- Adapt package for framework v2 [#32]
- 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 GitHub GitHub is a website that offers online implementation of git repositories that can 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]
- Fix library version to
- Removed leftover
remove() operation [#52]
config edit command [#48]
- Add higher timeout config value [#67]
- Adapt package for framework v2 [#66]
file_put_contents() writes to the
wp-config.php path [#63]
shuffle-salts command [#62]
- Bring template files over from
- 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]
- Adapt package for framework v2 [#29]
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]
db clean command [#93]
- Add examples for exporting certain posts [#90]
mysqldump command [#105]
- Add ISO size formats to
db size [#104]
- Adapt package for framework v2 [#110]
- Adapt package for framework v2 [#38]
- Scaffold missing top-level commands [#35]
- Abstract meta CRUD into methods [#174]
- Remove duplicative
--user_email=<user-email> argument [#173]
latest into actual version number [#171]
- Improve the formatting of various format parameter documentation [#168]
site meta sub-command [#159]
--unserialize flag to
option list command [#156]
--from-post=<post_id> flag to create duplicate posts [#154]
- Properly clone objects for comparison [#152]
- Fix missing quote in documentation [#147]
- Fix category The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. list count [#146]
user check-password subcommand [#144]
- Replace ‘install’ to ‘installation.’ [#187]
- Add support for
post generate [#184]
--skip-email flag for
wp user update [#155]
- Adapt package for framework v2 [#192]
- Adapt package for framework v2 [#27]
STDIN (implementation for #19) [#21]
- Start with an empty site to avoid count issues [#36]
- Adapt package for framework v2 [#44]
- Add missing templates to this repository [#107]
- Replace retired themes used in tests with new ones [#105]
theme mod list [#100]
README.md and test suite prior to
v1.1.10 release. [#89]
- Allow for
modern-wordpress redirect [#85]
--all flag for
plugin uninstall command [#84]
- Fix mustache file paths [#109] & [#112]
- Search: Add plugin or theme’s URL 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]
--all flag to
plugin delete [#103]
- Adapt package for framework v2 [#116]
- 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]
PhpFunctionsScanner extensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. [#62]
- Separate command argument handling from actual
--headers parameter [#58]
X-Generator header 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]
@when before_wp_load to command namespace [#42]
- Add option to extract strings with any text domain [#38]
- Correctly pass
exclude option to
- 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]
- 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]
- Adapt package for framework v2 [#30]
- Revert “Add plugin and theme command” [#28]
- Adapt package for framework v2 [#43]
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]
is-installed command to check if a given language is installed [#36]
language core update --dry-run message [#32]
language plugin and
language theme command. [#29]
- Adapt package for framework v2 [#85]
- Update examples in documentation [#81]
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]
- Assume default package name if
composer.json file cannot be retrieved [#78]
- Avoid using Composer CA bundle if in phar. [#73]
wp-cli-test Github organization [#66]
- Extract SSL 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]
- Remove double semi-colon [#130]
- Fix potential endless loop 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
- Fix off-by-1 error in progress bar examples [#128]
- Add optional
$msg parameter to
- Adapt package for framework v2 [#20]
--show-grant argument to
wp cap list and
wp cap add [#19]
--field=<field> support to listing roles [#17]
- Adapt package for framework v2 [#23]
- Skip PHPUnit tests for PHP 7.2+ [#145]
scaffold block to create
- Fix theme-specific paths in scaffolded blocks [#137]
- Add PHP 7.2 to CI templates [#135]
tests/test-sample.php via the phpunit.xml.dist file [#134]
sed -i option on MacOS [#132]
- Use correct default
$WP_TESTS_DIR on MacOS [#131]
phpunit 6.5.6 for PHP 7.2 to get around core test incompat. [#125]
- Fix WPCS A collection of PHP_CodeSniffer rules (sniffs) to validate code developed for WordPress. It ensures code quality and adherence to coding conventions, especially the official standards for WordPress Core. in theme-tests generation [#121]
- Switch CircleCI template to CircleCI 2.0. [#115]
'add_new_item' label [#163]
- Exclude string from escape warning [#162]
- Update PHPCS default rule set [#161]
--woocommerce flag to
scaffold _s command [#159]
- Add PHPCompatibility sniffs 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 block 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]
'wp-blocks' from style dependency [#151]
function_exists() check to block PHP template [#147]
- Adapt package for framework v2 [#166]
- Handle incomplete class (un)serialization gracefully [#76]
- Handle PCRE errors gracefully [#75]
- Remove “Site Not Found” message from multisite 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]
--regex-limit logic [#70]
- Adapt package for framework v2 [#86]
--regex-limit option. [#62]
- Adapt package for framework v2 [#42]
- Adapt package for framework v2 [#25]
- Better explain the
--basic flag [#23]
- Adapt package for framework v2 [#19]
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! ❤️