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.

Modern Tribe, Inc.

Jonathan Brinley

Peter Chester

<p>You can use this plugin to manually log data or to capture logging on WordPress actions. You can capture load time, memory, backrace, data dumps, urls, and server IPs.</p>
<p>This is designed to either be managed using wp-config.php and logging OR using the admin and debugbar plugin ( https://wordpress.org/extend/plugins/debug-bar/ ). Most of the following documentation applies equally to the settings panel or the wp-config.php vars.  Either one works fine. The only exception is the DEBUG_LOG configuration which is only supported as a wp-config var.</p>
<p>Firstly, you can manually log things using the following function:</p>
<pre><code>do_action( 'log', $message, $group, $data );
</code></pre>
<p>The $group allows you to selectively output logging based on groups of log messages. The $message is the string you want to see in the log. $data is an optional parameter for the data that you want to display in the log (objects, arrays, or any other sort of data really).</p>
<p>To render messages to the log, you must configure wp-config.php as follows:</p>
<p>Run debug on only these groups. Use ‘ALL’ to debug everything. The group ‘ACTIONS’ is reserved for WordPress actions.</p>
<pre><code>define( 'DEBUG_GROUPS', 'ACTIONS,default,myspecialgroup' );
</code></pre>
<p>Display these outputs in the log for each log message.</p>
<pre><code>define( 'DEBUG_PARAMS', 'time,timedelta,memory,memorydelta,data,backtrace,url,server' );
</code></pre>
<p>WordPress actions that you wish to log.</p>
<pre><code>define( 'DEBUG_ACTIONS', 'wp_head,switch_theme,wp_footer' );
</code></pre>
<p>Optional restriction by URL (useful on MU installs).</p>
<pre><code>define( 'DEBUG_URLS', 'myurl.com' );
</code></pre>
<p>Minimum time in milliseconds required to register a log entry as being slow. Default 0 for no minumum.</p>
<pre><code>define( 'DEBUG_MIN_TIME', 500 );
</code></pre>
<p>Minimum memory in killobytes required to register a log entry as being heavy. Default 0 for no minumum.</p>
<pre><code>define( 'DEBUG_MIN_MEM', 1024 );
</code></pre>
<p>Path to log file or set to TRUE to use php error log. Default FALSE for no logging.</p>
<pre><code>define( 'DEBUG_LOG', '/path/to/writable/log/file' );
</code></pre>
<p>or</p>
<pre><code>define( 'DEBUG_LOG', TRUE );
</code></pre>
<h4>Todo</h4>
<ul>
<li>Add variable for sample rate so that this could run randomly on production installs</li>
<li>Admin panel per site</li>
<li>Admin panel globally</li>
<li>WordPress error logging</li>
<li>Mysql query logging</li>
<li>WP_Error integration</li>
<li>Alerts ex: if this takes more than this much memory then log it…</li>
</ul>


Debugger

You can use this plugin to manually log data or to capture logging on WordPress actions. You can capture load time, memory, backrace, data dumps, urls …

What's running vs Debugger