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.

Brian Fegter

Chris Dillon

Chris Wallace

<blockquote>
This plugin is up for adoption.
</blockquote>
Kint Debugger is a simple wrapper for <a href="https://github.com/raveren/kint" rel="nofollow ugc">Kint</a>, a debugging tool to output information about variables and traces in a styled, collapsible format that makes understanding deep arrays and objects easier.
No more adding PRE tags before print_r or var_dump!
Kint Debugger works well with the <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a> plugin by creating its own panel to display your debug results.
<h4>Basic Usage</h4>
<pre><code><?php d( $var ); ?>
</code></pre>
Examples:
<pre><code><?php
 global $post;
 $term_list = wp_get_post_terms( $post->ID, 'my_taxonomy', array( 'fields' => 'all' ) );
 d( $term_list );
?>
</code></pre>
Kint Debugger also provides some helper functions for dumping variables that are frequently needed.
<ul>
<li><code>dump_wp_query()</code></li>
<li><code>dump_wp()</code></li>
<li><code>dump_post()</code></li>
<li><code>dump_this( $var, $inline = false )</code> – explained below</li>
</ul>
Examples:
<pre><code><?php dump_post(); ?>

<?php add_action( 'wp_head', 'dump_post' ); ?>
</code></pre>
Obviously, if this plugin is not active, calls to the helper functions will cause errors.
<h4>Your Own Functions</h4>
If you are dumping the same information in different places, consider writing your own helper functions in your theme’s functions file or an mu-plugin. For example:
<pre><code><?php
function my_dump_terms() {
 global $post;
 $term_list = wp_get_post_terms( $post->ID, 'my_taxonomy', array( 'fields' => 'all' ) );
 d( $term_list );
}
?>
</code></pre>
Then at strategic points in your theme or plugin:
<pre><code><?php my_dump_terms(); ?>
</code></pre>
<h4>With Debug Bar</h4>
By default, when <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a> is installed and active, Kint Debugger will send d() output to its Debug Bar panel.
To print debug output inline instead, as if Debug Bar was not active, declare the constant KINT_TO_DEBUG_BAR in your config.php (or really anywhere before your d() call):
<pre><code>define( 'KINT_TO_DEBUG_BAR', false );
</code></pre>
Or to print a specific dump inline, use a helper function with the parameter <code>$inline</code>. The generic <code>dump_this()</code> takes <code>$inline</code> as the second parameter.
Examples:
<pre><code><?php dump_post( true ); ?>

<?php
 global $post;
 $term_list = wp_get_post_terms( $post->ID, 'my_taxonomy', array( 'fields' => 'all' ) );
 dump_this( $term_list , true );
?>
</code></pre>
Kint Debugger overrides Kint’s d() function in order to buffer its output for Debug Bar. If you already have a modified d() function, you need to prevent the override in one of two ways.
<ol>
<li>Move your modified d() function to an mu-plugin. Kint Debugger checks if the function exists before declaring it so putting yours in an mu-plugin is the only way to ensure it exists first.</li>
<li>Declare KINT_TO_DEBUG_BAR as described above.</li>
</ol>
<h4>Restricting Output</h4>
To restrict visibility, use the <code>kint_debug_display</code> filter. For example, to prevent non-admins from seeing the debug output:
<pre><code>add_filter( 'kint_debug_display', function( $allow ) { return is_super_admin(); } );
</code></pre>
<h4>Try these plugins too</h4>
<ul>
<li><a href="https://wordpress.org/plugins/what-the-file/" rel="ugc">What The File</a> – Identify template files without fail.</li>
<li><a href="https://wordpress.org/plugins/debug-this/" rel="ugc">Debug This</a> – Peek under the hood with sixty debugging reports just one click away.</li>
</ul>

Kint Debugger

Dump variables and traces in an organized and interactive display. Integrates seamlessly with Debug Bar.

CU Debug Tool by CodeUnion vs Kint Debugger