Wala shell

Advanced PHP File Manager

Server IP: 127.0.0.1 | PHP Version: 8.3.30 | Domains Hosted: 54

Name	Size	Last Modified
📁 ..	-	2026-03-21 17:12
📄 check-autoload-options-size.feature Feature: Check the size of autoloaded options Scenario: Verify check description Given an empty directory When I run `wp doctor list --fields=name,description` Then STDOUT should be a table containing rows: \| name \| description \| \| autoload-options-size \| Warns when autoloaded options size exceeds threshold of 900 kb. \| Scenario: Autoloaded options are less than 900 kb Given a WP install When I run `wp doctor check autoload-options-size --fields=name,status` Then STDOUT should be a table containing rows: \| name \| status \| \| autoload-options-size \| success \| When I run `wp doctor check autoload-options-size --fields=message` Then STDOUT should contain: """ is less than threshold (900kb) """ @less-than-wp-6.5 Scenario: Autoloaded options are greater than 900 kb Given a WP install And a explode-options.php file: """ <?php $value = str_pad( '9', 15000, '9' ); for( $i = 0; $i < 75; $i++ ) { update_option( 'foobar' . $i, $value ); } """ And I run `wp eval-file explode-options.php` When I run `wp doctor check autoload-options-size --fields=name,status` Then STDOUT should be a table containing rows: \| name \| status \| \| autoload-options-size \| warning \| When I run `wp doctor check autoload-options-size --fields=message` Then STDOUT should contain: """ exceeds threshold (900kb) """ Scenario: Custom configuration Given a WP install And a custom.yml file: """ autoload-options-size: class: WP_CLI\Doctor\Check\Autoload_Options_Size options: threshold_kb: 800 """ When I run `wp doctor check autoload-options-size --fields=message --config=custom.yml` Then STDOUT should contain: """ is less than threshold (800kb) """	2.01 KB	2025-09-06 07:07
📄 check-cache-flush.feature Feature: Check if wp_cache_flush() function is used inside wp-content directory Scenario: Detect wp_cache_flush() Given a WP install And a wp-content/mu-plugins/plugin.php file: """ <?php wp_cache_flush(); """ When I run `wp doctor check cache-flush` Then STDOUT should contain: """ cache-flush """ And STDOUT should contain: """ warning """ And STDOUT should contain: """ Use of wp_cache_flush() detected """ And STDOUT should contain: """ mu-plugins/plugin.php """	595 B	2025-09-06 07:07
📄 check-constant-definition.feature Feature: Check the values of defined constants Scenario: Verify check description Given an empty directory When I run `wp doctor list --fields=name,description` Then STDOUT should be a table containing rows: \| name \| description \| \| constant-savequeries-falsy \| Confirms expected state of the SAVEQUERIES constant. \| \| constant-wp-debug-falsy \| Confirms expected state of the WP_DEBUG constant. \| Scenario: WP_DEBUG is defined to false Given a WP install And a wp-debug-true.php file: """ <?php define( 'WP_DEBUG', true ); """ When I run `wp doctor check constant-wp-debug-falsy` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| constant-wp-debug-falsy \| success \| Constant 'WP_DEBUG' is defined falsy. \| When I try `wp doctor check constant-wp-debug-falsy --require=wp-debug-true.php` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| constant-wp-debug-falsy \| error \| Constant 'WP_DEBUG' is defined 'true' but expected to be falsy. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 Scenario: SAVEQUERIES is defined to falsy Given a WP install And a savequeries-false.php file: """ <?php define( 'SAVEQUERIES', false ); """ And a savequeries-true.php file: """ <?php define( 'SAVEQUERIES', true ); """ When I run `wp doctor check constant-savequeries-falsy` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| constant-savequeries-falsy \| success \| Constant 'SAVEQUERIES' is undefined. \| When I run `wp doctor check constant-savequeries-falsy --require=savequeries-false.php` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| constant-savequeries-falsy \| success \| Constant 'SAVEQUERIES' is defined falsy. \| When I try `wp doctor check constant-savequeries-falsy --require=savequeries-true.php` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| constant-savequeries-falsy \| error \| Constant 'SAVEQUERIES' is defined 'true' but expected to be falsy. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 Scenario: Expected constant is defined Given a WP install And a config.yml file: """ constant-db-host-defined: class: WP_CLI\Doctor\Check\Constant_Definition options: constant: DB_HOST defined: true """ When I run `wp doctor check constant-db-host-defined --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| constant-db-host-defined \| success \| Constant 'DB_HOST' is defined. \| Scenario: Expected constant is missing Given a WP install And a config.yml file: """ constant-foobar-true: class: WP_CLI\Doctor\Check\Constant_Definition options: constant: FOOBAR value: true """ When I try `wp doctor check constant-foobar-true --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| constant-foobar-true \| error \| Constant 'FOOBAR' is undefined but expected to be 'true'. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 Scenario: Expected constant is defined as the correct value Given a WP install And a config.yml file: """ constant-foobar-true: class: WP_CLI\Doctor\Check\Constant_Definition options: constant: FOOBAR value: true """ And a wp-content/mu-plugins/constant.php file: """ <?php define( 'FOOBAR', true ); """ When I run `wp doctor check constant-foobar-true --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| constant-foobar-true \| success \| Constant 'FOOBAR' is defined 'true'. \|	4.79 KB	2025-09-06 07:07
📄 check-core-update.feature Feature: Check whether WordPress is up to date Scenario: Verify check description Given an empty directory When I run `wp doctor list --fields=name,description` Then STDOUT should be a table containing rows: \| name \| description \| \| core-update \| Errors when new WordPress minor release is available; warns for major release. \| Scenario: WordPress is up to date Given a WP install And a setup.php file: """ <?php global $wp_version; $obj = new stdClass; $obj->updates = []; $obj->last_checked = strtotime( '1 January 2099' ); $obj->version_checked = $wp_version; $obj->translations = []; set_site_transient( 'update_core', $obj ); """ And I run `wp eval-file setup.php` When I run `wp doctor check core-update` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| core-update \| success \| WordPress is at the latest version. \| @require-wp-6.0 @require-php-7.0 Scenario: WordPress has a new minor version but no new major version Given a WP install And I run `wp theme delete --all --force` And I run `wp theme install twentytwelve --activate` When I run `(curl -s https://api.wordpress.org/core/version-check/1.7/ \| jq -r ".offers[0].new_bundled" \| cut -d '.' -f 1,2)` Then save STDOUT as {LATEST_WP_VERSION} When I run `wp core download --version={LATEST_WP_VERSION} --force` Then STDOUT should contain: """ Success: WordPress downloaded. """ When I try `wp doctor check core-update` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| core-update \| error \| Updating to WordPress' newest minor version is strongly recommended. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 @require-mysql Scenario: WordPress has a new major version but no new minor version Given a WP install And I run `wp theme delete --all --force` And I run `wp theme install twentytwelve --activate` And I run `wp core download --version=5.9.10 --force` When I run `wp core update --minor` Then STDOUT should contain: """ Success: WordPress updated successfully. """ And the return code should be 0 When I try `wp doctor check core-update` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| core-update \| warning \| A new major version of WordPress is available for update. \| And the return code should be 0	2.83 KB	2025-09-06 07:07
📄 check-core-verify-checksums.feature Feature: Check whether WordPress core verifies against its checksums Scenario: Verify check description Given an empty directory When I run `wp doctor list --fields=name,description` Then STDOUT should be a table containing rows: \| name \| description \| \| core-verify-checksums \| Verifies WordPress files against published checksums; errors on failure. \| Scenario: WordPress verifies against checksums Given a WP install When I run `wp doctor check core-verify-checksums` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| core-verify-checksums \| success \| WordPress verifies against its checksums. \| Scenario: WordPress doesn't verify against checksums Given a WP install When I run `sed -i.bak s/WordPress/Wordpress/g readme.html` Then STDERR should be empty When I try `wp doctor check core-verify-checksums` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| core-verify-checksums \| error \| WordPress doesn't verify against its checksums. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1	1.39 KB	2025-05-25 12:40
📄 check-cron-count.feature Feature: Check total number of cron entries Background: Given a WP install Scenario: Verify check description When I run `wp doctor list --fields=name,description` Then STDOUT should be a table containing rows: \| name \| description \| \| cron-count \| Errors when there's an excess of 50 total cron jobs registered. \| Scenario: Cron check is healthy against a normal WordPress install When I run `wp doctor check cron-count` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| cron-count \| success \| Total number of cron jobs is within normal operating expectations. \| Scenario: Cron check errors with excess total crons Given a wp-content/mu-plugins/plugin.php file: """ <?php for ( $i=0; $i < 55; $i++ ) { // WP Cron doesn't permit registering two at the same time // so we need to distribute these crons against a spread of time wp_schedule_event( time() + ( $i * 3 ), 'hourly', 'too_many_crons_hook' ); } """ When I try `wp doctor check cron-count` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| cron-count \| error \| Total number of cron jobs exceeds expected threshold. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1	1.62 KB	2025-05-25 12:40
📄 check-cron-duplicates.feature Feature: Check for excess duplicate cron entries Background: Given a WP install And a wp-debug.php file: """ <?php define( 'WP_DEBUG', true ); """ And a wp-cli.yml file: """ require: - wp-debug.php """ Scenario: Verify check description When I run `wp doctor list --fields=name,description` Then STDOUT should be a table containing rows: \| name \| description \| \| cron-duplicates \| Errors when there's an excess of 10 duplicate cron jobs registered. \| Scenario: Cron check is healthy against a normal WordPress install When I run `wp doctor check cron-duplicates` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| cron-duplicates \| success \| All cron job counts are within normal operating expectations. \| And STDERR should be empty Scenario: Cron check errors with excess duplicate crons Given a wp-content/mu-plugins/plugin.php file: """ <?php for ( $i=0; $i < 55; $i++ ) { // WP Cron doesn't permit registering two at the same time // so we need to distribute these crons against a spread of time wp_schedule_event( time() + ( $i * 3 ), 'hourly', 'too_many_crons_hook' ); } """ When I try `wp doctor check cron-duplicates` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| cron-duplicates \| error \| Detected 10 or more of the same cron job. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1	1.82 KB	2025-05-25 12:40
📄 check-file-contents.feature Feature: Check files in a WordPress install Scenario: Verify check description Given an empty directory When I run `wp doctor list --fields=name,description` Then STDOUT should be a table containing rows: \| name \| description \| \| file-eval \| Checks files on the filesystem for regex pattern `eval\(.base64_decode\(.`. \| Scenario: Check for use of eval(base64_decode()) in files Given a WP install When I run `wp doctor check file-eval` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| file-eval \| success \| All 'php' files passed check for 'eval\(.base64_decode\(.'. \| Given a wp-content/plugins/exploited.php file: """ <?php // Plugin Name: Example Plugin eval( base64_decode( $_POST ) ); """ When I try `wp doctor check file-eval` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| file-eval \| error \| 1 'php' file failed check for 'eval\(.base64_decode\(.'. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 Scenario: Check for the use of sessions Given a WP install And a config.yml file: """ file-sessions: check: File_Contents options: regex: .(session_start\|\$_SESSION). only_wp_content: true """ When I run `wp doctor check file-sessions --config=config.yml --format=json` Then STDOUT should be JSON containing: """ [{"name":"file-sessions","status":"success","message":"All 'php' files passed check for '.(session_start\|\\$_SESSION).'."}] """ Given a wp-content/mu-plugins/sessions1.php file: """ <?php session_start(); """ And a wp-content/mu-plugins/sessions2.php file: """ <?php echo ''; $_SESSION['foo'] = 'bar'; """ When I try `wp doctor check file-sessions --config=config.yml --format=json` Then STDOUT should be JSON containing: """ [{"name":"file-sessions","status":"error","message":"2 'php' files failed check for '.(session_start\|\\$_SESSION).'."}] """ And STDERR should be empty And the return code should be 1 Scenario: Check for use of $_SERVER['SERVER_NAME'] in wp-config.php Given a WP install And a config.yml file: """ file-server-name-wp-config: check: File_Contents options: regex: define\(.+WP_(HOME\|SITEURL).+\$_SERVER.+SERVER_NAME path: wp-config.php """ And a wp-content/mu-plugins/ignored-define.php file: """ <?php @define( 'WP_SITEURL', $_SERVER['SERVER_NAME'] ); """ When I run `wp doctor check file-server-name-wp-config --config=config.yml --format=json` Then STDOUT should be JSON containing: """ [{"name":"file-server-name-wp-config","status":"success","message":"All 'php' files passed check for 'define\\(.+WP_(HOME\|SITEURL).+\\$_SERVER.+SERVER_NAME'."}] """ Given a prepend-siteurl.php file: """ <?php $contents = file_get_contents( dirname( __FILE__ ) . '/wp-config.php' ); $contents = str_replace( '<?php', '<?php' . PHP_EOL . "@define( 'WP_SITEURL', \$_SERVER['SERVER_NAME'] );", $contents ); file_put_contents( dirname( __FILE__ ) . '/wp-config.php', $contents ); """ When I run `wp eval-file prepend-siteurl.php --skip-wordpress` Then STDERR should be empty When I run `cat wp-config.php` Then STDOUT should contain: """ <?php @define( 'WP_SITEURL', $_SERVER['SERVER_NAME'] ); """ When I try `wp doctor check file-server-name-wp-config --config=config.yml --format=json` Then STDOUT should be JSON containing: """ [{"name":"file-server-name-wp-config","status":"error","message":"1 'php' file failed check for 'define\\(.+WP_(HOME\|SITEURL).+\\$_SERVER.+SERVER_NAME'."}] """ And STDERR should be empty And the return code should be 1 Scenario: Check for the successful use of the exist flag Given a WP install And a config.yml file: """ file-content-exist: check: File_Contents options: regex: .wp-doctor-exists-test. only_wp_content: true exists: true """ When I try `wp doctor check file-content-exist --config=config.yml --format=json` Then STDOUT should be JSON containing: """ [{"name":"file-content-exist","status":"error","message":"0 'php' files passed check for '.wp-doctor-exists-test.'."}] """ And STDERR should be empty And the return code should be 1 Given a wp-content/mu-plugins/wp-doctor-exist-test.php file: """ <?php //wp-doctor-exists-test """ When I run `wp doctor check file-content-exist --config=config.yml --format=json` Then STDOUT should be JSON containing: """ [{"name":"file-content-exist","status":"success","message":"1 'php' file passed check for '.wp-doctor-exists-test.'."}] """	5.25 KB	2025-09-06 07:07
📄 check-file-type.feature Feature: Check the type of file Scenario: Check that object-cache.php isn't a symlink Given a WP install And a config.yml file: """ file-object-cache-symlink: check: File_Type options: path: wp-content/object-cache.php symlink: false """ When I run `wp doctor check file-object-cache-symlink --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| file-object-cache-symlink \| success \| All 'php' files passed assertion that symlink is 'false'. \| Given a wp-content/test.php file: """ <?php """ And I run `ln -s wp-content/test.php wp-content/object-cache.php` When I try `wp doctor check file-object-cache-symlink --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| file-object-cache-symlink \| error \| 1 'php' file failed assertion that symlink is 'false'. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 Scenario: Check that object-cache.php is a symlink Given a WP install And a config.yml file: """ file-object-cache-symlink: check: File_Type options: path: wp-content/object-cache.php symlink: true """ And a wp-content/object-cache.php file: """ <?php """ When I try `wp doctor check file-object-cache-symlink --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| file-object-cache-symlink \| error \| 1 'php' file failed assertion that symlink is 'true'. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 Given a wp-content/test.php file: """ <?php """ And I run `rm wp-content/object-cache.php` And I run `ln -s wp-content/test.php wp-content/object-cache.php` When I run `wp doctor check file-object-cache-symlink --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| file-object-cache-symlink \| success \| All 'php' files passed assertion that symlink is 'true'. \|	2.58 KB	2025-05-25 12:40
📄 check-language-update.feature Feature: Check whether languages are up to date Scenario: Verify check description Given an empty directory When I run `wp doctor list --fields=name,description` Then STDOUT should be a table containing rows: \| name \| description \| \| language-update \| Warns when there are language updates available. \| Scenario: Languages are up to date Given a WP install When I run `wp doctor check language-update` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| language-update \| success \| Languages are up to date. \|	669 B	2026-03-21 17:12
📄 check-network-required-plugins.feature Feature: Check required network plugins Scenario: Verify check description Given an empty directory And a config.yml file: """ network-required-plugins: check: Network_Required_Plugins options: plugins: - akismet """ When I try `wp doctor list --fields=name,description --config=config.yml` Then STDOUT should be a table containing rows: \| name \| description \| \| network-required-plugins \| Errors when required plugins are not network-activated. \| Scenario: Required plugin is not network-activated Given a WP multisite installation And a config.yml file: """ network-required-plugins: check: Network_Required_Plugins options: plugins: - akismet """ When I try `wp doctor check network-required-plugins --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| network-required-plugins \| error \| Required network plugin check failed. Not network-activated: akismet (inactive). \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 Scenario: Required plugin is network-activated Given a WP multisite installation And a config.yml file: """ network-required-plugins: check: Network_Required_Plugins options: plugins: - akismet """ And I run `wp plugin activate akismet --network` When I run `wp doctor check network-required-plugins --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| network-required-plugins \| success \| All required plugins are network-activated. \|	2 KB	2026-03-21 17:12
📄 check-network-site-count.feature Feature: Check multisite network site count Scenario: Verify check description Given an empty directory And a config.yml file: """ network-site-count: check: Network_Site_Count """ When I try `wp doctor list --fields=name,description --config=config.yml` Then STDOUT should be a table containing rows: \| name \| description \| \| network-site-count \| Warns when multisite network site count is outside the range 1-500. \| Scenario: Site count is within expected range Given a WP multisite installation And a config.yml file: """ network-site-count: check: Network_Site_Count options: minimum: 1 maximum: 10 """ When I run `wp doctor check network-site-count --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| network-site-count \| success \| Network has 1 sites; expected between 1 and 10. \| Scenario: Site count is outside expected range Given a WP multisite installation And a config.yml file: """ network-site-count: check: Network_Site_Count options: minimum: 2 maximum: 10 """ When I run `wp doctor check network-site-count --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| network-site-count \| warning \| Network has 1 sites; expected between 2 and 10. \|	1.64 KB	2026-03-21 17:12
📄 check-network-site-option-value.feature Feature: Check the value of a network option Scenario: Verify check description Given an empty directory And a config.yml file: """ network-registration: check: Network_Site_Option_Value options: option: registration value: none """ When I try `wp doctor list --fields=name,description --config=config.yml` Then STDOUT should be a table containing rows: \| name \| description \| \| network-registration \| Confirms the expected value of the network option 'registration'. \| Scenario: Check the value of a network option Given a WP multisite installation And a config.yml file: """ network-registration: check: Network_Site_Option_Value options: option: registration value: all """ And I run `wp eval 'update_site_option( "registration", "none" );'` When I try `wp doctor check network-registration --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| network-registration \| error \| Network option 'registration' is 'none' but expected to be 'all'. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 When I run `wp eval 'update_site_option( "registration", "all" );'` Then STDOUT should be empty When I run `wp doctor check network-registration --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| network-registration \| success \| Network option 'registration' is 'all' as expected. \| Scenario: Check value_is_not for a network option Given a WP multisite installation And a config.yml file: """ network-registration: check: Network_Site_Option_Value options: option: registration value_is_not: none """ And I run `wp eval 'update_site_option( "registration", "none" );'` When I try `wp doctor check network-registration --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| network-registration \| error \| Network option 'registration' is 'none' and expected not to be. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 When I run `wp eval 'update_site_option( "registration", "all" );'` Then STDOUT should be empty When I run `wp doctor check network-registration --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| network-registration \| success \| Network option 'registration' is not 'none' as expected. \| Scenario: Gracefully render array values in error messages Given a WP multisite installation And a config.yml file: """ network-registration: check: Network_Site_Option_Value options: option: registration value: none """ And I run `wp eval 'update_site_option( "registration", array( "users" => "all" ) );'` When I try `wp doctor check network-registration --config=config.yml` Then STDOUT should contain: """ Network option 'registration' is '{"users":"all"}' but expected to be 'none'. """ And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1	3.77 KB	2026-03-21 17:12
📄 check-option-value.feature Feature: Check the value of a given option Scenario: Verify check description Given an empty directory When I run `wp doctor list --fields=name,description` Then STDOUT should be a table containing rows: \| name \| description \| \| option-blog-public \| Confirms the expected value of the 'blog_public' option. \| Scenario: Check the value of blog_public Given a WP install And a blog-private.yml file: """ option-blog-private: check: Option_Value options: option: blog_public value: 0 """ And a blog-public.yml file: """ option-blog-public: check: Option_Value options: option: blog_public value: 1 """ When I run `wp option update blog_public 1` Then STDOUT should contain: """ Success: """ When I try `wp doctor check --config=blog-private.yml option-blog-private` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| option-blog-private \| error \| Site is public but expected to be private. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 When I run `wp doctor check --config=blog-public.yml option-blog-public` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| option-blog-public \| success \| Site is public as expected. \| When I run `wp option update blog_public 0` Then STDOUT should contain: """ Success: """ When I try `wp doctor check --config=blog-public.yml option-blog-public` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| option-blog-public \| error \| Site is private but expected to be public. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 When I run `wp doctor check --config=blog-private.yml option-blog-private` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| option-blog-private \| success \| Site is private as expected. \| Scenario: Check the value of admin_email Given a WP install And a config.yml file: """ option-admin-email: check: Option_Value options: option: admin_email value: foo@example.org """ When I try `wp doctor check --config=config.yml option-admin-email` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| option-admin-email \| error \| Option 'admin_email' is 'admin@example.com' but expected to be 'foo@example.org'. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 When I run `wp option update admin_email foo@example.org` Then STDOUT should contain: """ Success: """ When I run `wp doctor check --config=config.yml option-admin-email` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| option-admin-email \| success \| Option 'admin_email' is 'foo@example.org' as expected. \| Scenario: Check the value_is_not of admin_email Given a WP install And a config.yml file: """ option-admin-email: check: Option_Value options: option: admin_email value_is_not: foo@example.org """ When I run `wp doctor check --config=config.yml option-admin-email` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| option-admin-email \| success \| Option 'admin_email' is not 'foo@example.org' as expected. \| When I run `wp option update admin_email foo@example.org` Then STDOUT should contain: """ Success: """ When I try `wp doctor check --config=config.yml option-admin-email` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| option-admin-email \| error \| Option 'admin_email' is 'foo@example.org' and expected not to be. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 Scenario: Check the value of users_can_register Given a WP install And a config.yml file: """ option-users-can-register: check: Option_Value options: option: users_can_register value: 0 """ And I run `wp option update users_can_register 1` When I try `wp doctor check --config=config.yml option-users-can-register` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| option-users-can-register \| error \| Option 'users_can_register' is '1' but expected to be '0'. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 When I run `wp option update users_can_register 0` Then STDOUT should contain: """ Success: """ When I run `wp doctor check --config=config.yml option-users-can-register` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| option-users-can-register \| success \| Option 'users_can_register' is '0' as expected. \| Scenario: Error if value and value_is_not are both used Given a WP install And a config.yml file: """ option-users-can-register: check: Option_Value options: option: users_can_register value: 0 value_is_not: 1 """ When I try `wp doctor check --config=config.yml option-users-can-register` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| option-users-can-register \| error \| You must use either "value" or "value_is_not". \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1	6.78 KB	2025-05-25 12:40
📄 check-php-in-upload.feature Feature: Check for presence of .php files in the uploads folder Scenario: Detect PHP files Given a WP install And a wp-content/uploads/malicious.php file: """ <?php some_malicious_code(); ?> """ When I run `wp doctor check php-in-upload` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| php-in-upload \| warning \| PHP files detected in the Uploads folder. \|	478 B	2025-05-25 12:40
📄 check-plugin-active-count.feature Feature: Check whether a high number of plugins are activated Scenario: Verify check description Given an empty directory When I run `wp doctor list --fields=name,description` Then STDOUT should be a table containing rows: \| name \| description \| \| plugin-active-count \| Warns when there are greater than 80 plugins activated. \| Scenario: Less than threshold plugins are active Given a WP install And I run `wp plugin activate --all` When I run `wp doctor check plugin-active-count` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| plugin-active-count \| success \| Number of active plugins (2) is less than threshold (80). \| # WordPress Importer requirement. @require-wp-5.2 Scenario: Greater than threshold plugins are active Given a WP install And a config.yml file: """ plugin-active-count: class: WP_CLI\Doctor\Check\Plugin_Active_Count options: threshold_count: 3 """ And I run `wp plugin install debug-bar wordpress-importer` And I run `wp plugin activate --all` When I run `wp doctor check plugin-active-count --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| plugin-active-count \| warning \| Number of active plugins (4) exceeds threshold (3). \| Scenario: Include network-enabled plugins in active plugin count Given a WP multisite installation And I run `wp plugin activate --network --all` When I run `wp doctor check plugin-active-count` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| plugin-active-count \| success \| Number of active plugins (2) is less than threshold (80). \|	2.03 KB	2026-03-21 17:12
📄 check-plugin-deactivated.feature Feature: Check whether a high percentage of plugins are deactivated Scenario: Verify check description Given an empty directory When I run `wp doctor list --fields=name,description` Then STDOUT should be a table containing rows: \| name \| description \| \| plugin-deactivated \| Warns when greater than 40% of plugins are deactivated. \| # WordPress Importer requirement. @require-wp-5.2 Scenario: All plugins are activated Given a WP install And I run `wp plugin install debug-bar wordpress-importer` And I run `wp plugin activate --all` When I run `wp doctor check plugin-deactivated` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| plugin-deactivated \| success \| Less than 40 percent of plugins are deactivated. \| # WordPress Importer requirement. @require-wp-5.2 Scenario: Too many plugins are deactivated Given a WP install And I run `wp plugin install debug-bar wordpress-importer` When I run `wp doctor check plugin-deactivated` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| plugin-deactivated \| warning \| Greater than 40 percent of plugins are deactivated. \| # WordPress Importer requirement. @require-wp-5.2 Scenario: Custom percentage of deactivated plugins Given a WP install And a custom.yml file: """ plugin-deactivated: class: WP_CLI\Doctor\Check\Plugin_Deactivated options: threshold_percentage: 60 """ And I run `wp plugin install debug-bar wordpress-importer` When I run `wp doctor check plugin-deactivated --config=custom.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| plugin-deactivated \| warning \| Greater than 60 percent of plugins are deactivated. \| Scenario: Gracefully handle no plugins installed Given a WP install And I run `wp plugin uninstall --all` When I run `wp doctor check plugin-deactivated` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| plugin-deactivated \| success \| Less than 40 percent of plugins are deactivated. \| Scenario: Gracefully handle only network-enabled plugins installed and activated Given a WP multisite installation And I run `wp plugin activate --network --all` When I run `wp doctor check plugin-deactivated` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| plugin-deactivated \| success \| Less than 40 percent of plugins are deactivated. \|	2.93 KB	2026-03-21 17:12
📄 check-plugin-status.feature Feature: Check the status of a plugin Scenario: Verify check description Given a WP install And a config.yml file: """ plugin-akismet-active: class: WP_CLI\Doctor\Check\Plugin_Status options: name: akismet status: active """ When I run `wp doctor list --fields=name,description --config=config.yml` Then STDOUT should be a table containing rows: \| name \| description \| \| plugin-akismet-active \| Errors if plugin 'akismet' isn't in the expected state 'active'. \| Scenario: Basic usage Given a WP install And I run `wp plugin install https://github.com/wp-cli/sample-plugin/archive/refs/heads/master.zip` And a config.yml file: """ plugin-akismet-active: class: WP_CLI\Doctor\Check\Plugin_Status options: name: akismet status: active plugin-sample-plugin-uninstalled: class: WP_CLI\Doctor\Check\Plugin_Status options: name: sample-plugin status: uninstalled """ When I try `wp doctor check --all --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| plugin-akismet-active \| error \| Plugin 'akismet' is 'inactive' but expected to be 'active'. \| \| plugin-sample-plugin-uninstalled \| error \| Plugin 'sample-plugin' is 'inactive' but expected to be 'uninstalled'. \| And STDERR should contain: """ Error: 2 checks report 'error'. """ And the return code should be 1 When I run `wp plugin activate akismet` Then STDOUT should not be empty When I try `wp doctor check --all --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| plugin-akismet-active \| success \| Plugin 'akismet' is 'active' as expected. \| \| plugin-sample-plugin-uninstalled \| error \| Plugin 'sample-plugin' is 'inactive' but expected to be 'uninstalled'. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 When I run `wp plugin delete sample-plugin` Then STDOUT should not be empty When I run `wp doctor check --all --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| plugin-akismet-active \| success \| Plugin 'akismet' is 'active' as expected. \| \| plugin-sample-plugin-uninstalled \| success \| Plugin 'sample-plugin' is 'uninstalled' as expected. \| Scenario: Invalid status registered Given a WP install And a config.yml file: """ plugin-akismet-active-network: class: WP_CLI\Doctor\Check\Plugin_Status options: name: akismet status: active-network """ When I try `wp doctor check plugin-akismet-active-network --config=config.yml` Then STDERR should be: """ Error: Invalid plugin_status. Should be one of: uninstalled, installed, active. """	3.4 KB	2025-09-06 07:07
📄 check-plugin-update.feature Feature: Check whether plugins are up to date Scenario: Verify check description Given an empty directory When I run `wp doctor list --fields=name,description` Then STDOUT should be a table containing rows: \| name \| description \| \| plugin-update \| Warns when there are plugin updates available. \| Scenario: Plugins are up to date Given a WP install # Akismet requires a newer WordPress version, but we don't really need it here. And I run `wp plugin uninstall akismet` And I run `wp plugin update --all` When I run `wp doctor check plugin-update` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| plugin-update \| success \| Plugins are up to date. \| Scenario: One plugin has an update available Given a WP install And I run `wp plugin install akismet --version=3.1.10 --force` When I run `wp doctor check plugin-update` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| plugin-update \| warning \| 1 plugin has an update available. \|	1.29 KB	2025-09-06 07:07
📄 check-theme-update.feature Feature: Check whether themes are up to date Scenario: Verify check description Given an empty directory When I run `wp doctor list --fields=name,description` Then STDOUT should be a table containing rows: \| name \| description \| \| theme-update \| Warns when there are theme updates available. \| Scenario: Themes are up to date Given a WP install And I run `wp theme update --all` When I run `wp doctor check theme-update` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| theme-update \| success \| Themes are up to date. \| Scenario: One theme has an update available Given a WP install And I run `wp theme update --all` And I run `wp theme install moina --version=1.1.2` When I run `wp doctor check theme-update` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| theme-update \| warning \| 1 theme has an update available. \|	1.19 KB	2025-09-06 07:07
📄 check.feature Feature: Basic check usage # Message "Updating to WordPress' newest minor version is strongly recommended." of type "error" appears. @broken @require-mysql Scenario: Use --spotlight to focus on warnings and errors Given a WP install And I run `wp plugin activate --all` And I run `wp plugin update --all` And I run `wp theme update --all` When I run `wp doctor list --format=count` Then save STDOUT as {CHECK_COUNT} When I run `wp doctor check --all --spotlight` Then STDOUT should be: """ Success: All {CHECK_COUNT} checks report 'success'. """ When I run `wp doctor check plugin-deactivated --spotlight` Then STDOUT should be: """ Success: The check reports 'success'. """ When I run `wp doctor check --all --spotlight --format=json` Then STDOUT should be: """ [] """ Scenario: Filter check results Given a WP install # Akismet requires a newer WordPress version, but we don't really need it here. And I run `wp plugin uninstall akismet` And I run `wp plugin activate --all` And I run `wp plugin update --all` And I run `wp theme update --all` And I run `wp option update blog_public 0` And a wp-content/uploads/foo.php file: """ <?php // Simple PHP file. """ When I try `wp doctor check option-blog-public php-in-upload --format=csv --fields=name,status` Then STDOUT should contain: """ php-in-upload,warning """ And STDOUT should contain: """ option-blog-public,error """ And the return code should be 1 When I try `wp doctor check option-blog-public php-in-upload --format=csv --fields=name,status --status=error` Then STDOUT should contain: """ option-blog-public,error """ And STDOUT should not contain: """ php-in-upload,warning """ And the return code should be 1 Scenario: Use --spotlight to view warnings and errors Given a WP install And I run `wp option update blog_public 0` And a wp-content/plugins/foo.php file: """ <?php // Plugin Name: Foo Plugin wp_cache_flush(); """ When I try `wp doctor check option-blog-public php-in-upload cache-flush --format=csv --fields=name,status` Then STDOUT should be: """ name,status cache-flush,warning option-blog-public,error php-in-upload,success """ And the return code should be 1 When I run `wp doctor check php-in-upload plugin-active-count --spotlight` Then STDOUT should be: """ Success: All 2 checks report 'success'. """ And the return code should be 0 When I run `wp doctor check plugin-active-count --spotlight` Then STDOUT should be: """ Success: The check reports 'success'. """ And the return code should be 0 When I try `wp doctor check option-blog-public php-in-upload cache-flush --spotlight --format=csv --fields=name,status` Then STDOUT should be: """ name,status cache-flush,warning option-blog-public,error """ And the return code should be 1 When I run `wp doctor check php-in-upload --spotlight --format=json` Then STDOUT should be: """ [] """ And the return code should be 0 Scenario: Error when no checks nor --all are provided Given a WP install When I try `wp doctor check` Then STDERR should be: """ Error: Please specify one or more checks, or use --all. """ And the return code should be 1 Scenario: Error when an invalid check is provided. Given a WP install And a config.yml file: """ """ When I try `wp doctor check invalid-check` Then STDERR should be: """ Error: Invalid check. """ And the return code should be 1 When I try `wp doctor check invalid-check invalid-check2` Then STDERR should be: """ Error: Invalid checks. """ And the return code should be 1 When I try `wp doctor check --all --config=config.yml` Then STDERR should be: """ Error: No checks registered. """ And the return code should be 1 Scenario: List all default checks Given a WP install When I run `wp doctor list --fields=name` Then STDOUT should be a table containing rows: \| name \| \| autoload-options-size \| \| core-update \| \| core-verify-checksums \| \| plugin-deactivated \| \| plugin-update \| \| theme-update \| Scenario: Discard redirects emitted by WordPress Given a WP install And a wp-content/mu-plugins/redirect.php file: """ <?php add_action( 'template_redirect', function(){ wp_redirect( 'http://google.com' ); exit; }); """ When I try `wp doctor check autoload-options-size --fields=name,status` Then STDERR should contain: """ Warning: Incomplete check execution. Some code is trying to do a URL redirect. Backtrace: """ And STDOUT should be a table containing rows: \| name \| status \| \| autoload-options-size \| success \| Scenario: Use --debug=doctor flag to see check progress Given a WP install When I try `wp doctor check autoload-options-size --debug=doctor` Then STDERR should contain: """ Running check: autoload-options-size """ And STDERR should contain: """ Status: """ Scenario: Use --debug=doctor flag with multiple checks Given a WP install When I try `wp doctor check autoload-options-size plugin-deactivated --debug=doctor` Then STDERR should contain: """ Running check: autoload-options-size """ And STDERR should contain: """ Running check: plugin-deactivated """ Scenario: Use --debug=doctor flag with file checks Given a WP install And a wp-content/plugins/foo.php file: """ <?php // Plugin Name: Foo Plugin wp_cache_flush(); """ When I try `wp doctor check cache-flush --debug=doctor` Then STDERR should contain: """ Scanning filesystem for file checks... """ And STDERR should contain: """ Running check: cache-flush """	6.27 KB	2026-03-21 17:12
📄 config.feature Feature: Configure the Doctor Scenario: Error when config file doesn't exist Given an empty directory When I try `wp doctor list --config=foo.yml` Then STDERR should be: """ Error: Invalid configuration file. """ Scenario: Error when a check class doesn't exist Given an empty directory And a config.yml file: """ undefined-class: class: Class_Undefined """ When I try `wp doctor check --all --config=config.yml` Then STDERR should be: """ Error: Class 'Class_Undefined' for check 'undefined-class' doesn't exist. Verify check registration. """ Scenario: Error when a check class doesn't extend our base class Given an empty directory And a config.yml file: """ invalid-class: class: WP_CLI """ When I try `wp doctor check --all --config=config.yml` Then STDERR should be: """ Error: Class 'WP_CLI' for check 'invalid-class' needs to extend Check base class. Verify check registration. """ Scenario: Error when an invalid check name is provided Given an empty directory And a config.yml file: """ check space: class: WP_CLI\Doctor\Check\Constant_Definition """ When I try `wp doctor check --all --config=config.yml` Then STDERR should be: """ Error: Check name 'check space' is invalid. Verify check registration. """ Scenario: Error when a check is missing its 'check' or 'class' Given an empty directory And a config.yml file: """ constant-custom: constant: Constant_Definition options: constant: CUSTOM defined: true """ When I try `wp doctor list --config=config.yml` Then STDERR should be: """ Error: Check 'constant-custom' is missing 'class' or 'check'. Verify check registration. """ Scenario: Error when a check has been provided an unsupported option Given an empty directory And a config.yml file: """ constant-invalid-option: check: Constant_Definition options: constant_name: CUSTOM defined: true """ When I try `wp doctor list --config=config.yml` Then STDERR should be: """ Error: Cannot set invalid property 'constant_name'. """ Scenario: Support inheriting another config file Given an empty directory And a first-config.yml file: """ constant-wp-debug: check: Constant_Definition options: constant: WP_DEBUG falsy: true """ And a second-config.yml file: """ _: inherit: first-config.yml constant-savequeries: check: Constant_Definition options: constant: SAVEQUERIES falsy: true """ When I run `wp doctor list --format=count --config=first-config.yml` Then STDOUT should be: """ 1 """ When I run `wp doctor list --format=count --config=second-config.yml` Then STDOUT should be: """ 2 """ Scenario: Support inheriting the default doctor.yml Given an empty directory And a first-config.yml file: """ _: inherit: default constant-custom: check: Constant_Definition options: constant: CUSTOM defined: true """ When I run `wp doctor list --config=first-config.yml --fields=name` Then STDOUT should be a table containing rows: \| name \| \| constant-custom \| \| constant-savequeries-falsy \| Scenario: Permit checks to be skipped when inheriting Given an empty directory And a skipped-checks.yml file: """ _: inherit: default skipped_checks: - constant-savequeries-falsy """ When I run `wp doctor list --fields=name` Then STDOUT should contain: """ constant-savequeries-falsy """ When I run `wp doctor list --config=skipped-checks.yml --fields=name` Then STDOUT should not contain: """ constant-savequeries-falsy """ # Minimum requirement for Akismet is WP 5.8. @require-wp-5.8 Scenario: Use the 'require' attribute to require an arbitrary path Given a WP install And a config.yml file: """ plugin-akismet-valid-api-key: class: Akismet_Valid_API_Key require: akismet-valid-api-key.php """ And a akismet-valid-api-key.php file: """ <?php /** * Ensures Akismet is activated with the appropriate credentials. */ class Akismet_Valid_API_Key extends WP_CLI\Doctor\Check { public function run() { // If the Akismet isn't activated, bail early. if ( ! class_exists( 'Akismet' ) ) { $this->set_status( 'error' ); $this->set_message( "Akismet doesn't appear to be activated." ); return; } // Verify that the API exists. $api_key = Akismet::get_api_key(); if ( empty( $api_key ) ) { $this->set_status( 'error' ); $this->set_message( 'API key is missing.' ); return; } // Verify that the API key is valid. $verification = Akismet::verify_key( $api_key ); if ( 'failed' === $verification ) { $this->set_status( 'error' ); $this->set_message( 'API key verification failed.' ); return; } // Everything looks good, so report a success. $this->set_status( 'success' ); $this->set_message( 'Akismet is activated with a verified API key.' ); } } """ And I run `wp plugin activate akismet` When I try `wp doctor check --all --config=config.yml` Then STDOUT should be a table containing rows: \| name \| status \| message \| \| plugin-akismet-valid-api-key \| error \| API key is missing. \| And STDERR should contain: """ Error: 1 check reports 'error'. """ And the return code should be 1 Scenario: 'require' attribute fails successfully when the file doesn't exist Given a WP install And a config.yml file: """ plugin-akismet-valid-api-key: class: Akismet_Valid_API_Key require: akismet-valid-api-key.php """ When I try `wp doctor check --all --config=config.yml` Then STDERR should be: """ Error: Required file 'akismet-valid-api-key.php' doesn't exist (from 'plugin-akismet-valid-api-key'). """	6.52 KB	2025-09-06 07:07

Edit File:

Terminal