Tonya Mork

<p>This WordPress plugin is a wrapper for the <a href="https://kint-php.github.io/kint/" rel="nofollow ugc">Kint</a> PHP Debugger utility version 1.x.  Now instead of using var_dump() or print_r(), you simply use d() with zero, nadda, no formatting required.</p>
<p>Use this tool when you are debugging your website, in place of <strong><a href="http://php.net/manual/en/function.var-dump.php" rel="nofollow ugc">var_dump()</a></strong>, <strong><a href="http://php.net/manual/en/function.print-r.php" rel="nofollow ugc">print_r()</a></strong> and <strong><a href="http://php.net/manual/en/function.debug-backtrace.php" rel="nofollow ugc">debug_backtrace()</a></strong>.</p>
<h4>Handy Tools</h4>
<p>Some handy tools just for the PHP Developer:</p>
<ul>
<li><code>d( $var );</code> to render a collapsible UI container which displays your variable data in “the most informative way”</li>
<li><code>ddd( $var );</code> same as d() except that it also executes <code>die()</code> to halt execution.</li>
</ul>
<p>Here are some variations of <code>d()</code> to give you the display you want:</p>
<ul>
<li><code>~d( $var );</code> outputs in plain text format.</li>
<li><code>+d( $var );</code> disregards depth level limits and outputs everything</li>
<li><code>!d( $var );</code> shows expanded rich output</li>
<li><code>-d( $var );</code> attempts to ob_clean() the previous output (dump something inside of HTML)</li>
</ul>
<h4>Profiler</h4>
<p>Kint even includes a naïve profiler, which can help you analyze which blocks of code take longer than others:</p>
<pre><code>Kint::dump( microtime() ); // just pass microtime()
sleep( 1 );
Kint::dump( microtime(), 'after sleep(1)' );
sleep( 2 );
ddd( microtime(), 'final call, after sleep(2)' );
</code></pre>
<p>See <a href="https://wordpress.org/extend/plugins/kint-php-debugger/screenshots/" rel="ugc">screenshot 2</a> for what is rendered out in your browser.</p>
<h3>Admin Bar</h3>
<p>“KINT ACTIVE” indicator displays in the WordPress admin bar to alert you when the plugin is active.</p>


Kint PHP Debugger

Really like to debug with Kint, and this plugin makes it much easier.



Useful

Love this plugin. Displays more than var_dump does and is so much easier to read the output. Handy toggle to display more information is very helpful. Love that ddd() option to display and stop execution. Thank you!!!



Improves Workflow and Troubleshooting

Thanks for this plugin. It makes debugging my arrays of arrays of arrays much simpler. ;)

Works great!

Saves a lot of time when writing plugins and themes.
Thanks!

Update 2/11/2021 - even though this plugin hasn't had any updated in more than 2 years, it is still working just great.

Does what it says

Kint is a modern and powerful PHP debugging helper, which requires zero-setup and replaces var_dump(), print_r() and debug_backtrace().

Brian Fegter

Chris Dillon

Chris Wallace

<blockquote>
<p>This plugin is up for adoption.</p>
</blockquote>
<p><strong>Kint Debugger</strong> is a simple wrapper for <a href="https://github.com/raveren/kint" rel="nofollow ugc">Kint</a>, a debugging tool to output information about variables and traces in a styled, collapsible format that makes understanding deep arrays and objects easier.</p>
<p><em>No more adding PRE tags before print_r or var_dump!</em></p>
<p>Kint Debugger works well with the <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a> plugin by creating its own panel to display your debug results.</p>
<h4>Basic Usage</h4>
<pre><code><?php d( $var ); ?>
</code></pre>
<p>Examples:</p>
<pre><code><?php
    global $post;
    $term_list = wp_get_post_terms( $post->ID, 'my_taxonomy', array( 'fields' => 'all' ) );
    d( $term_list );
?>
</code></pre>
<p>Kint Debugger also provides some helper functions for dumping variables that are frequently needed.</p>
<ul>
<li><code>dump_wp_query()</code></li>
<li><code>dump_wp()</code></li>
<li><code>dump_post()</code></li>
<li><code>dump_this( $var, $inline = false )</code> – explained below</li>
</ul>
<p>Examples:</p>
<pre><code><?php dump_post(); ?>

<?php add_action( 'wp_head', 'dump_post' ); ?>
</code></pre>
<p>Obviously, if this plugin is not active, calls to the helper functions will cause errors.</p>
<h4>Your Own Functions</h4>
<p>If you are dumping the same information in different places, consider writing your own helper functions in your theme’s functions file or an mu-plugin. For example:</p>
<pre><code><?php
function my_dump_terms() {
     global $post;
     $term_list = wp_get_post_terms( $post->ID, 'my_taxonomy', array( 'fields' => 'all' ) );
     d( $term_list  );
}
?>
</code></pre>
<p>Then at strategic points in your theme or plugin:</p>
<pre><code><?php my_dump_terms(); ?>
</code></pre>
<h4>With Debug Bar</h4>
<p>By default, when <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a> is installed and active, Kint Debugger will send d() output to its Debug Bar panel.</p>
<p>To print debug output inline instead, as if Debug Bar was not active, declare the constant KINT_TO_DEBUG_BAR in your config.php (or really anywhere before your d() call):</p>
<pre><code>define( 'KINT_TO_DEBUG_BAR', false );
</code></pre>
<p>Or to print a specific dump inline, use a helper function with the parameter <code>$inline</code>. The generic <code>dump_this()</code> takes <code>$inline</code> as the second parameter.</p>
<p>Examples:</p>
<pre><code><?php dump_post( true ); ?>

<?php
    global $post;
    $term_list = wp_get_post_terms( $post->ID, 'my_taxonomy', array( 'fields' => 'all' ) );
    dump_this( $term_list , true );
?>
</code></pre>
<p>Kint Debugger overrides Kint’s d() function in order to buffer its output for Debug Bar. If you already have a modified d() function, you need to prevent the override in one of two ways.</p>
<ol>
<li>Move your modified d() function to an mu-plugin. Kint Debugger checks if the function exists before declaring it so putting yours in an mu-plugin is the only way to ensure it exists first.</li>
<li>Declare KINT_TO_DEBUG_BAR as described above.</li>
</ol>
<h4>Restricting Output</h4>
<p>To restrict visibility, use the <code>kint_debug_display</code> filter. For example, to prevent non-admins from seeing the debug output:</p>
<pre><code>add_filter( 'kint_debug_display', function( $allow ) { return is_super_admin(); } );
</code></pre>
<h4>Try these plugins too</h4>
<ul>
<li><a href="https://wordpress.org/plugins/what-the-file/" rel="ugc">What The File</a> – Identify template files without fail.</li>
<li><a href="https://wordpress.org/plugins/debug-this/" rel="ugc">Debug This</a> – Peek under the hood with sixty debugging reports just one click away.</li>
</ul>


Kint Debugger

Dump variables and traces in an organized and interactive display. Integrates seamlessly with Debug Bar.

Kint PHP Debugger vs Kint Debugger