Health Check & Troubleshooting

Opis

Wtyczka wykonuje wiele testów instalacji WordPress, aby wykryć typowe błędy konfiguracji oraz znane problemy.

Obecnie sprawdza używane wersje PHP i MySQL, niektóre rozszerzenia, potrzebne lub ulepszające WordPressa, oraz sprawdza czy usługi WordPress.org są dostępne w witrynie.

Sekcja debugowania umożliwia zbieranie informacji o konfiguracji WordPressa i serwera, które można łatwo udostępnić zespołom wsparcia motywu, wtyczek lub na oficjalnych forach pomocy WordPress.org.

Rozwiązywanie problemów umożliwia wykonanie waniliowej sesji WordPressa, w której wyłączane są wszystkie wtyczki, a motyw przestawiany na domyślny. Wszystko to dzieje się tylko dla testującego użytkownika.

Aby uzyskać szerszy przykład skutecznego korzystania z wtyczki Health Check, sprawdź stronę podręcznika zespołu pomocy technicznej WordPress.org na temat wtyczki.

W przyszłości możemy wprowadzić więcej sprawdzeń i poznać opinie zarówno na forach WordPress.org, jak i na stronie projektu na GitHubie.

Zrzuty ekranów

  • Ekran kontroli stanu po automatycznych testach przeszedł przez system.
  • Informacje debugowania z rozszerzonym polem kopiuj i wklej.
  • Ogólna zakładka informacji o PHP, gdy potrzebne są bardziej szczegółowe dane.

FAQ

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.

Recenzje

Often My First Step in Troubleshooting

I love this plugin. I’ve worked on a number of sites that had an issue where the normal troubleshooting of disabling plugins and themes couldn’t easily be done.

Health check is often one of the first steps in troubleshooting these sites. Although you may still have some manual diagnostics to perform, this narrows things down without breaking the front end of the site. This saves me the time and hassle of setting up a staging site to troubleshoot, then transfer the fix over to the live site.

This is a wonderful plugin for any troubleshooting but especially for sites where it’s important the site doesn’t go down.

Handy for troubleshooting without affecting live site

I’ve used this plugin a couple of times on client sites, but a recent experience at a WordCamp help desk was amazing. A person came up with a perplexing problem that most of her WooCommerce store products showed their price just fine, but a few (more recently created) products were not showing a price at all. We look at a few basic settings, but nothing looked out of place.

Of course, since this is a live and active store, troubleshooting for plugin conflicts could be a mess, since you don’t want current site visitors to see stuff going up and down. So we installed the Health Check plugin, and deactivated all the plugins except WooCommerce. Strangely, the problem persisted, but when we switched to a default theme, bingo! – the issue resolved. Theme conflict!

We were not able to completely solve the problem with the theme at the help desk, but at least we were able to help this person narrow down where the problem was coming from. I’ll definitely keep this top of mind next time I have issues to troubleshoot – especially when it’s preferable that the live site not be affected!

Indispensable for Isolating Problems on Active Sites

The ability to temporarily change themes and plugins on an active site without affecting other users is absolutely the best thing I’ve ever encountered in building websites. To manually do everything this plugin does would take hours if not days. It’ll let you root out conflicts in no time, or at least as fast as you can run a test scenario.

Make no mistake, this is not a magic bullet. You still may need to do the debugging work, but it goes so much faster. If you’re lucky, the status and debug screens will flag the problem right away. If not, the troubleshooting mode will at least isolate the problem to a specific theme or plugin.

I was initially reluctant to use this plugin because of many low ratings, but then I realized that the vast majority of low ratings were related to earlier versions. After seeing in the health-check support forum how everyone posting received help and invariably got their problem resolved, it put my reservations to rest and I went ahead and installed this plugin. I never looked back, it’s awesome!

I now recommend health-check to everyone who appears to be experiencing a conflict of some sort. I personally have not heard of anyone I’ve helped having trouble with this plugin. Because of my active involvement in the WordPress support forums, I realize my opinion on this could be biased, but I’m absolutely certain I would be equally pleased if I was brand new to WordPress and encountered a problem.

Fast and Easy

It’s a great tool to figure out what plugin is causing an issue ( or theme in some cases ). I’ve used it a fair number of times, easy to install, easy to disable and re-enable plugins, easy to remove once you’ve found whatever was causing the issue. The plugin does what it advertises without complaint and, from my understanding, is in active development to get better.

Awesome for finding conflicts

It’s so simple to use. Install, activate debug mode and with the admin menu you can enable/disable separate plugins/themes without affecting your live site. You can quickly find out which plugin or theme is causing the issue.

Would definitely recommend it to anyone who runs into an issue on his own site.

Przeczytaj 85 recenzji

Kontrybutorzy i deweloperzy

„Health Check & Troubleshooting” jest oprogramowaniem open source. Poniższe osoby miały wkład w rozwój wtyczki.

Kontrybutorzy

Wtyczka “Health Check & Troubleshooting” została przetłumaczona na 19 języków. Podziękuj tłumaczom za ich wkład.

Przetłumacz wtyczkę “Health Check & Troubleshooting” na swój język.

Interesuje cię rozwój wtyczki?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Log zmian

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.