Patrick Lumumba

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


Lumiblog Debug Log Inspector

Monitor debug logs for any WordPress plugin errors and display real-time status in the WordPress admin bar.

neeraj kumar

<p>RuntimeGuard is a monitoring plugin that helps administrators detect, track, and resolve runtime issues in their WordPress site from a centralized dashboard.</p>
<p>It provides real-time insights into errors, system health, and environment issues so you can fix problems before they affect your users.</p>
<h4>Why Use RuntimeGuard?</h4>
<p>Many WordPress issues go unnoticed until they affect users — broken features, failed emails, silent JavaScript errors, or server misconfigurations.</p>
<p>RuntimeGuard helps you:</p>
<ul>
<li>Detect issues early before they impact visitors</li>
<li>Monitor errors across PHP, JavaScript, and system checks</li>
<li>Get alerts when something breaks</li>
<li>Maintain site stability without constant manual checks</li>
</ul>
<h4>Key Features</h4>
<ul>
<li>Real-time runtime issue logging with severity levels</li>
<li>JavaScript error tracking for admin and front-end pages</li>
<li>System health checks including loopback and environment validation</li>
<li>Debug log scanning and analysis</li>
<li>Monitoring of database, PHP configuration, email delivery, and file permissions</li>
<li>Plugin and theme activity history tracking</li>
<li>Email alerts for critical issues</li>
<li>Scheduled email digests (weekly, bi-weekly, or monthly)</li>
<li>Export issue logs as CSV for reporting and analysis</li>
</ul>
<p>RuntimeGuard is designed as a monitoring and diagnostic tool for administrators. It complements your development workflow but does not replace code linting, testing, or server-level monitoring tools.</p>


RuntimeGuard

Detect hidden errors in your WordPress site with real-time monitoring, logging, and alerts for runtime issues.

Lumiblog Debug Log Inspector vs RuntimeGuard