Health Check & Troubleshooting Plugin
Health Check identifies common problems, and helps you troubleshoot plugin and theme conflicts.
This plugin will perform a number of checks on your WordPress installation to detect common configuration errors and known issues, and also allows plugins and themes to add their own checks.
The debug section, which allows you to gather information about your WordPress and server configuration that you may easily share with support representatives for themes, plugins or on the official WordPress.org support forums.
Troubleshooting allows you to have a clean WordPress session, where all plugins are disabled, and a default theme is used, but only for your user until you disable it or log out.
The Tools section allows you to check that WordPress files have not been tampered with, that emails can be sent, and if your plugins are compatible with any PHP version updates in the future.
For a more extensive example of how to efficiently use the Health Check plugin, check out the WordPress.org support team handbook page about this plugin.
Feedback is welcome both through the WordPress.org forums, the GitHub project page, or on Slack in either #forums or #core-site-health.
Screenshots
The health check screen after the automated tests have gone over the system.
The debug information, with the copy and paste field expanded.
A selection of tools that can be ran on your site.
Troubleshooting mode enabled, showing your website Dashboard
FAQ
If you should find your self stuck in Troubleshooting Mode for any reason, you can easily disable it by clearing your cookies.
Are you unfamiliar with how to clear your cookies? No worries, you may also close all your browser windows, or perform a computer restart and it will clear this specific cookie automatically.
The plugin is made to be a support tool for as many users as possible, this means it needs code that is written for older sites as well.
Tools that check for PHP compatibility do not know how to separate this code from the real code, so it will give a false positive response.
At this time, the plugin has been tested with every version of PHP from 5.2 through 7.3, and works with all of these.
The Site Health team and WordPress community take security bugs seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
To report a security issue, please visit the WordPress HackerOne program.
Changelog
1.7.0 (2023-08-06)
- General: Improved styling inconsistency between the plugin and WordPress core.
- General: Fixed an issue with plugin translations where language strings would get mixed when using third party language plugins, or a separate profile language.
- Troubleshooting Mode: Fixed the URL used when disabling elements and having a subdirectory installation.
- Troubleshooting Mode: Fixed a deprecation warning when disabling troubleshooting mode on PHP version 8.3 or higher.
- Troubleshooting Mode: Added reference on how to troubleshoot as different users when testing scenarios.
- Tools: Fixed integration with WPTide for the PHP Compatibility checker.
- Tools: Added a viewer that will display debug log output when enabled.
- Tools: Added a warning to the File Integrity tester if unexpected files are mixed in with WordPress core files.
- Tools: Added a warning if sending emails is taking longer than expected.
- Tools: Added beta feature toggle for those who wish to test new functionality that may not be fully ready yet.
- CLI: Fixed the CLI commands, you can now
wp health-check statusto your hearts content! - Beta feature: Added a new beta feature, making it easier for non-technical users to grab screenshots of issues on their site, and share them.
v1.6.0 (2023-03-31)
- Improved the visual aspects of the Troubleshooting Mode Widget.
- Improved security by hardening Troubleshooting Mode actions with security tokens (nonces).
- Added a new tool to check
.htaccessrules (where applicable). - Added TwentyTwenty Three to the list of default themes.
- Added option to install the latest classic (non Site Editor-focused) default theme if no default theme exists.
- Added a new security confirmation prompt in Troubleshooting Mode, if a security token (nonce) value is either expired, or missing.
- Added better documentation around reporting security concerns.
- Fixed a bug where notices from previous Troubleshooting sessions would show up in a new session, which is just confusing.