A powerful WordPress plugin for monitoring debug logs and tracking plugin errors in real-time. Monitor any WordPress plugin through an intuitive admin interface - no coding required!
- 🔍 Universal Plugin Monitoring - Monitor ANY WordPress plugin, not just specific ones
- ⚙️ No Code Required - Manage everything through a beautiful admin interface
- 🎨 Visual Status Indicators - Color-coded admin bar (🟢 Green = OK, 🔴 Red = Errors, ⚪ Gray = Disabled)
- ⚡ Real-time Scanning - Automatically detects errors as they occur
- 🎯 Smart Filtering - Only monitor active plugins (optional)
- 🔄 Enable/Disable Toggle - Turn monitoring on/off without deleting entries
- 🚫 Duplicate Prevention - Smart validation prevents adding the same plugin twice
- 📊 Last Error Display - Quick access to the most recent error
- 💨 Lightweight - Minimal performance impact
- 🏗️ Clean Code - Modular, well-documented, follows WordPress standards
- WordPress 5.0 or higher
- PHP 7.0 or higher
- Debug logging enabled in WordPress
- Download the latest release from the Releases page
- Go to Plugins > Add New > Upload Plugin
- Upload the zip file
- Click Install Now and then Activate
cd wp-content/plugins
git clone https://github.com/yourusername/debug-log-inspector.gitThen activate through WordPress admin.
Add these lines to your wp-config.php file:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );- Navigate to Settings > Log Inspector
- Add a plugin to monitor:
- Plugin Name:
WooCommerce - Plugin File Path:
woocommerce/woocommerce.php - Search Terms:
woocommerce, wc-
- Plugin Name:
- Save and check your admin bar for the status indicator
- Go to Settings > Log Inspector
- Fill in the "Add New Plugin to Monitor" form:
- Plugin Name: Display name (e.g., "WooCommerce")
- Plugin File Path: Main plugin file (e.g., "woocommerce/woocommerce.php")
- Search Terms: Keywords to look for in logs (e.g., "woocommerce, wc-")
- Click Add Plugin
The plugin file path format is: folder-name/main-file.php
Examples:
- WooCommerce:
woocommerce/woocommerce.php - Yoast SEO:
wordpress-seo/wp-seo.php - Contact Form 7:
contact-form-7/wp-contact-form-7.php
You can find this under Plugins > Installed Plugins (shown below each plugin name).
Search terms are keywords the plugin looks for in your debug.log file. Use unique identifiers from the plugin:
- WooCommerce:
woocommerce, wc- - Elementor:
elementor, elementor-pro - Yoast SEO:
yoast, wpseo
Pro Tip: Check your debug.log to see what keywords appear in error messages from the plugin.
Create wp-content/plugins/test-error/test-error.php:
<?php
/**
* Plugin Name: Test Error Generator
*/
if ( isset( $_GET['trigger_test_error'] ) ) {
trigger_error( 'Test error from WooCommerce', E_USER_WARNING );
}- Activate the test plugin
- Visit:
yoursite.com/wp-admin/?trigger_test_error=1 - Check admin bar - should turn RED
- Click "LOG INSPECTOR" to see the error
Temporarily add this to any active plugin:
trigger_error( 'woocommerce test error', E_USER_WARNING );Reload admin, check the admin bar, then remove the code.
debug-log-inspector/
├── debug-log-inspector.php # Main plugin file
├── readme.txt # WordPress.org readme
├── README.md # This file
├── includes/
│ ├── class-log-inspector.php # Core scanning logic
│ ├── class-settings.php # Settings page handler
│ └── class-admin-bar.php # Admin bar display
├── assets/
│ ├── css/
│ │ └── admin-style.css # Admin interface styles
│ └── js/
│ └── admin-script.js # Admin interface scripts
└── templates/
└── settings-page.php # Settings page template
| Color | Status | Description |
|---|---|---|
| 🟢 Green | All Clear | No errors detected in monitored plugins |
| 🔴 Red | Errors Found | At least one plugin has errors |
| ⚪ Gray | Disabled | Debug logging is not enabled |
- Log Scan Size: Maximum bytes to scan (default: 300KB)
- Auto Enable: Only monitor active plugins
- Show Last Error: Display most recent error in admin bar
# Clone the repository
git clone https://github.com/yourusername/debug-log-inspector.git
# Navigate to the plugin directory
cd debug-log-inspector
# Create a symlink in your WordPress plugins directory
ln -s $(pwd) /path/to/wordpress/wp-content/plugins/debug-log-inspectorThis plugin follows WordPress Coding Standards.
Run PHP CodeSniffer:
phpcs --standard=WordPress debug-log-inspector/We welcome contributions! Please follow these steps:
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
- ✨ Complete plugin rewrite with modular architecture
- ✨ Universal plugin monitoring - works with ANY WordPress plugin
- ✨ Settings page for easy management (no code editing)
- ✨ Add/Edit/Delete plugins through admin interface
- ✨ Enable/Disable toggle for individual plugins
- ✨ Duplicate prevention using file paths and names
- ✨ Improved security with proper nonce verification
- ✨ Better internationalization support
- ✨ Full WordPress Coding Standards compliance
- 🐛 Fixed multiple security warnings
- 🎨 Modern admin UI with better UX
- 🎉 Initial release
- ⚡ Basic monitoring for predefined plugins
- 🎨 Color-coded admin bar indicator
- 📊 Last error message display
- None currently reported
- Email notifications when errors detected
- Export error logs to CSV
- Error statistics dashboard
- Multi-site network admin support
- Integration with error tracking services (Sentry, Rollbar)
- Custom alert thresholds
- Error categorization (warnings vs fatal)
- Automated testing suite
- WP-CLI commands
Add to your wp-config.php:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );No. The plugin only runs in the WordPress admin area and uses efficient file reading.
Yes! As long as the plugin writes to the debug log, you can monitor it.
Yes, the plugin works on WordPress Multisite installations.
Debug Log Inspector takes security seriously. We follow WordPress security best practices:
- ✅ Proper nonce verification
- ✅ Data sanitization and validation
- ✅ Capability checks
- ✅ Escaping output
- ✅ No external API calls
- ✅ Local file reading only
Found a security issue? Please report it privately to [email protected]
This plugin is licensed under the GPL v2 or later.
Copyright (C) 2025 Paluhost Web Services
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
Paluhost Web Services
- Website: https://paluhost.co.ke
- GitHub: @paluhost
Thanks to these wonderful people who have contributed to this project:
Want to contribute? See CONTRIBUTING.md
If you find this plugin helpful, please:
- ⭐ Star this repository
- 🐛 Report bugs and issues
- 💡 Suggest new features
- 🔀 Submit pull requests
- 📢 Share with the WordPress community
- ☕ Buy us a coffee
Made with ❤️ by Paluhost Web Services