Yevhen Leonidov

<p>Working with <code>WP_DEBUG</code> enabled often floods the screen with notices and deprecation warnings from third-party plugins and themes – things you neither wrote nor can fix. GLOBUS Debug Control lets you filter out the noise and focus on what actually matters.</p>
<p>All settings are available in <strong>Settings – GLOBUS Debug Control</strong>. The plugin provides eight tabs: Settings, WP_DEBUG, Error Log, Cron Tasks, Transients, Autoloaded, HTTP Log, and Constants. No code editing needed.</p>
<h4>Settings tab</h4>
<p><strong>Choose which errors to see</strong></p>
<p>Turn off specific PHP error types independently:</p>
<ul>
<li>Notices – informational messages that rarely indicate a real problem</li>
<li>Deprecated – warnings about outdated functions, usually from third-party code</li>
<li>Warnings – optional, keep them on if you are actively debugging</li>
<li>Strict – PHP 7 strict standards messages (not applicable in PHP 8+)</li>
</ul>
<p><strong>Control error display</strong></p>
<p>Three modes for showing errors on screen:</p>
<ul>
<li><strong>Inherit</strong> – follows your <code>wp-config.php</code> settings (default, non-intrusive)</li>
<li><strong>On</strong> – always show errors, useful during active development</li>
<li><strong>Off</strong> – hide all errors from screen even if <code>WP_DEBUG_DISPLAY</code> is on</li>
</ul>
<p>Errors are always hidden automatically during AJAX requests, REST API calls, WP-Cron, and WP-CLI, so your API responses stay clean regardless of the display setting.</p>
<p><strong>Error logging</strong></p>
<p>Enable logging to capture errors in a file instead of (or in addition to) showing them on screen:</p>
<ul>
<li>Set a custom log file path (absolute or relative to <code>wp-content/</code>)</li>
<li>Set a maximum log file size (1-100 MB); the file rotates automatically when the limit is reached</li>
<li>Defaults to <code>wp-content/debug.log</code> if no path is specified</li>
</ul>
<p><strong>Remove the php-error CSS class</strong></p>
<p>When WordPress encounters a PHP error, it adds a <code>php-error</code> class to the <code><body></code> tag, which can break your page layout. This option removes it via both CSS and JavaScript so your front-end and admin look normal even in debug mode.</p>
<p><strong>Early error interception (optional)</strong></p>
<p>WordPress loads plugins in alphabetical order. If another plugin throws an error before GLOBUS Debug Control initialises, those errors will not be filtered. Enabling the <strong>MU-plugin dropin</strong> installs a small helper file into <code>wp-content/mu-plugins/</code> that runs before any regular plugin, ensuring your filter settings apply from the very start of the request. The dropin is removed automatically when the plugin is deactivated or uninstalled.</p>
<h4>WP_DEBUG tab</h4>
<p>Toggle the five most important debug constants directly from the admin panel without editing <code>wp-config.php</code>:</p>
<ul>
<li><code>WP_DEBUG</code> – master debug switch</li>
<li><code>WP_DEBUG_LOG</code> – write errors to a log file</li>
<li><code>WP_DEBUG_DISPLAY</code> – show errors on screen</li>
<li><code>SCRIPT_DEBUG</code> – use unminified core JS/CSS</li>
<li><code>SAVEQUERIES</code> – log all database queries</li>
</ul>
<p>The plugin locates your <code>wp-config.php</code> automatically and patches it in place, adding the constant if it is missing or updating the existing value. Commented-out defines and block-comment sections are never touched. The current status of <code>WP_DEBUG</code> is always visible as a badge in the plugin header.</p>
<h4>Error Log tab</h4>
<p>Displays the contents of your <code>debug.log</code> file directly in the admin panel using a CodeMirror editor with line numbers. Lines are color-coded by severity: fatal/parse errors, warnings, notices/deprecations, and cron-related messages. The log is paginated (200 lines per page), supports live polling for new entries, and can be downloaded or cleared with one click. Large log files (over 2 MB) are read from the tail to keep memory usage low.</p>
<h4>Cron Tasks tab</h4>
<p>Lists all scheduled WordPress cron events with hook name, next run time, recurrence interval, and arguments. Summary cards show total events, overdue count, orphaned hooks, and duplicates. Overdue events are highlighted. You can run any event immediately or delete orphaned hooks directly from the table.</p>
<h4>Transients tab</h4>
<p>Displays database-stored WordPress transients from the options table with key name, data size, and expiration time. Transients stored in an external object cache (Redis, Memcached) are not shown. Expired transients are highlighted. You can delete individual transients or purge all expired ones in one click. Summary cards show total count, expired count, and total data size.</p>
<h4>Autoloaded tab</h4>
<p>Lists autoloaded options from <code>wp_options</code> sorted by data size (top 200). Shows the option name and value size. Summary cards display total autoloaded row count and total payload size with warnings when thresholds are exceeded (over 800 KB or over 100 rows). This is a read-only diagnostic view to help identify options that inflate every WordPress request.</p>
<h4>HTTP Log tab</h4>
<p>Captures outgoing WordPress HTTP API requests (<code>wp_remote_get</code>, <code>wp_remote_post</code>, etc.) via the <code>http_api_debug</code> hook. Capturing must be explicitly enabled and stores up to 100 entries (6-hour TTL). Each entry shows the request URL, HTTP method, status code, response time, and transport class. Useful for spotting slow or failing external API calls.</p>
<h4>Constants tab</h4>
<p>Displays all WordPress-related PHP constants defined at runtime, grouped by category: Debug, Performance, Security, Database, Auth and Salts, Paths, and Other WP_* constants. Sensitive values (database password, auth keys, salts) are automatically masked. This is a read-only reference view.</p>


