Juliette Reinders Folmer

Debug Bar Localization adds a new panel to the Debug Bar which displays information on the locale for your install and the language files loaded.
Additionally it will show you:
<ul>
<li>The installed languages.</li>
<li>Which text-domains were called from translation functions while no <code>load_..._textdomain()</code> call was found for that text-domain.</li>
<li>For which text-domains <code>load_..._textdomain()</code> was called more than once.</li>
<li>Which files WP tried to load to obtain a translation and whether this was successful.</li>
<li>If successful: how many translated strings were found and when the translation was last updated.</li>
</ul>
<blockquote>
Did you know ?
During the creating and continued development of this plugin a – localization related – performance issue and a bug were found in WordPress itself. 
 For each of these I’ve send in patches. The end-results are now in core.
Want to know more ? Here they are: <a href="https://core.trac.wordpress.org/ticket/35439" rel="nofollow ugc">Trac 35439</a> and <a href="https://core.trac.wordpress.org/ticket/35442" rel="nofollow ugc">Trac 35442</a> (and related: <a href="https://core.trac.wordpress.org/ticket/21319" rel="nofollow ugc">Trac 21319</a> )
</blockquote>
<h4>Important</h4>
This plugin requires the <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a> plugin to be installed and activated.
Also note that this plugin should be used solely for debugging and/or in a development environment and is not intended for use on a production site.
If you like this plugin, please <a href="https://wordpress.org/support/view/plugin-reviews/debug-bar-localization" 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-localization" rel="ugc">Support Forum</a> or in the <a href="https://github.com/jrfnl/debug-bar-localization/issues" rel="nofollow ugc">GitHub repository</a>.

Debug Bar Localization

Just help me to debug a website that had a problem !!
Thanks !!! :)



Very nice

When you've messed up your localize_script or plugin and you have a hard time tracking it, it helps you in no time!

Great job!

Works like a charm

Debug Bar Localization adds a new panel to the Debug Bar which displays information on the locale for your install and the language files loaded.

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.
Additionally it will show you:
<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. 
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.</li>
<li>Find out all pages/posts/etc on which a shortcode is used</li>
</ul>
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.
<h4>Why is it useful to have insight into the shortcodes ?</h4>
There are a number of typical uses I can think of:
<ul>
<li>
If you are a blog author:
<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>
If you are a web designer / web master:
<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>
If you are a developer:
<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>
This plugin requires the <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a> plugin to be installed and activated.
<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>
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>.

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 Localization vs Debug Bar Shortcodes