Jacek Labudda

<p>DockTHOR integrates WordPress with the THOR monitoring platform and automatically reports PHP errors and uncaught exceptions.</p>
<p>The plugin is designed to work silently in the background and has no admin interface. After installation you only need to configure your THOR project credentials.</p>
<h3>Features:</h3>
<ul>
<li>Automatic reporting of PHP errors and uncaught exceptions</li>
<li>Support for custom error filtering</li>
<li>Optional user context information</li>
<li>Customizable configuration via WordPress constants and filters</li>
<li>Minimal performance overhead</li>
</ul>
<p>This plugin is intended for developers and teams who want to monitor errors occurring in WordPress installations.</p>
<p>Installation</p>
<ol>
<li>Upload the plugin files to the <code>/wp-content/plugins/dockthor</code> directory, or install the plugin through the WordPress plugins screen.</li>
<li>Activate the plugin through the <strong>Plugins</strong> menu in WordPress.</li>
<li>Configure your THOR credentials in <code>wp-config.php</code>.</li>
</ol>
<p>Example configuration:<br />
    <code>php<br />
define( 'DOCK_THOR_TOKEN', 'YOUR_THOR_TOKEN' );<br />
define( 'DOCK_THOR_PRIVATE_KEY', 'YOUR_PRIVATE_KEY' );</code><br />
Once configured, the plugin will automatically begin reporting PHP errors.</p>
<p>Configuration</p>
<p>Add the following constants to your <code>wp-config.php</code> file.</p>
<h3>DockTHOR Token</h3>
<p><code>php<br />
define( 'DOCK_THOR_TOKEN', 'YOUR_THOR_TOKEN' );<br />
    `<h3>Private Key</h3></code>php<br />
define( ‘DOCK_THOR_PRIVATE_KEY’, ‘YOUR_PRIVATE_KEY’ );<br />
    `</p>
<h3>Error Types (optional)</h3>
<p>“`php<br />
define( ‘DOCK_THOR_ERROR_TYPES’, E_ALL & ~E_DEPRECATED & ~E_NOTICE & ~E_USER_DEPRECATED );<br />
    <code>Define which PHP errors should be captured.<h3>Send Default PII (optional)</h3><br />
If enabled, additional context such as the logged-in user and IP address will be attached to the event.</code>php<br />
define( ‘DOCK_THOR_SEND_DEFAULT_PII’, true );<br />
    <code><h3>Site Version (optional)</h3><br />
Define the version of your website. This can help track which version of the site generated an error.</code>php<br />
define( ‘DOCK_THOR_VERSION’, ‘v1.0.0’ );<br />
    <code><h3>Environment (optional)</h3><br />
Define the current environment.</code>php<br />
define( ‘DOCK_THOR_ENV’, ‘production’ );<br />
    `</p>
<p>Filters</p>
<p>DockTHOR provides several filters that allow developers to customize behavior.</p>
<h3>dock_thor_user_context</h3>
<p>Allows extending the user context sent to THOR.</p>
<p>Example:<br />
    <code>php<br />
add_filter( 'dock_thor_user_context', function ( array $user ) {<br />
    return array_merge( $user, ['custom_meta' => 'value'] );<br />
});</code></p>
<p>Note: These values may be exposed publicly when used in JavaScript trackers.</p>
<h3>dock_thor_token</h3>
<p>Allows overriding the THOR token.</p>
<p>Example:<br />
    <code>php<br />
add_filter( 'dock_thor_token', function ( $token ) {<br />
    return 'xxxxxxxxxxxxxxxxxxxx';<br />
});</code><br />
Using the <code>DOCK_THOR_TOKEN</code> constant is recommended instead.</p>
<h3>dock_thor_scope</h3>
<p>Allows modifying the THOR scope before events are sent.</p>
<p>Example:<br />
    <code>php<br />
add_filter( 'dock_thor_scope', function ( \Dock\Thor\State\Scope $scope ) {<br />
    $scope->setTag('custom-tag', 'value');<br />
    return $scope;<br />
});</code></p>
<h3>dock_thor_options</h3>
<p>Allows customizing THOR SDK options.</p>
<p>Example:<br />
    <code>php<br />
add_filter( 'dock_thor_options', function ( \Dock\Thor\Options $options ) {<br />
    $options->setSampleRate(0.9);<br />
    return $options;<br />
});</code></p>
<p>Advanced Usage</p>
<h3>High volume of notices</h3>
<p>Some plugins generate large amounts of PHP notices. You can filter them out:<br />
    <code>php<br />
define( 'DOCK_THOR_ERROR_TYPES', E_ALL & ~E_NOTICE );</code></p>
<h3>Capturing handled exceptions</h3>
<p>If you want to report handled exceptions:<br />
    <code>php<br />
try {<br />
    myMethodThatCanThrowAnException();<br />
} catch ( \Exception $e ) {<br />
    if ( function_exists( 'dock_thor_safe' ) ) {<br />
        dock_thor_safe( function ( \Dock\Thor\State\HubInterface $client ) use ( $e ) {<br />
            $client->captureException( $e );<br />
        });<br />
    }<br />
    wp_die( 'An error occurred.' );<br />
}</code></p>
<p>Frequently Asked Questions</p>
<h4>Does this plugin have an admin panel?</h4>
<p>No. DockTHOR works automatically after configuration in <code>wp-config.php</code>.</p>
<h4>Will this slow down my site?</h4>
<p>The plugin is designed to have minimal performance impact. Error events are sent asynchronously when possible.</p>
<h4>Can I disable certain errors?</h4>
<p>Yes. You can configure the error types captured using the <code>DOCK_THOR_ERROR_TYPES</code> constant.</p>


DockTHOR

DockTHOR is a lightweight WordPress integration for sending PHP errors and exceptions to the THOR monitoring platform.

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.

DockTHOR vs Lumiblog Debug Log Inspector