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.
A secção de depuração permite-lhe reunir informações sobre o seu WordPress e a configuração do servidor, que poderá partilhar com os representantes do suporte dos temas e plugins, ou no fórum de suporte oficial em WordPress.org.
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.
Para mais detalhes sobre como usar o plugin Health Check, consulte o manual do plugin criado pela equipa de suporte em WordPress.org.
Feedback is welcome both through the WordPress.org forums, the GitHub project page, or on Slack in either #forums or #core-site-health.
I am unable to access my site after enabling troubleshooting
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 PHP compatibility says this plugin only work with PHP version X?
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.
Where can I report security bugs?
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.
Contribuidores e programadores
“Health Check & Troubleshooting” é software de código aberto. As seguintes pessoas contribuíram para este plugin:Contribuidores
“Health Check & Troubleshooting” foi traduzido para 29 locales. Obrigado aos tradutores pelas suas contribuições.
Traduza o “Health Check & Troubleshooting” para o seu idioma.
Interessado no desenvolvimento?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Registo de alterações
- 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.
- Fixed a bug where if Health Check was disabled during troubleshooting, you would need to force-enable/disable other plugins or themes.
- Added a custom filter for the Health Check plugin PHP Compatibility check.
- Added functions which will try to disable cache solutions during troubleshooting.
- Added ability to force changes if loopbacks fail during troubleshooting.
- Changed the location of the
phpinfo()check to the Tools section.
- Changed how troubleshooting mode implements its conditional actions and filters when enabled.
- Fixed styling issues for troubleshooting mode in WordPress 5.9.
- Removed Site Health Status from the plugin, as they were implemented in WordPress 5.2.