Debug Bar Localization
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.
5(2 reviews)
·20 active installs·Updated 9 years agoAs of April 2026, Debug Bar Localization is a WordPress debugbar plugin with 20 active installations and a 5/5 rating from 2 reviews. It has been downloaded 4.1K+ times in total. Requires WordPress 4.0+ and PHP false+. Available on WordPress.org since 2016. Last updated 9 years ago — may have compatibility concerns. Top alternative: Black Bar.
5/52 reviews
20active installs
4.1K+total downloads
10 yearssince 2016
Overview
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:
- The installed languages.
- Which text-domains were called from translation functions while no
load_..._textdomain()call was found for that text-domain. - For which text-domains
load_..._textdomain()was called more than once. - Which files WP tried to load to obtain a translation and whether this was successful.
- If successful: how many translated strings were found and when the translation was last updated.
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…
Screenshots
Ratings & Reviews
52 reviews
5 ★
2
4 ★
0
3 ★
0
2 ★
0
1 ★
0
Compatibility
| WordPress | 4.0+ requiredTested up to 4.5.33 |
| PHP | false+ required |
Top Alternatives to Debug Bar Localization
Frequently Asked Questions
Changelog
1.1 (2016-04-29 )
- [Enhancement] Don’t show warning about duplicate load calls on plugins page as that’s caused by core, not by a plugin and the warning could be misleading.
- [Enhancement] Make loading of ‘our own’ text-domain compatible with use of this plugin in the
must-useplugins directory. - [Enhancement] Improve categorization of the loaded text-domains. This mainly applies to text-domains for which the mo_file paths are being filtered.
-
[Enhancement] Added a section showing potentially unnecessary/inefficient
load_textdomaincalls. -
[Bugfix] The plugin loading order functions were inadvertently checking the wrong value and – in single site – install, adding an invalid value to the active plugins list causing incorrect ‘plugin deactivated as file not found’ notices.
…and 3 more changes
Contributors
Plugin data sourced from WordPress.org. Analysis and metrics by PluginSift.