Daniel Dvorkin

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.
To log things manually, you can use:
<pre><code>browser()->log ( $var, $label );
browser()->warn ( $var, $label );
browser()->info ( $var, $label );
browser()->error( $var, $label );
</code></pre>
Also, commandas are chainable:
<pre><code>browser()->log( 'This is a log...' )->error( '...and this is an error' );
</code></pre>
For example, to log all your main query’s query_vars:
<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>
wplinb-match-wp-debug: Set to true to only log when wp_debug is true. To prevent logging when wp_debug is false:
<pre><code>add_filter( 'wplinb-match-wp-debug', '__return_true' );
</code></pre>
wplinb-enabled: To disable logging completely. It takes precedence over wplinb-match-wp-debug. To disable logging:
<pre><code>add_filter( 'wplinb-enabled', '__return_false' );
</code></pre>
<h4>Profiling</h4>
The plugin includes a really simple function to allow you to track execution time of different parts of your code.
<pre><code>browser()->timer( $key, $log = false );
</code></pre>
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.
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.
Example 1: Sequential use, log manually.
<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>
Example 2: Start and end in different places, log automatically.
<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>
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.
In exactly the same way, you can use the function
<pre><code>Browser()->memory( $key, $log = false );
</code></pre>
to measure delta of memory consumption from your first call and your second call with the same $key.
Example:
<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 …

rsprta

Blog Terminal generates a terminal-like box that you can use to demonstrate terminal output or show the entry of terminal/console commands in a manner that is more demonstrative of actually using a Linux/Unix terminal or Windows cmd shell.
The code is a fork of Post Terminal, which is a fork of WP-Terminal which in turn is a modification of WP-Syntax, a source code highlighter plugin for WordPress.
Unlike Post terminal, it uses <code>[terminal]</code> shorthand for the terminal box. It also shows prompt only on lines explitly set to do that.
<h4>Basic Usage</h4>
The most basic usage is to wrap your terminal blocks with <code>[terminal][/terminal]</code> tags. If no further options are defined within the tag a generic prompt is generated using ‘user@computer’ with no working directory shown. This is similar to exporting PS1=”\u@\h:$ ” in sh(1), setting prompt=”%n@%m:$ ” in csh(1), etc. 
Other options available within the tag are user=”user”, computer=”computer”, and cwd=”/path/to/directory”. These allow you to override the generic user@computer settings as well as provide a ‘current working directory’. 
The prompt is only shown on the lines starting with ‘$ ‘. So you can mix commands with simulated terminal output.
<h3>Usage</h3>
Wrap terminal blocks with <code>[terminal user="username" computer="computername" cwd="/path/to/directory"]</code> and <code>[\terminal]</code>. They are all optional. “user” and “computer” will be shown if you don’t provide them, cwd is purely optional.
Example 1: No customized command
<pre><code>[terminal]
$ ls -a
[/terminal]
</code></pre>
Example 2: User and computer customizations
<pre><code>[terminal user="tux" computer="linux"]
$ ls -a
[/terminal]
</code></pre>
Example 3: Customizing just the user
<pre><code>[terminal user="dak"]
$ ls -a
[/terminal]
</code></pre>
Example 4: Customizing user, computer and displaying a working directory
<pre><code>[terminal user="root" computer="linuxserver" cwd="/usr/src/linux"]
$ make mrproper
 ...
 ... 
[/terminal]
</code></pre>

Blog Terminal

Blog Terminal provides a terminal-like box for embedding terminal commands within pages or posts.

WP Log in Browser vs Blog Terminal