Automattic

Thorsten Ott

<p>This plugins adds more features to the debug-bar and is mainly aimed at developers who like to debug their code or want to measure runtimes to find glitches in their code.<br />
It also allows lookup of variables by adding simple code snippets in your source.</p>
<p>Please note that this plugin should be used solely for debugging or on a development environment and is not intended for use in a production site.</p>
<h3>Requirements</h3>
<p>This plugin requires <a href="https://wordpress.org/extend/plugins/debug-bar" rel="ugc">the debug-bar plugin >0.5</a> and a developers’ brain to work correctly.</p>
<h3>Usage</h3>
<h4>Usage example to debug the loop of a theme</h4>
<p>Add your checkpoints in the index.php or any other template file as shown below.</p>
<pre><code><?php if (have_posts()) : ?>

<?php Debug_Bar_Extender::instance()->checkpoint('loop start'); ?>

<?php while (have_posts()) : the_post(); ?>

<?php Debug_Bar_Extender::instance()->trace_var( $post ); ?>

<?php Debug_Bar_Extender::instance()->checkpoint('loop1'); ?>

<div <?php post_class() ?> id="post-<?php the_ID(); ?>">
<?php //before_post(); ?>
<h2><a href="<?php the_permalink() ?>" rel="bookmark" title="<?php printf(__('Permanent Link to %s', 'kubrick'), the_title_attribute('echo=0')); ?>"><?php the_title(); ?></a></h2>
<small><?php the_time(get_option('date_format')) ?> by <?php the_author() ?></small>
<div class="entry">
<?php the_content(__('Read the rest of this entry &raquo;', 'kubrick')); ?>
</div>
<p class="postmetadata"><?php the_tags(__('Tags:', 'kubrick') . ' ', ', ', '<br />'); ?> <?php printf(__('Posted in %s', 'kubrick'), get_the_category_list(', ')); ?> | <?php edit_post_link(__('Edit', 'kubrick'), '', ' | '); ?> <?php comments_popup_link(__('No Comments »', 'kubrick'), __('1 Comment »', 'kubrick'), __('% Comments »', 'kubrick')); ?></p>
<?php after_post(); ?>
</div>

<?php Debug_Bar_Extender::instance()->checkpoint('loop2'); ?>

<?php endwhile; ?>

<?php Debug_Bar_Extender::instance()->checkpoint('loop end'); ?>

<div class="navigation">
<div class="alignleft"><?php next_posts_link(__('&laquo; Older Entries', 'kubrick')) ?></div>
<div class="alignright"><?php previous_posts_link(__('Newer Entries &raquo;', 'kubrick')) ?></div>
</div>
<?php else : ?>
</code></pre>
<h3>Advanced usage</h3>
<p>Looking at the source of the debug-bar-extender.php you will notice that there are various filters to control the default settings. This is useful when you are working on a multisite install and want to use the debug bar without having to adjust the settings every time. Here’s an example of how settings enforced by a php file in mu-plugins/ could look like</p>
<pre><code>add_filter( 'debugbarextender_default_settings', 'my_debug_bar_extender_settings' );
// enforce debug bar settings
function my_debug_bar_extender_settings( $default_settings ) {
    $default_settings = array(
            'enable_profiler'               => 1,
            'enable_variable_lookup'        => 1,
            'track_default_vars'            => 0,
            'add_default_checkpoints'       => 1,
            'savequeries_debugmode_enable'  => 1,
            'use_error_log'                 => 0,
            'allow_url_settings'            => 1,
            'enable_admin_bar_menu'         => 1,
    );
    return $default_settings;
}

add_filter( 'debugbarextender_default_checkpoint_actions', 'my_debug_bar_extender_checkpoints' );
// initiate some default checkpoints
function my_debug_bar_extender_checkpoints( $default_checkpoints ) {
    $default_checkpoints = array(
                    'muplugins_loaded',
                    'wp_head',
                    'wp_footer',
                    'loop_start',
                    'loop_end',
                    'shutdown',
    );
    return $default_checkpoints;
}
</code></pre>
<h3>Wishlist</h3>
<p>This is a work in progress, so feel free to pass by on <a href="http://hitchhackerguide.com/wordpress-plugins/debug-bar-extender/" rel="nofollow ugc">our plugin page</a> and leave us<br />
your suggestions in the comments.</p>


