BugWP logo BugWP
Back to Community
Home / Community / Plugin → Health check & troubleshooting

Resolving Common Health Check Plugin Errors: Warnings, Notices, and Fatal Issues

44 threads Sep 16, 2025 Plugin → Health check & troubleshooting

Content

The 'Health Check & Troubleshooting' plugin is an invaluable tool for diagnosing WordPress site issues. However, like any complex software, it can sometimes throw errors itself. Based on community reports, this guide covers the most frequent errors and how to resolve them.

Understanding the Common Errors

The errors users encounter generally fall into three categories:

  • PHP Notices and Warnings: These are non-critical messages about undefined variables or indexes (e.g., Undefined index: slug, Trying to get property of non-object). They often appear in debug logs but may not break the site.
  • PHP Fatal Errors: These are critical errors that halt script execution, often causing a white screen or a "critical error" message on the site. They are frequently caused by compatibility issues with other plugins, themes, or WordPress core itself.
  • Functionality Bugs: These are issues where a specific feature, like the phpinfo tab or WP-CLI command, doesn't work as intended due to a coding oversight.

Fixes and Workarounds for Common Issues

1. PHP Notices and Warnings

Many warnings and notices are often patched by the 'Health Check & Troubleshooting' team in subsequent updates. If you see an error like one of the following, updating the plugin is the first step.

  • "Undefined index: slug" (line 306)
    This was a known issue in version 1.2.4. A fix was implemented in a later version. If you cannot update immediately, a community-suggested workaround was to edit the file plugins/health-check/includes/class-health-check.php at line 306. The line was changed from: 
    '_wpnonce' => wp_create_nonce( 'health-check-troubleshoot-plugin-' . $plugin_data['slug'] ),
    to a version that first checks if the slug index exists.
  • "Trying to get property of non-object" (Dashboard Widget)
    This notice, found in class-health-check-dashboard-widget.php, was caused by an incorrect data check. This was resolved in version 1.4.1. Visiting the Site Health Status page can sometimes trigger the data to populate correctly and clear the notice.
  • "Undefined variable: core_update_needed" (line 66)
    This notice in class-health-check-debug-data.php was fixed by defining the variable before it is used. This patch was included in version 1.2.1.

2. PHP Fatal Errors

Fatal errors are more severe and require immediate action, often preventing access to the admin dashboard.

  • "Call to undefined function" in Troubleshooting Mode
    A common trigger is a function missing because a plugin (like WooCommerce) is disabled in Troubleshooting Mode but its functions are still being called. The 'Health Check & Troubleshooting' team has frequently released compatibility updates (e.g., version 1.4.5 for WP 5.5) to address these issues. If you get locked out of your admin due to Troubleshooting Mode, you can clear your browser cookies or close all browser windows to exit the mode and regain access.
  • Session/Header Errors
    Errors related to sessions or headers being sent (often after a WordPress core update) can indicate a conflict with another plugin or theme. The standard troubleshooting step is to disable all other plugins and switch to a default theme to confirm the conflict.
  • WP-CLI "Class not found" Error
    An error like Class "HealthCheckWP_CLIStatus" not found indicates a problem with the WP-CLI integration. This typically requires a plugin update to resolve.

3. Functionality and Interface Bugs

  • Blank phpinfo Tab
    If the PHP Information tab returns a blank page, it may be due to server-level security settings that block requests containing the term "phpinfo". This is a server configuration issue, not a bug with the plugin itself.
  • Incorrect Link for PHP Info
    A bug in earlier versions caused the "View extended PHP information" button to link to the wrong admin page (/wp-admin/?page=health-check... instead of /wp-admin/tools.php?page=health-check...). This was fixed in version 1.3.2.
  • Translation Errors
    Some translation files contained incorrect strings. The 'Health Check & Troubleshooting' team manages translations through WordPress's Translate platform, where community members can submit corrections and new translations.

General Troubleshooting Steps

  1. Update the Plugin: The vast majority of these bugs were identified and fixed in subsequent releases. Always ensure you are running the latest version of the 'Health Check & Troubleshooting' plugin.
  2. Basic Conflict Test: If an error persists, follow standard WordPress troubleshooting procedure: disable all other plugins and switch to a default theme (like Twenty Twenty-One). If the error stops, re-enable plugins one-by-one to find the conflict.
  3. Check Your Logs: Enable WP_DEBUG to log errors to a debug.log file. The specific error and file line number are crucial for diagnosing the problem.
  4. Search for Solutions: Check the plugin's support forums to see if your specific error has already been reported and resolved. The community often shares temporary workarounds before an official fix is released.

While encountering errors can be frustrating, the 'Health Check & Troubleshooting' plugin has an active development history of quickly addressing reported bugs. Following these steps should help you resolve most common issues and get back to diagnosing your WordPress site's health.

Related Support Threads Support