GLOBUS Debug Control

WordPress debug toolkit: filter errors, toggle WP_DEBUG, view error logs, monitor cron, transients, HTTP requests, and more.

welaika

<p><a href="https://github.com/welaika/wordless" rel="nofollow ugc">Wordless</a> is the WP themes framework developed and used by <a href="http://dev.welaika.com" rel="nofollow ugc">weLaika</a>.</p>
<p>As we wrote in the Wordless README:</p>
<pre><code>« Wordless is not meant to be a bloated, all-included tool.
This is why we recommend adding some other plugins
to get the most out of your beautiful WP developer life »
</code></pre>
<p><em>Wordless Extender</em> (WLE from now on) is a starting point for every Wordless theme.<br />
Let’s take a look in depth.</p>
<h3>Plugin Manager</h3>
<p>Never change a winning team! These are our <em>starred</em> plugins; with these we cover the 90% of our developing needs.<br />
You’ll have a control panel inside WLE to list, enable, disable and upgrade plugins from the collection; never search that useful plugin crawling the WP.org repo and have team kickstart projects with always the same plugin set.</p>
<h3>Config Constants</h3>
<p>Manage WP constants (stored in your wp-config.php) directly within the WP backend.</p>
<p>We got inspired by WordPress <a href="https://codex.wordpress.org/Editing_wp-config.php" rel="nofollow ugc">guidelines</a> and we crafted this little control panel. It is intended for advanced users: we are not interested in making things easy, but we’d like to remember important/complex/abstruse settings and have them always just one click away.</p>
<p>Everytime you’ll update these configs <code>wp-config.php</code> file will be backed-up in <code>wp-config.php.orig</code>. Keep in mind.</p>
<h3>Security fixes</h3>
<p>This is the most important section: improving security.<br />
Most of the tricks are directly from <a href="https://codex.wordpress.org/Hardening_WordPress" rel="nofollow ugc">Hardening WordPress</a> guide; others are tricks discovered on battlefield.</p>
<p>You have to know what you are doing. Follow the comments in the panel if you are confused. Remind that when you’ll let the plugin rewrite your <code>.htaccess</code> file, it will take a backup copy of the last version in <code>.htaccess.orig</code>.</p>
<p>If you are asking about the things are we doing with your <code>.htaccess</code> go read the template in <code>resources/htaccess.tpl</code>.<br />
Essentially we’ll block access to various files and locations.<br />
We are always at work to improve this section, so if you have some tips open an issue or send a pull request.</p>
<h3>Wordless integration</h3>
<p>WLE menu in the WP backend, will be integrated with the Wordless 0.4+ backend menu, creating <em>one place to rule them all!</em></p>
<h3>Need more tools?</h3>
<p>Visit <a href="http://wptools.it" rel="nofollow ugc">WordPress Tools</a>.</p>
<h3>Licence</h3>
<p>(The MIT License)</p>
<p>Copyright © 2014-2015 weLaika</p>
<p>Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ‘Software’), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:</p>
<p>The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.</p>
<p>THE SOFTWARE IS PROVIDED ‘AS IS’, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>


Wordless Extender

Wordless Extender is a starting point for everyone: list of commonly used plugins, wp-config.php / .htaccess configuration and security improvements.

GLOBUS Debug Control vs Wordless Extender