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.

Per Søderlind

Juliette Reinders Folmer

<p>We all know that when we’re add a script or style to WordPress, we should use <code>wp_enqueue_script( $handle, $src, $deps, $ver, $in_footer )</code> and <code>wp_enqueue_style( $handle, $src, $deps, $ver, $media )</code> as in:</p>
<pre><code>function themeslug_enqueue_style() {
    wp_enqueue_style( 'core', 'style.css', array('twentytwelve-style') );
}

function themeslug_enqueue_script() {
    wp_enqueue_script( 'my-js', 'filename.js', array('jquery') );
}

add_action( 'wp_enqueue_scripts', 'themeslug_enqueue_style' );
add_action( 'wp_enqueue_scripts', 'themeslug_enqueue_script' )
</code></pre>
<p>$deps (dependencies), the handle name and an optional parameter, lets you control when/where your script or style should be added. If $deps is <code>array('jquery')</code>, your script will be loaded after jquery is loaded.</p>
<p>The problem is, which one exists and in which order are they loaded ?</p>
<p>Debug Bar List Script & Style Dependencies, an add-on to <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a>, will list the dependencies.</p>
<h4>Use</h4>
<p>To view the loaded scripts and styles</p>
<ul>
<li>Front-end: Go to the front-end, and on the admin bar choose Debug and view Script & Style Dependencies</li>
<li>Back-end: Go to the back-end, on the admin bar choose Debug and view Script & Style Dependencies</li>
</ul>
<p>Note, the front-end and back-end loads different scripts and styles. Also, different pages on the front-end and back-end can load different scripts and styles.</p>


Debug Bar List Script & Style Dependencies

Style very useful (even if it has not been updated since two years) ! Thanks !



useful !

Debug Bar List Script & Style Dependencies is an add-on to WordPress Debug Bar

Debug-Bar-Extender vs Debug Bar List Script & Style Dependencies