Although it’s power comes from its ability to be customized,
wp doctor includes a number of default diagnostic checks considered to be recommendations for production websites.
wp doctor list to view these default checks:
|autoload-options-size||Warns when autoloaded options size exceeds threshold of 900 kb.|
|constant-savequeries-falsy||Confirms expected state of the SAVEQUERIES constant.|
|constant-wp-debug-falsy||Confirms expected state of the WP_DEBUG constant.|
|core-update||Errors when new WordPress minor release is available; warns for major release.|
|core-verify-checksums||Verifies WordPress files against published checksums; errors on failure.|
|cron-count||Errors when there’s an excess of 50 total cron jobs registered.|
|cron-duplicates||Errors when there’s an excess of 10 duplicate cron jobs registered.|
|file-eval||Checks files on the filesystem for regex pattern
|option-blog-public||Confirms the expected value of the ‘blog_public’ option.|
|plugin-active-count||Warns when there are greater than 80 plugins activated.|
|plugin-deactivated||Warns when greater than 40% of plugins are deactivated.|
|plugin-update||Warns when there are plugin updates available.|
|theme-update||Warns when there are theme updates available.|
To explain these further:
- Autoloaded options are options that are automatically loaded in every request to WordPress. A size exceeding the recommended threshold could be a symptom of a larger problem.
SAVEQUERIEScauses WordPress to save a backtrace for every SQL query, which is an expensive operation, using
SAVEQUERIESin production is discouraged.
- WordPress minor versions are typically security releases that should be applied immediately.
If you create a custom
doctor.yml config file, you can use
wp doctor list --config=<file> to view the diagnostic checks listed in the file.