WP-CLI command which checks the existence of PHP extensions needed to run WordPress.
Quick links: Using | Installing | Contributing | Support
This package implements the following commands:
Checks the existence of extensions that are required to run WordPress.
Example output:
$ wp ext required
+-----------+-----------+
| extension | installed |
+-----------+-----------+
| curl | 1 |
| date | 1 |
| dom | 1 |
| filter | 1 |
| ftp | 1 |
| gd | 1 |
| hash | 1 |
| iconv | 1 |
| json | 1 |
| libxml | 1 |
| mbstring | 1 |
| mysqli | 1 |
| openssl | 1 |
| pcre | 1 |
| posix | 1 |
| SimpleXML | 1 |
| sockets | 1 |
| SPL | 1 |
| tokenizer | 1 |
| xml | 1 |
| xmlreader | 1 |
| zlib | 1 |
+-----------+-----------+
Success: All required extensions are installed
Checks the existence of extensions that are recommended to run WordPress.
Example output:
$ wp ext recommended
+-----------+-----------+
| extension | installed |
+-----------+-----------+
| gmagick | |
| ssh2 | |
| exif | 1 |
| imagick | 1 |
+-----------+-----------+
Error: Some recommended extensions are not installed
Checks the existence of all extensions that are either required or recommended to run WordPress.
Example output:
$ wp ext check
+-----------+-----------+
| extension | installed |
+-----------+-----------+
| gmagick | |
| ssh2 | |
| curl | 1 |
| date | 1 |
| dom | 1 |
| exif | 1 |
| filter | 1 |
| ftp | 1 |
| gd | 1 |
| hash | 1 |
| iconv | 1 |
| imagick | 1 |
| json | 1 |
| libxml | 1 |
| mbstring | 1 |
| mysqli | 1 |
| openssl | 1 |
| pcre | 1 |
| posix | 1 |
| SimpleXML | 1 |
| sockets | 1 |
| SPL | 1 |
| tokenizer | 1 |
| xml | 1 |
| xmlreader | 1 |
| zlib | 1 |
+-----------+-----------+
Error: Some extensions are not installed
Installing this package requires WP-CLI's latest stable release. Update to the latest stable release with wp cli update.
Once you've done so, you can install this package with:
wp package install [email protected]:johnbillion/ext.git
We appreciate you taking the initiative to contribute to this project.
Contributing isn’t limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation.
For a more thorough introduction, check out WP-CLI's guide to contributing. This package follows those policy and guidelines.
Think you’ve found a bug? We’d love for you to help us get it fixed.
Before you create a new issue, you should search existing issues to see if there’s an existing resolution to it, or if it’s already been fixed in a newer version.
Once you’ve done a bit of searching and discovered there isn’t an open or fixed issue for your bug, please create a new issue. Include as much detail as you can, and clear steps to reproduce if possible. For more guidance, review our bug report documentation.
Want to contribute a new feature? Please first open a new issue to discuss whether the feature is a good fit for the project.
Once you've decided to commit the time to seeing your pull request through, please follow our guidelines for creating a pull request to make sure it's a pleasant experience. See "Setting up" for details specific to working on this package locally.
GitHub issues aren't for general support questions, but there are other venues you can try: https://wp-cli.org/#support