Debug-Bar-Extender

Extends the debug-bar plugin with additional tabs to measure runtimes between checkpoints and lookup variable content.

Juliette Reinders Folmer

<p>Debug Bar Shortcodes adds a new panel to the <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a> that displays the registered shortcodes for the current request.</p>
<p>Additionally it will show you:</p>
<ul>
<li>Which function/method is called by the shortcode</li>
<li>Whether the shortcode is used on the current post/page/post type and how (only when on singular)</li>
<li>Any additional information available about the shortcode, such as a description, which parameters it takes, whether or not it is self-closing.<br />
<em>Want to control the additional information displayed about your own shortcodes ? You can! See the <a href="https://wordpress.org/plugins/debug-bar-shortcodes/faq/" rel="ugc">FAQ</a> for more info.</em></li>
<li>Find out all pages/posts/etc on which a shortcode is used</li>
</ul>
<p>This plugin is compatible with the <a href="https://wordpress.org/plugins/lrh-shortcode-list/" rel="ugc">LRH-Shortcode list</a> and the <a href="https://wordpress.org/plugins/shortcode-ui/" rel="ugc">Shortcake/Shortcode UI</a> plugins. Additional information about a shortcode provided to these plugins will be taken into account and made available through this plugin too.</p>
<h4>Why is it useful to have insight into the shortcodes ?</h4>
<p>There are a number of typical uses I can think of:</p>
<ul>
<li>
<p>If you are a <strong><em>blog author</em></strong>:</p>
<ul>
<li>to know which shortcodes you can use in your posts/pages.</li>
<li>if you switch plugins or remove a plugin, to know in which posts/pages you need to remove/replace old shortcodes</li>
</ul>
</li>
<li>
<p>If you are a <strong><em>web designer / web master</em></strong>:</p>
<ul>
<li>if you switch plugins or remove a plugin, to know in which posts/pages you need to remove/replace old shortcodes.</li>
<li>to know which shortcodes you can use in theme files.</li>
<li>to avoid name conflicts for website specific shortcodes.</li>
</ul>
</li>
<li>
<p>If you are a <strong><em>developer</em></strong>:</p>
<ul>
<li>to avoid name conflicts with shortcodes registered by other plugins/themes.</li>
<li>to check whether your shortcode registers properly and whether the conditionals are applied correctly.</li>
</ul>
</li>
</ul>
<h4>Important</h4>
<p>This plugin requires the <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a> plugin to be installed and activated.</p>
<h4>Credits</h4>
<ul>
<li>The additional information functionality is inspired by <a href="https://wordpress.org/plugins/lrh-shortcode-list/" rel="ugc">LRH-Shortcode list</a> and <a href="https://wordpress.org/plugins/shortcode-reference/" rel="ugc">Shortcode reference</a>.</li>
<li>The finding of shortcode uses throughout the site is inspired by <a href="https://wordpress.org/plugins/tr-all-shortcodes/" rel="ugc">TR All Shortcodes</a></li>
</ul>
<p>If you like this plugin, please <a href="https://wordpress.org/support/view/plugin-reviews/debug-bar-shortcodes" rel="ugc">rate and/or review</a> it. If you have ideas on how to make the plugin even better or if you have found any bugs, please report these in the <a href="https://wordpress.org/support/plugin/debug-bar-shortcodes" rel="ugc">Support Forum</a> or in the <a href="https://github.com/jrfnl/Debug-Bar-Shortcodes/issues" rel="nofollow ugc">GitHub repository</a>.</p>


Debug Bar Shortcodes

Works great

Debug Bar Shortcodes adds a new panel to the Debug Bar that displays the registered shortcodes for the current request.

Debug-Bar-Extender vs Debug Bar Shortcodes