Checks whether a specific constant or variable exists in the wp-config.php file.
- Name of the wp-config.php constant or variable.
- Type of the config value to set. Defaults to ‘all’.
- Specify the file path to the config file to be checked. Defaults to the root of the WordPress installation and the filename “wp-config.php”.
# Check whether the DB_PASSWORD constant exists in the wp-config.php file. $ wp config has DB_PASSWORD
GLOBAL PARAMETERS GLOBAL PARAMETERS
These global parameters have the same behavior across all commands and affect how WP-CLI interacts with WordPress.
||Path to the WordPress files.|
||Pretend request came from given URL. In multisite, this argument is how the target site is specified.|
||Perform operation against a remote server over SSH (or a container using scheme of “docker”, “docker-compose”, “docker-compose-run”, “vagrant”).|
||Perform operation against a remote WordPress installation over HTTP.|
||Set the WordPress user.|
||Skip loading all plugins, or a comma-separated list of plugins. Note: mu-plugins are still loaded.|
||Skip loading all themes, or a comma-separated list of themes.|
||Skip loading all installed packages.|
||Load PHP file before running the command (may be used more than once).|
||Execute PHP code before running the command (may be used more than once).|
||Load WordPress in a given context.|
||Whether to colorize the output.|
||Show all PHP errors and add verbosity to WP-CLI output. Built-in groups include: bootstrap, commandfactory, and help.|
||Prompt the user to enter values for all command arguments, or a subset specified as comma-separated values.|
||Suppress informational messages.|
Command documentation is regenerated at every release. To add or update an example, please submit a pull request against the corresponding part of the codebase.