Silkalns

WP Chill

Brian Fegter

Chris Dillon

Razvan Aldea

<p>For admins, developers, and support staff, <strong>Debug This</strong> provides a ton of information about your WordPress installation, all from the front-end admin bar.</p>
<ul>
<li><em>The current WP_Query object</em></li>
<li>Blog info and options</li>
<li>Embed providers</li>
<li>Files in rendered HTML (CSS, images, JavaScript)</li>
<li>Filters and actions</li>
<li>Images sizes</li>
<li>Globals and constants</li>
<li>Menus</li>
<li>Object cache stats</li>
<li>Plugins, must-use plugins, and dropins</li>
<li>Rewrite rules</li>
<li>Queries</li>
<li>PHP and server information</li>
<li>Post attachments</li>
<li>Post types</li>
<li>Scripts and styles enqueued</li>
<li>Shortcodes</li>
<li>Sidebars and widgets</li>
<li>Taxonomies and terms</li>
<li>Themes</li>
<li>Users</li>
<li>WP cron schedules and jobs</li>
<li>WP debug log</li>
</ul>
<p><strong>Debug This</strong> helps you save time and effort when trying to figure out what’s going on. Instead of hardcoding debug snippets or writing complex unit<br />
tests for small functionality, you can simply bring to the surface what you need right from the admin bar.</p>
<p>For example, when viewing a single post, you can see:</p>
<ul>
<li>a list of post attachments,</li>
<li>which menus and sidebars are being displayed,</li>
<li>the post type, post fields, and meta data,</li>
<li>the current query variables and query string,</li>
<li>the rewrite rules applied,</li>
<li>the author,</li>
<li>the terms,</li>
<li>and much more.</li>
</ul>
<h3>Extend</h3>
<h4>Debug This Functions</h4>
<p>New debug modes can be created easily:</p>
<pre><code>add_debug_extension(
    $mode,
    $menu_label,
    $description,
    $callback,
    $group = 'General'
);
</code></pre>
<p><strong>Example</strong></p>
<pre><code>add_debug_extension(
    'actions',
    __('Actions', 'debug-this'),
    __('$wp_actions contains all active registered actions', 'debug-this'),
    'foo_callback',
    'Filters And Actions'
);
function foo_callback($buffer, $template){
    global $wp_actions;
    $debug = print_r($wp_actions, true);
    return $debug;
}
</code></pre>
<p>You can add links to the header of a debug mode page. Place this code within your debug callback function.</p>
<pre><code>add_debug_header_link('http://urltolink', 'Link Label');
</code></pre>
<p>Extensions can be removed as well using <code>remove_debug_extension($mode);</code></p>
<p><strong>No PRE Tags</strong></p>
<p>If you don’t want your debug output to be enclosed in PRE tags, simply set the following in your extension:</p>
<pre><code>Debug_This::$no_pre = true;
</code></pre>
<p><strong>Saved Queries and Execution Time</strong></p>
<p>Retrieve saved queries and execution time by using the following static properties:</p>
<ul>
<li><code>Debug_This::$execution_time</code></li>
<li><code>Debug_This::$queries</code> – SAVEQUERIES must defined as true</li>
</ul>
<p><strong>URL Helpers</strong></p>
<ul>
<li><code>Debug_This::get_current_debug_url()</code> – current URL with the debug query</li>
<li><code>Debug_This::get_escape_url()</code> – used for the debug escape link that links to original page URL</li>
</ul>
<h4>WP Actions</h4>
<ul>
<li><code>debug_this</code> – receives the $mode arg – outputs the debug code sent from the extension modes. The default action is set to priority 5. This allows you to prepend or append any output without conflict using less or greater priorities.</li>
</ul>
<h4>WP Filters</h4>
<p>There are a few filters you can use to customize Debug This to your needs:</p>
<ul>
<li><code>debug_this_template</code> – receives $template arg – Use your own template</li>
<li><code>debug_this_default_mode</code>  – receives $mode arg – Alters the mode for the parent DT admin bar button link.</li>
<li><code>debug_this_output</code> – receives $output, $mode args – Filter debug content before it’s rendered</li>
</ul>
<h4>JavaScript</h4>
<p>To access the built-in Debug This JS functionality, enqueue your custom script with the dependency set to <code>debug-this</code>. Your script will inherit a jQuery dependency.</p>
<p><strong>Object: debugThis</strong></p>
<ul>
<li><code>debugThis.mode</code> – current mode</li>
<li><code>debugThis.defaultMode</code></li>
<li><code>debugThis.template</code> – current included template</li>
<li><code>debugThis.queryVar</code> – the defined query string variable</li>
</ul>
<p><strong>Functions:</strong></p>
<ul>
<li><code>isDebug()</code></li>
<li><code>getDebugMode()</code> – uses <code>isDebug()</code></li>
</ul>
<p><strong>Events:</strong></p>
<p>A jQuery <code>debug-this</code> event is fired from the footer. You can hook into this event with the following;</p>
<pre><code>jQuery(document).bind('debug-this', function(event, debugThis){
    console.log(debugThis);
});
</code></pre>
<h4>Helper Functions</h4>
<p>There are three included functions to help you work with files.</p>
<ul>
<li><code>debug_this_get_file_ownership($file)</code> – returns <code>array('name' => $name, 'group' => $group)</code></li>
<li><code>debug_this_get_file_perms($file)</code> – returns string – Example: 0775</li>
<li><code>debug_this_convert_perms_to_rwx($perms)</code> – returns string – converts permission number to RWX format – Example: 0755 folder becomes drwxr-xr-x</li>
</ul>


Debug This

Very nice, even the phpinfo() colors are displayed correctly.

Great plugin

Peek under the hood with sixty debugging reports just one click away.

Milan Petrovic

