Stefan Boonstra

<p>Developer Tools currently only supports logging of variables, errors and exceptions. Features such as profiling a<br />
website’s database queries and server memory usage are not yet supported.</p>
<h4>Features</h4>
<ul>
<li>Log any type of variable</li>
<li>Log any catchable error or exception</li>
<li>Watch for new log entries through the backend interface</li>
<li>No bloating the live environment with developer dumps</li>
<li>That’s it for now 🙂</li>
</ul>
<h4>Need the (uncompressed) source code?</h4>
<p>Find the Slideshow project’s source code in my <a href="https://github.com/Boonstra/WordPress-Developer-Tools" rel="nofollow ugc">GitHub</a> repository. The<br />
uncompressed files can be compiled using <a href="http://alphapixels.com/prepros/" rel="nofollow ugc">Prepros</a>, or <a href="http://incident57.com/codekit/" rel="nofollow ugc">CodeKit</a>.</p>
<h3>Links</h3>
<ul>
<li><a href="http://stefanboonstra.com/" rel="nofollow ugc">Stefan Boonstra</a></li>
<li><a href="https://github.com/Boonstra/WordPress-Developer-Tools" rel="nofollow ugc">GitHub</a></li>
</ul>


Basic Developer Tools

Basic Developer Tools helps developers to log any variable, error or exception of which they need the value, without bloating their live environment.

Daniel Dvorkin

<p>I’m working on a nice admin screen to config auto-logging of some common things (like wp_query in pre_get_posts and wp), and some other goodies.</p>
<p>To log things manually, you can use:</p>
<pre><code>browser()->log  ( $var, $label );
browser()->warn ( $var, $label );
browser()->info ( $var, $label );
browser()->error( $var, $label );
</code></pre>
<p>Also, commandas are chainable:</p>
<pre><code>browser()->log( 'This is a log...' )->error( '...and this is an error' );
</code></pre>
<p>For example, to log all your main query’s query_vars:</p>
<pre><code>add_filter( 'pre_get_posts', 'log_wp_query', 10000 );

function log_wp_query( $query ) {
    if ( $query->is_main_query() )
        browser()->log( $query->query_vars, 'pre_get_posts' );

    return $query;
}
</code></pre>
<h4>Filters</h4>
<p><em>wplinb-match-wp-debug</em>: Set to true to only log when wp_debug is true. To prevent logging when wp_debug is false:</p>
<pre><code>add_filter( 'wplinb-match-wp-debug', '__return_true' );
</code></pre>
<p><em>wplinb-enabled</em>: To disable logging completely. It takes precedence over <em>wplinb-match-wp-debug</em>. To disable logging:</p>
<pre><code>add_filter( 'wplinb-enabled', '__return_false' );
</code></pre>
<h4>Profiling</h4>
<p>The plugin includes a really simple function to allow you to track execution time of different parts of your code.</p>
<pre><code>browser()->timer( $key, $log = false );
</code></pre>
<p>The first time you call this function with a given $key (string) it will start a timer, and return false. You can start as many timers as you want, using different $key values. You can ignore the second parameter for this first call.</p>
<p>The second time you call this function with a given $key, it will return the ellapsed time in seconds since you started this $key timer. If you set the second parameter to true, it will also log this value to the browser.</p>
<p>Example 1: Sequential use, log manually.</p>
<pre><code>browser()->timer( 'Mega loop' );
for ( $i = 0; $i < 1000000; $i++ ) {
    //do something
}
$time = browser()->timer( 'Mega loop' );
browser()->log( $time, 'The mega loop took:' );
</code></pre>
<p>Example 2: Start and end in different places, log automatically.</p>
<pre><code>add_action( 'posts_selection', 'start_timer', 100 );
add_filter( 'the_posts', 'end_timer', 1, 2 );

function start_timer( $query ) {
    browser()->timer( 'Main query time' );
}

function end_timer( $posts, $query ) {
    browser()->timer( 'Main query time', true );
    return $posts;
}
</code></pre>
<p><em>This is not a good way of measuring how much time a query takes to run, it’s just to illustrate how to use the timer.</em></p>
<p>In exactly the same way, you can use the function</p>
<pre><code>Browser()->memory( $key, $log = false );
</code></pre>
<p>to measure delta of memory consumption from your first call and your second call with the same $key.</p>
<p>Example:</p>
<pre><code>Browser()->memory( 'testing' );
$test = array();
for ( $i = 0; $i < 100; $i++ ) {
    $test[$i] = md5( rand( 1, $i ) );
}
Browser()->memory( 'testing', true );


Browser()->memory( 'testing' );
$test = array();
for ( $i = 0; $i < 10000; $i++ ) {
    $test[$i] = md5( rand( 1, $i ) );
}
Browser()->memory( 'testing', true );
</code></pre>


WP Log in Browser

Allows you to log data from your PHP WordPress code to your browser's console.

Annoyed you can't var_dump from an AJAX handler? Not anymore …

Basic Developer Tools vs WP Log in Browser