Health Check & Troubleshooting

Descrição

Este plugin fará algumas verificações à sua instalação de WordPress para detectar erros comuns de configuração e problemas conhecidos.

De momento verifica as suas versões de PHP e MySQL, algumas extensões necessárias ou que poderão melhorar o seu WordPress, e verifica se o seu site tem acesso aos serviços de WordPress.org.

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.

A resolução de problemas permite-lhe activar um modo de segurança particular, em que todos os plugins são desactivados e é utilizado um tema por omissão, mas apenas para o seu utilizador.

Para mais detalhes sobre como usar o plugin Health Check, consulte o manual do plugin criado pela equipa de suporte em WordPress.org.

No futuro poderão ser adicionadas mais verificações, agradecemos feedback no fórum em WordPress.org e na página do projecto no GitHub.

Ecrãs

  • O ecrã de verificação após decorrerem os testes automáticos do sistema.
  • A informação de depuração, mostrando o campo para copiar e colar.
  • The generic PHP information tab, when more detailed information is required.

Perguntas frequentes

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.

Avaliações

thanks

lines above code of sitemap.xml, bug solved https://kb.yoast.com/kb/how-to-check-for-plugin-conflicts/#plugin https://github.com/olefredrik/FoundationPress/issues/753

Essential

A necessary plugin, also used by the giants of programming. Allows you to find and solve any problem of any internal conflict without pausing the website. Highly recommended.

Helped me find a non-updating problem

I love this plugin. Not only does it summarize all the technical info of the server with a phpinfo() page but it also provides a sanity check on the installation. Specifically that check pointed out that my wordpress folder had a .git folder within, an indication that I was using version control. (I wasn't.) But that .git folder was preventing auto-updating. Ta Da!
Ler todas as 97 avaliações

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 20 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

v1.2.6

  • Security: Harden the consistency checker, further limiting what files can be looked up to only include core files. Independently reported by Julien Legras of Synacktiv and Tim Coen of Tim Coen IT Security & Development.

v1.2.5

  • Fix: Ensure the REST API status test runs as intended.
  • Fix: Remove warning on plugin screens when premium plugins are used.
  • Fix: Backup reminder would not remain dismissed in all scenarios after the recent update.

v1.2.4

  • Security: Prevent arbitrary file viewing through the integrity file actions. Independently reported by Julien Legras of Synacktiv and siliconforks.
  • Security: Site status was available to any user with a subscriber role or higher on a site. Reported by Julien Legras of Synacktiv.
  • Security: Hardened the troubleshooting mode session so it is locked to the users location when active.
  • New enhancement: Check that various PHP extensions exist, as recommended by the WordPress Hosting Community.
  • New enhancement: Check if update APIs are being manipulated by plugins or themes.
  • Fix: Copying debug information had the wrong indentation for easier readability.
  • Fix: Toggling plugins and themes from the troubleshooting widget on in the dashboard now lets you expand/collapse them as intended.
  • Fix: When debugging was enabled in WordPress, disabling a plugin in troubleshooting mode would cause a WSOD if the disabled plugin caused a fatal error.

v1.2.3

  • Added REST API availability test to the Site Status

v 1.2.2

  • Added Twenty Nineteen as a recognized core theme.

v 1.2.1

  • Make sure only those with access to the plugin see the backup encouragement notice.
  • Make sure the is_troubleshooting() checks are available to the Site Status tester when the MU plugin may not have updated yet.
  • Avoid a warning of an undefined variable if you have the latest WordPress version installed.

v 1.2.0

  • Changed plugin name, it now better describes the plugins two primary purposes.
  • Changed the Health Check tab, it’s now named Site Status, as we used the old name too many places and it was confusing.
  • Site status tests now run asynchronously, making the page load much faster.
  • The HTTPS tests now also check your Site URL settings to make sure they are following recommended best practices.
  • Fixed a warning preventing plugin names from displaying on the front-end in some cases.
  • Fixed an issue where you might get a 500 error if you tried using Troubleshooting Mode while using a child theme.
  • Automatically disable/enable a plugin or theme in Troubleshooting Mode if they are detected to cause errors.
  • Introduce a new dashboard widget during Troubleshooting Mode (and a simplified version on the plugins screen) to better explain what is going on, and make available actions more discoverable than the admin menu is.
  • Some text improvements throughout the plugin.
  • When loopback tests fail, we previously tested all plugins at once, for sites that have many plugins this may fail as the request times out. We now test one plugin at a time to avoid this, while also showing more information at the tests are running to the end user.