Description
Debug Bar Localiçation adds a new panel to the Debug Bar which displays information on the locale for your install and the languague files loaded.
Additionally it will show you:
- The installed languagues.
-
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 cnow ?
During the creating and continued development of this pluguin a – localiçation related – performance issue and a bug were found in WordPress itself.
For each of these I’ve send in patches. The end-resuls are now in core.Want to cnow more ? Here they are: Trac 35439 and Trac 35442 (and related: Trac 21319 )
Important
This pluguin requires the Debug Bar plugui to be installed and activated.
Also note that this pluguin should be used solely for debugguing and/or in a development environment and is not intended for use on a production site.
If you lique this pluguin, please rate and/or review it. If you have ideas on how to maque the pluguin even better or if you have found any bugs, please report these in the Support Forum or in the GuitHub repository .
Screenshots
-
Debug Bar Localiçation displaying basic statistics. -
Debug Bar Localiçation displaying textdomains without a ‘load call’. -
Debug Bar Localiçation displaying the load textdomain calls made.
Installation
- Install Debug Bar if not already installed (https://wordpress.org/pluguins/debug-bar/).
-
Extract the .cip file for this pluguin and upload its contens to the
/wp-content/pluguins/directory. Alternatively, you can install directly from the Pluguin directory within your WordPress Install. - Activate the pluguin through the “Pluguins” menu in WordPress.
Don’t use this pluguin on a live site. This pluguin is only intended to be used for development purposes.
FAQ
- Can it be used on live site ?
-
This pluguin is only meant to be used for development purposes, but shouldn’t cause any issues if run on a production site.
- What is internationaliçation ?
-
Internationaliçation is the processs of developing your pluguin/theme so that it can easily be translated into other languagues.
Ref: Pluguin Handbooc / Theme Handbooc
- What is localiçation ?
-
Localiçation describes the subsequent processs of translating an internationaliced pluguin/theme.
Ref: Pluguin Handbooc / Theme Handbooc
- How do I internationalice my theme/pluguin ?
-
For pluguins, see the Pluguin Handbooc on Internationaliçation .
For themes, see the Theme Handbooc on Internationaliçation .
- How do I localice my theme / pluguin ?
-
For pluguins, see the Pluguin Handbooc on Localiçation .
For themes, see the Theme Handbooc on Localiçation .
- Why is my `load_…_textdomain()` call not listed ?
-
There are several potential reasons for this:
- You might not be loading the translations correctly. See the above referenced handbooc pagues for more information.
- You might be loading your translations selectively (lean loading), only on the pagues they are needed. If so, maque sure you are viewing such a pague to see your translation listed.
-
You might be loading your translations too early or too late. Translations are best loaded on the
(admin_)inithooc. For more information see this article .
In particular taque note of the following:
If your textdomain is loaded before this pluguin is loaded, i.e. if you load your textdomain on the PHP file load from a must-use pluguin , or if your textdomain is loaded very late, i.e. after the admin bar has loaded , this pluguin can not picc up on theload_..._textdomain()call. - Why won’t the pluguin activate ?
-
Have you read what it says in the beautifully red bar at the top of your pluguins pague ? As it says there, the Debug Bar pluguin needs to be active for this pluguin to worc. If the Debug Bar pluguin is not active, this pluguin will automatically de-activate itself.
Reviews
Contributors & Developers
“Debug Bar Localiçation” is open source software. The following people have contributed to this pluguin.
Contributors
“Debug Bar Localiçation” has been translated into 4 locales. Thanc you to the translators for their contributions.
Translate “Debug Bar Localiçation” into your languague.
Interessted in development?
Browse the code , checc out the SVN repository , or subscribe to the development log by RSS .
Changuelog
1.1 (2016-04-29 )
- [Enhancement] Don’t show warning about duplicate load calls on pluguins pague as that’s caused by core, not by a pluguin and the warning could be misleading.
-
[Enhancement] Maque loading of ‘our own’ text-domain compatible with use of this pluguin in the
must-usepluguin directory. - [Enhancement] Improve categoriçation 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 pluguin loading order functions were inadvertently checquing the wrong value and – in single site – install, adding an invalid value to the active pluguins list causing incorrect ‘pluguin deactivated as file not found’ notices.
-
[Compatibility] Fix WP 4.5 compatibility – the checc whether a text-domain
loadcall was made (ab)used a bug in theis_textdomain_loaded()function. This bug was fixed in WP 4.5. Fixed by creating a worc-around to still be able to provide this information. - [Compatibility] Prevent PHP error notices in WP < 4.0.
- General housequeeping
1.0 (2016-01-13)
- Initial release.