<p>DebugPress is an easy-to-use plugin implementing popup for debugging and profiling currently loaded WordPress powered website page with support for intercepting AJAX requests. The main debugger window is displayed as a popup, activated through the button with the Bug integrated into WordPress Toolbar, or floating on the page.</p>
<p>The plugin currently has a total of 22 tabs in the popup debugger window, showing all kinds of information relevant to the current page, WordPress setup, background AJAX calls, and much more.</p>
<p>The plugin doesn’t modify or replace any WordPress files or functions.</p>
<h4>Home and GitHub</h4>
<ul>
<li>Learn more about the plugin: <a href="https://www.dev4press.com/plugins/debugpress/" rel="nofollow ugc">DebugPress Website</a></li>
<li>Contribute to plugin development: <a href="https://github.com/dev4press/debugpress" rel="nofollow ugc">DebugPress on GitHub</a></li>
</ul>
<h4>Quick Overview Video</h4>
<p><iframe loading="lazy" title="DebugPress: Quick Overview" width="750" height="422" src="https://www.youtube.com/embed/-eFnBRLhy-s?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></p>
<h4>Pretty Print for objects</h4>
<p>To display the content of objects or arrays, plugin has pretty print functionality through use of simpler PrettyPrint library, or more robust third-party library Kint. You can choose one or the other from the plugin Settings, Advanced tab.</p>
<h4>Debugger Panels</h4>
<p>Currently, the plugin has the following panels:</p>
<ul>
<li>Basic</li>
<li>Request (optional)</li>
<li>Query (for frontend only)</li>
<li>Content (optional)</li>
<li>Roles (optional)</li>
<li>Constants (optional)</li>
<li>Hooks (optional)</li>
<li>PHP (optional)</li>
<li>Server (optional)</li>
<li>Enqueue (optional)</li>
<li>SQL Queries (if SQL queries logging is enabled)</li>
<li>User (optional, if user is logged in only)</li>
<li>HTTP (optional, if HTTP API calls are captured)</li>
<li>bbPress (optional, on bbPress forum pages only)</li>
<li>Plugins (optional, if plugins store data)</li>
<li>Errors (for all captured PHP errors)</li>
<li>Doing It Wrong (for captured WordPress Doing It Wrong warnings)</li>
<li>Deprecated (for captured PHP deprecated warnings)</li>
<li>AJAX (for captured AJAX calls while page is active)</li>
<li>Store (for any user stored objects during the page loading)</li>
<li>Tools (internal and external tools links)</li>
<li>Debug Log (load content on demand from WordPress ‘debug.log’)</li>
<li>Layout (control the size, position and activation of the popup)</li>
</ul>
<h4>SQL Queries</h4>
<p>This panel lists all the queries WordPress has run. It allows you to order the queries by execution order or length of execution, and all queries can be filtered by the query type, database table it targets or the WordPress function that called it. Every query displays the execution time, order, caller functions stack and fully formatted SQL query that is easy to read. For some Dev4Press created plugins (and that list will grow), DebugPress can detect the source of the query and allow you to filter by the plugin calling the query.</p>
<h4>PHP and WordPress Errors</h4>
<p>Plugin has 3 panels dedicated to showing PHP and WordPress errors and warnings. The Plugin captures this information during the page load, and it shows full debug trace as returned by the PHP debug tracing function.</p>
<h4>AJAX</h4>
<p>The plugin tracks every AJAX call coming through WordPress <code>admin-ajax.php</code> handler, and with every response, it returns HTTP headers with AJAX request basic execution information. Right now, plugin is not returning a list of logged errors or SQL queries, because both can produce huge output that goes over the HTTP header limits. Plan is to introduce these in the future plugin versions.</p>
<h4>Info Panels</h4>
<p>In the administration Tools menu, plugin adds DebugPress Info page showing several panels</p>
<ul>
<li>PHP Info: full formatted results from <code>phpinfo()</code> function</li>
<li>OPCache Info: full settings and statistics for the OPCache PHP extension</li>
<li>MySQL Variables: full MySQL settings retrieved from the database</li>
</ul>
<h4>Plugin Settings</h4>
<p>The plugin has various options controlling the plugin activation, button integration position, user roles that can see the debugger window, options to attempt overriding WordPress debug flags and options controlling the visibility of optional debugger panels.</p>
<h4>Log into Database</h4>
<p>Debugger popup is visible for the request running in the browser. But there are many requests that are happening in the background (AJAX calls, REST API calls…), and for them, you can’t see errors, call information and other stuff in the debugger. Because of that, DebugPress supports logging of various events into database with the use of ‘coreActivity’ plugin, and it is highly recommended to install and use coreActivity.</p>
<p>Log various debug events into a database with the free plugin: <a href="https://wordpress.org/plugins/coreactivity/" rel="ugc">coreActivity Plugin</a>, supporting over 120 events and 10 popular WordPress plugins. DebugPress related events will be logged and available for later analysis, and this includes errors, AJAX calls, and HTTP API calls.</p>
<h4>Documentation and Support</h4>
<p>To get help with the plugin, you can use WordPress.org support forums, or you can use Dev4Press.com support forums.</p>
<ul>
<li>Plugin Documentation: <a href="https://www.dev4press.com/kb/product/debugpress/" rel="nofollow ugc">DebugPress Website</a></li>
<li>Support Forum: <a href="https://support.dev4press.com/forums/forum/plugins-free/debugpress/" rel="nofollow ugc">Dev4Press Support</a></li>
</ul>


DebugPress: Debugger in Popup

Great plugin for developers. Thank you for building and sharing this with the community.

Excellent

Easy-to-use plugin for debugging and profiling website loading, SQL queries analysis, help with development, bug fixing, all in configurable popup.

Debug This vs DebugPress: Debugger in Popup