hydr4x

<p>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.</p>
<p><strong>Key Features:</strong></p>
<ul>
<li><strong>Dumps:</strong> 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><strong>Log Viewer:</strong> 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><strong>ACF Fields Viewer:</strong> 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><strong>Hooks:</strong> 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><strong>Rewrites:</strong> 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><strong>Globals:</strong> 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><strong>Inspector:</strong> 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><strong>Registry:</strong> 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><strong>Assets:</strong> 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><strong>Mails:</strong> 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><strong>SQL Monitor:</strong> 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><strong>Tools:</strong> 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>
<p><strong>Security & Performance</strong><br />
The tool is only visible to administrators (<code>manage_options</code> capability).</p>


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.

Viktor Szépe

<h4>Only for development!</h4>
<h4>Now with OPcache memory consumption support</h4>
<p>This plugin dumps the colorized filenames and memory consumptions or file sizes after the normal WordPress HTML output, after the closing html tag. This generates invalid HTML but gives you an overview of loaded plugins and the current theme.</p>
<p><em>What’s running</em> lists all files parsed and executed by the PHP engine. It can be used for plugin or theme refactoring.</p>
<h4>Now you can highlight your own plugin and theme</h4>
<p>Provide a part of its path in wp-config.php:</p>
<pre><code>define( 'WHATS_RUNNING_HIGHLIGHT', 'wp-content/plugins/my-plugin' ); </code></pre>
<h4>Color codes</h4>
<ul>
<li>your code is highlighted with YELLOW background</li>
<li>plugin files are in BLUE</li>
<li>themes files are in ORANGE</li>
<li>files in the wp-includes directory are in GREEN</li>
<li>files in the wp-admin directory are in GREY</li>
<li>all other files are in RED</li>
<li>VIOLET bar after the filename represents the file size ( 0.5 kB/px )</li>
<li>DARK MAGENTA bar after the filename represents the OPcache memory consumption ( 1 kB/px )</li>
</ul>
<h4>Links</h4>
<p>You can watch <a href="https://core.trac.wordpress.org/ticket/28364" rel="nofollow ugc">WP core bug #28364</a> to get more information about <a href="https://github.com/szepeviktor/WPHW/blob/master/wp-entry-points.md" rel="nofollow ugc">WordPress entry points</a>.</p>
<p>You can find some documentaion here what makes a WordPress plugin efficient: https://github.com/szepeviktor/WPHW</p>
<p>Development of this plugin goes on on <a href="https://github.com/szepeviktor/whats-running" rel="nofollow ugc">GitHub</a>.</p>


What's running

Lists WordPress require() calls mainly for plugin code refactoring.

CU Debug Tool by CodeUnion vs What's running