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.

Tonya Mork

Debug Toolkit makes debugging your code easier and more enjoyable. It provides you with interactive and helpful tools:
<ul>
<li>Better PHP error interface from (<a href="http://filp.github.io/whoops/" rel="nofollow ugc">Whoops</a>)</li>
<li>Better variable inspection – no need to use <code>var_dump</code>, <code>print_r</code>, or X-debug</li>
<li>An interactive way to back trace the program’s execution order</li>
</ul>
<h3>Better PHP Error Interface from Whoops</h3>
The built-in PHP error container is basic and not as helpful as it could be. On top of that, it’s rather ugly. Wouldn’t you agree?
Whoops gives you a cool interface that is helpful, interactive, and quite nice to look at. Some features:
<ul>
<li>Provides the error message and links to search Google, DuckDuckGo, and Stack Overflow.</li>
<li>Shows the actual code where the error occurred.</li>
<li>Provides an interactive call stack. Click each and the actual code appears in the viewer panel.</li>
<li>Environment and details including GET Data, POST Data, Files, Cookie, Session, Server/Request Data, Environment Variables, and Registered Handlers.</li>
</ul>
See the tools in action in this video
<iframe loading="lazy" title="Introducing the Debug Toolkit Plugin for WordPress" src="https://player.vimeo.com/video/322351688?dnt=1&app_id=122963" width="750" height="422" frameborder="0" allow="autoplay; fullscreen; picture-in-picture; clipboard-write"></iframe>
<h3>Better Variable Inspection</h3>
Though X-debug is powerful, it can be difficult to set up and run. For that reason, it’s common to dump or print out the variable to browser. But the built-in display for the PHP <code>var_dump</code> and <code>print_r</code> is basic.
This plugin includes both two very popular variable dumper tools:
<ul>
<li><a href="https://symfony.com/doc/current/components/var_dumper.html" rel="nofollow ugc">VarDumper from Symfony</a></li>
<li><a href="https://kint-php.github.io/kint/" rel="nofollow ugc">Kint – a modern and powerful PHP debugging helper</a></li>
</ul>
VarDumper provides a simple container that displays where you place it.
On the other hand, Kint provides a more powerful interface that gives you more information such as printing out the expression that was passed into it, the data type, memory size, and the value.
To make it even easier, the following utility functions are available for you to use in your code:
<h4>Available Functions for Inspecting Variable Values</h4>
Let’s explore the functions that are available for you through this plugin. We’ll use the variable inspectors to dump <code>global $post</code>.
Note: You can pass in any variable or function that returns a value.
Dumps the given variable(s):
<pre><code>global $post;

// VarDumper
vdump( $post );

// Kint
dump( $post );
</code></pre>
Dumps the given variable(s) and then exits the program’s execution:
<pre><code>global $post;

// VarDumper
vdump_and_die( $post );

// Kint
dump_and_die( $post );
</code></pre>
In addition, there are alias (shorthand) functions available for you if you prefer shorter function names:
<ul>
<li><code>vd()</code> is an alias for <code>vdump()</code></li>
<li><code>vdd()</code> and <code>vdd()</code> are aliases for <code>vdump_and_die()</code></li>
<li><code>d()</code> is an alias for <code>dump()</code></li>
<li><code>dd()</code> and <code>ddd()</code> are aliases for <code>dump_and_die()</code></li>
</ul>
<h3>Tracing Call Stack</h3>
When debugging, there are times when you need to see the order in which functions were called that lead to a certain point in the program. PHP offers a backtrace that traces back the execution order from the point when the function is invoked.
To make backtracing easier, this plugin provides you with a <code>trace()</code> function and combines it with the variable inspect functions.
For example, if you wanted to trace the call stack to the start of the loop in your theme’s <code>functions.php</code> file, you could use this code:
<pre><code>add_action( 'loop_start', function() {
 trace();
} );
</code></pre>
<h4>Available Trace Functions</h4>
Place these functions at the point where you want to trace the call stack.
<ul>
<li><code>trace();</code></li>
<li><code>trace_vdump();</code> – Combines <code>trace()</code> and <code>vdump()</code></li>
<li><code>trace_dump();</code> – Combines <code>trace()</code> and <code>dump()</code></li>
<li><code>trace_vdump_and_die();</code> – Combines <code>trace()</code> and <code>vdump_and_die()</code></li>
<li><code>trace_dump_and_die();</code> – Combines <code>trace()</code> and <code>dump_and_die()</code></li>
</ul>
In addition, there are alias (shorthand) functions available for you if you prefer shorter function names:
<ul>
<li><code>tracevd();</code> – Combines <code>trace()</code> and <code>vd()</code></li>
<li><code>traced();</code> – Combines <code>trace()</code> and <code>d()</code></li>
<li><code>tracevdd();</code> – Combines <code>trace()</code> and <code>vdd()</code></li>
<li><code>tracedd();</code> – Combines <code>trace()</code> and <code>dd()</code></li>
<li><code>tracevddd();</code> – Combines <code>trace()</code> and <code>vddd()</code></li>
<li><code>traceddd();</code> – Combines <code>trace()</code> and <code>ddd()</code></li>
</ul>
<h3>Admin Bar</h3>
“DEBUG ACTIVE” indicator displays in the WordPress admin bar to alert you when the plugin is active.

Debug Toolkit

This is a must have plugin if you do any kind of PHP coding for WordPress. It makes the difficult aspects of debugging code easy. You'll spend less time debugging and more time writing great functionality.

Very Nice!! A must have...

Thanks for creating this. Another must have in my plugin development workflow!

Another must have!

I've just discovered this plugin after years of WP development and it's super useful! I'm not a fan of xDebugging variables; debugging big objects and arrays with dump() or vdump() is very cool, as you can easily open up and close the tree to navigate through it more easily.
Nice work!

Excellent developer companion plugin

Wonderful plugin to debug errors. A feature request would be to dump the variable in debug.log file as well when define( 'WP_DEBUG_LOG', true ); is set in config file.

Wonderful Plugin

This is a great new plugin, and I love having the option to use Kint or VarDumper, they're invaluable. Having Whoops in there is a major plus. Tonya rocks!

Part of my build setup on every site now.

A must have!

This plugin is amazing, Highly recommended for developers. 

Really worth it !

One of my favourite plugin. Helps a lot with development and debugging. Please keep it update or if we could get a chance to contribute we would love that.

Best Plugin For Devs


This is a must have developers tool. Can't work without it. Highly recommend it.


Saved me many times

Code debug made easier and more enjoyable.

CU Debug Tool by CodeUnion vs Debug Toolkit