Lumiblog Debug Log Inspector is a powerful quality assurance and debugging tool that monitors your WordPress debug.log file for plugin-specific errors. Unlike other debug tools, it allows you to monitor ANY WordPress plugin through an easy-to-use settings interface – no coding required!
Key Features
- Universal Plugin Monitoring: Add any WordPress plugin to monitor through a simple settings page
- No Code Editing: Add/edit/delete monitored plugins through the WordPress admin interface
- Real-time Monitoring: Automatically scans your debug.log file for errors
- Visual Status Indicators: Color-coded admin bar display (Green = OK, Red = Errors Found, Gray = Debug Logging Disabled)
- Auto-Detection: Option to only monitor plugins that are currently active
- Plugin-Specific Tracking: Individual status for each monitored plugin
- Last Error Display: Shows the most recent error message for quick diagnosis
- Duplicate Prevention: Smart validation prevents adding the same plugin twice
- Enable/Disable Plugins: Toggle monitoring for specific plugins without deleting them
- Lightweight: Minimal performance impact with efficient log reading
- Well-Organized Code: Modular file structure for easy maintenance and customization
Perfect For
- QA Teams testing multiple plugins
- Plugin Developers debugging their own plugins
- WordPress Developers monitoring client sites
- Agency Teams managing multiple WordPress installations
- Anyone who wants to keep track of plugin errors
How It Works
- Install and activate the plugin
- Go to Settings > Log Inspector
- Add any plugin you want to monitor by providing:
- Plugin Name (e.g., “WooCommerce”)
- Plugin File Path (e.g., “woocommerce/woocommerce.php”)
- Search Terms (e.g., “woocommerce, wc-“)
- Check the admin bar for real-time error status
Requirements
To use this plugin effectively, you need to enable WordPress debug logging by adding these constants to your wp-config.php file:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
Testing the Plugin
To verify Lumiblog Debug Log Inspector is working correctly, follow these steps:
Step 1: Enable Debug Logging
Add to your wp-config.php:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
Step 2: Add a Plugin to Monitor
- Go to Settings > Log Inspector
- Click “Add New Plugin to Monitor”
- Fill in the form with a plugin you have installed (e.g., WooCommerce)
- Plugin Name:
WooCommerce
- Plugin File Path:
woocommerce/woocommerce.php
- Search Terms:
woocommerce, wc-
- Click “Add Plugin”
Step 3: Generate a Test Error
Note: Ensure that the test site is running on PHP 8.4+
-
Add this code snippet inside of any active plugin’s main file:
/**
- DEBUG LOG INSPECTOR DEMO – PHP 8.4 Warning Trigger
- REMOVE AFTER DEMO/TESTING!
*/
add_action( ‘load-index.php’, function() {
if ( version_compare( PHP_VERSION, ‘8.4.0’, ‘>=’ ) ) {
$test_array = array( ‘name’ => ‘Debug Log Inspector’ );
$undefined_value = $test_array[’email’]; // Triggers warning
error_log( ‘[DLI-DEMO-PHP84] PHP 8.4 warning triggered!’ );
}
});
-
Reload the site’s admin dashboard to trigger the error
- Check your admin bar – it should turn RED
Step 4: View the Debug Log (Optional)
Navigate to wp-content/debug.log to see the actual error entries that were logged.
Clean Up:
- Remove the test code you added
- Either delete
wp-content/debug.log or clear its contents
- The admin bar should return to GREEN
Additional Information
Debug Constants
For enhanced debugging, you can also add these optional constants to your wp-config.php:
define( 'SCRIPT_DEBUG', true );
define( 'SAVEQUERIES', true );
define( 'WP_DEBUG_DISPLAY', false ); // Set to false on production sites
For Developers
The plugin is designed to be easily extendable. All classes are well-documented and follow WordPress coding standards. Feel free to fork and customize for your specific needs.
Support
For support, feature requests, or bug reports, please visit the WordPress.org support forums for this plugin.
Contributing
Contributions are welcome! Please visit the plugin’s Github Repo for more information.