Milan Petrovic

<p>Standard display of pages in WordPress can be a problem if you have a lot of pages with sub-pages causing the widget with list of pages to take a lot of space in the sidebar. With this widget you can use on of the 4 currently supported methods of navigation:</p>
<h4>Pages list display methods</h4>
<ul>
<li><strong>Full Hierarchy</strong>: Displays complete hierarchy of all pages in the blog.</li>
<li><strong>Custom Parent</strong>: Displays only sub-pages for a parent page of your choice.</li>
<li><strong>Navigator</strong>: Dynamic list of pages, based on the currently active page.</li>
<li><strong>Selected</strong>: Select pages to display, all other will be ignored.</li>
</ul>
<h4>Important URL’s</h4>
<ul>
<li><a href="https://plugins.dev4press.com/gd-pages-navigator/" rel="nofollow ugc">Plugin Home</a></li>
<li><a href="https://support.dev4press.com/forums/forum/plugins-free/gd-pages-navigator/" rel="nofollow ugc">Support Forum</a></li>
</ul>


GD Pages Navigator

Simple and powerful widget plugin to create enhanced navigation for hierarchical post types, based on different criteria for filtering and display of  …

<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.

GD Pages Navigator vs DebugPress: Debugger in Popup