hydr4x

CU Debug Tool is a lightweight yet powerful debugging assistant designed for WordPress developers. Built with a modular architecture, it provides a clean, dark-mode overlay that helps you analyze what is happening under the hood of your WordPress site.
Key Features:
<ul>
<li>Dumps: Tired of cluttering your frontend with <code>var_dump</code> or <code>print_r</code> breaking the layout? Use our helper function <code>cu_dump()</code> to capture variable data cleanly and display it inside the debug panel without affecting your site’s design.</li>
<li>Log Viewer: Don’t want to log in to your server via FTP just to check errors? View the realtime contents of your <code>debug.log</code> file and clear it instantly directly from the toolbar.</li>
<li>ACF Fields Viewer: Working with ACF Blocks or Options pages? Stop guessing the array structure. Instantly inspect clean, readable data for current Post Meta, Global Options, and specific Gutenberg Blocks without the internal metadata noise.</li>
<li>Hooks: Debugging the event-driven architecture? Search for any Action or Filter hook to see a list of all attached callbacks, their priorities, and exactly where they are defined in the code.</li>
<li>Rewrites: Permalink headaches? Test any URL against your active rewrite rules to see exactly which rule matches, what query variables are parsed, and why you might be getting 404 errors.</li>
<li>Globals: Wondering which template is rendering the current page? Need to check active PHP variables, memory usage, or <code>wp-config.php</code> constants? This tab gives you a complete snapshot of the current environment.</li>
<li>Inspector: Your central search engine for WordPress internals. Quickly inspect the raw value of any database Option (<code>get_option</code>) or interactively test specific hooks and rewrites without writing temporary code.</li>
<li>Registry: A comprehensive manifest of your system. View all scheduled WP-Cron events (including overdue status) and use the “Shortcode Detective” to find the exact file and line number where a shortcode is defined.</li>
<li>Assets: Wondering what scripts and styles are loading on the current page? Get a quick, organized list of all enqueued CSS and JavaScript files to debug dependencies.</li>
<li>Mails: Need to verify if WordPress is actually sending emails? Inspect the headers and content of every email sent via <code>wp_mail()</code> during the current request.</li>
<li>SQL Monitor: Analyze database queries on demand. Toggle recording only when you need it to inspect raw SQL, identify slow queries, and spot duplicates without slowing down your site permanently.</li>
<li>Tools: A suite of one-click utilities for developers. Flush rewrite rules, clear Transients (cache), and send test emails to verify SMTP configuration instantly.</li>
</ul>
Security & Performance 
The tool is only visible to administrators (<code>manage_options</code> capability).

CU Debug Tool by CodeUnion

A professional, modular debugging toolbar for developers. Inspect SQL, Rewrite Rules, Hooks, Cron events, and Options without cluttering the frontend.

Modern Tribe, Inc.

Jonathan Brinley

Peter Chester

You can use this plugin to manually log data or to capture logging on WordPress actions. You can capture load time, memory, backrace, data dumps, urls, and server IPs.
This is designed to either be managed using wp-config.php and logging OR using the admin and debugbar plugin ( https://wordpress.org/extend/plugins/debug-bar/ ). Most of the following documentation applies equally to the settings panel or the wp-config.php vars. Either one works fine. The only exception is the DEBUG_LOG configuration which is only supported as a wp-config var.
Firstly, you can manually log things using the following function:
<pre><code>do_action( 'log', $message, $group, $data );
</code></pre>
The $group allows you to selectively output logging based on groups of log messages. The $message is the string you want to see in the log. $data is an optional parameter for the data that you want to display in the log (objects, arrays, or any other sort of data really).
To render messages to the log, you must configure wp-config.php as follows:
Run debug on only these groups. Use ‘ALL’ to debug everything. The group ‘ACTIONS’ is reserved for WordPress actions.
<pre><code>define( 'DEBUG_GROUPS', 'ACTIONS,default,myspecialgroup' );
</code></pre>
Display these outputs in the log for each log message.
<pre><code>define( 'DEBUG_PARAMS', 'time,timedelta,memory,memorydelta,data,backtrace,url,server' );
</code></pre>
WordPress actions that you wish to log.
<pre><code>define( 'DEBUG_ACTIONS', 'wp_head,switch_theme,wp_footer' );
</code></pre>
Optional restriction by URL (useful on MU installs).
<pre><code>define( 'DEBUG_URLS', 'myurl.com' );
</code></pre>
Minimum time in milliseconds required to register a log entry as being slow. Default 0 for no minumum.
<pre><code>define( 'DEBUG_MIN_TIME', 500 );
</code></pre>
Minimum memory in killobytes required to register a log entry as being heavy. Default 0 for no minumum.
<pre><code>define( 'DEBUG_MIN_MEM', 1024 );
</code></pre>
Path to log file or set to TRUE to use php error log. Default FALSE for no logging.
<pre><code>define( 'DEBUG_LOG', '/path/to/writable/log/file' );
</code></pre>
or
<pre><code>define( 'DEBUG_LOG', TRUE );
</code></pre>
<h4>Todo</h4>
<ul>
<li>Add variable for sample rate so that this could run randomly on production installs</li>
<li>Admin panel per site</li>
<li>Admin panel globally</li>
<li>WordPress error logging</li>
<li>Mysql query logging</li>
<li>WP_Error integration</li>
<li>Alerts ex: if this takes more than this much memory then log it…</li>
</ul>

Debugger

You can use this plugin to manually log data or to capture logging on WordPress actions. You can capture load time, memory, backrace, data dumps, urls …

CU Debug Tool by CodeUnion vs Debugger