Health Check & Troubleshooting

説明

This plugin will perform a number of checks on your WordPress install to detect common configuration errors and known issues.

It currently checks your PHP and MySQL versions, some extensions which are needed or may improve WordPress, and that the WordPress.org services are accessible to you.

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 vanilla WordPress session, where all plugins are disabled, and a default theme is used, but only for your user.

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.

In the future we may introduce more checks, and welcome feedback both through the WordPress.org forums, and the GitHub project page.

スクリーンショット

  • The health check screen after the automated tests have gone over the system.
  • デバッグ情報とそのコピーペースト欄
  • 詳細情報が必要な場合の一般的な PHP 情報

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.

評価

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.

Customer Service responses

Love the idea of the plugin. A nice option to manual healthchecks, but haven’t been impressed with the customer service response to users comments in the support forums.

Coderisk.com score for the plugin (zero) is absolutely awesome. Wish all the plugins I use were so secure.

84件のレビューをすべて表示

貢献者と開発者

Health Check & Troubleshooting はオープンソースソフトウェアです。以下の人々がこのプラグインに貢献しています。

貢献者

“Health Check & Troubleshooting” は19ロケールに翻訳されています。 翻訳者のみなさん、翻訳へのご協力ありがとうございます。

“Health Check & Troubleshooting” をあなたの言語に翻訳しましょう。

開発に興味がありますか ?

コードを閲覧するか、SVN リポジトリをチェックするか、開発ログRSS で購読してみてください。

変更履歴

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.