gorillasolutions

<p>Using this simple plugin, you can update <code>wp-config.php</code> by setting the PHP named constants used for WordPress debugging via a simple UI. Those named constants are <code>WP_DEBUG</code>, <code>WP_DEBUG_LOG</code>, <code>WP_DEBUG_DISPLAY</code>, <code>SCRIPT_DEBUG</code>, and <code>SAVEQUERIES</code>.</p>
<p>This plugin also allows you to view and edit the <code>debug.log</code> file from within the WP Admin panel, without the need to access this file directly through the file system.</p>
<p>Moreover, this plugin introduces a debugging function, <code>gorilla_debug()</code>, that allows you to output debugging messages to either the display or the <code>debug.log</code> file.</p>
<p><em>This plugin is intended for development purposes only</em></p>
<p>For full documentation, visit https://debug.gorilla.solutions and https://debug.gorilla.wtf</p>


Gorilla Debug

Gorilla Debug is a simple WordPress plugin. It is geared towards helping programmers with the development of WordPress themes and plugins.

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.

Gorilla Debug vs What's running