Health Check & Troubleshooting


這個外掛會為 WordPress 網站進行多項檢查,以便檢測常見的設定錯誤及已知問題。

目前這個外掛會檢查網站的 PHP 及 MySQL 版本、WordPress 需要或有待改善的延伸模組,以及目前網站可以存取的 服務。

外掛的偵錯功能可讓網站管理員收集 WordPress 網站及伺服器設定的相關資訊,這樣便能輕鬆地將必要資訊分享給佈景主題、外掛或官方 技術支援論壇的技術支援代表。

疑難排解功能可讓網站管理員為 WordPress 網站執行一個停用全部外掛及佈景主題的標準工作階段,且該工作階段僅會套用於啟用這個模式的使用者,而不會影響網站一般訪客。

如需更全面有效使用 Health Check 外掛的示範案例,請參閱 技術支援小組撰寫的外掛手冊頁面 (英文)。

將來我們會為這個外掛加入更多檢查項目,歡迎前往外掛的技術支援論壇GitHub 專案頁面提出意見反應。


  • 系統通過自動測試後所顯示的網站狀態檢查畫面
  • [偵錯資訊] 標籤頁提供了可進行複製貼上的欄位
  • 如需更多詳細資訊,可以在 [PHP 資訊] 標籤頁內取得



如因啟用 [疑難排解模式] 造成任何問題,清除瀏覽器 Cookie 便可將該模式予以停用。

不瞭解如何清除瀏覽器的 Cookie 嗎?不必擔心,請關閉所有瀏覽器視窗、或重新啟動電腦,便能自動清除因啟用 [移難排解模式] 所產生的 Cookie。



lines above code of sitemap.xml, bug solved


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!
閱讀全部 97 則使用者評論


Health Check & Troubleshooting 外掛為開源軟體。以下人員為這個外掛做出了重大貢獻。


Health Check & Troubleshooting 外掛目前已有 20 個本地化語言版本。 感謝所有譯者為這個外掛做出的貢獻。

將 Health Check & Troubleshooting 外掛本地化為台灣繁體中文版


任何人均可瀏覽程式碼、查看 SVN 存放庫,或透過 RSS 訂閱開發記錄



  • 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.


  • 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.


  • 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.


  • 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.