10+
April 30, 2016
January 13, 2016
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:
load_..._textdomain() call was found for that text-domain.load_..._textdomain() was called more than once.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: Trac 35439 and Trac 35442 (and related: Trac 21319 )
This plugin requires the Debug Bar 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 rate and/or review 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 Support Forum or in the GitHub repository.
/wp-content/plugins/ directory. Alternatively, you can install directly from the Plugin directory within your WordPress Install.Don’t use this plugin on a live site. This plugin is only intended to be used for development purposes.
This plugin is only meant to be used for development purposes, but shouldn’t cause any issues if run on a production site.
Internationalization is the process of developing your plugin/theme so that it can easily be translated into other languages.
Ref: Plugin Handbook / Theme Handbook
Localization describes the subsequent process of translating an internationalized plugin/theme.
Ref: Plugin Handbook / Theme Handbook
For plugins, see the Plugin Handbook on Internationalization.
For themes, see the Theme Handbook on Internationalization.
For plugins, see the Plugin Handbook on Localization.
For themes, see the Theme Handbook on Localization.
There are several potential reasons for this:
(admin_)init hook. For more information see this article.In particular take note of the following:
If your textdomain is loaded before this plugin is loaded, i.e. if you load your textdomain on the PHP file load from a must-use plugin, or if your textdomain is loaded very late, i.e. after the admin bar has loaded, this plugin can not pick up on the load_..._textdomain() call.
Have you read what it says in the beautifully red bar at the top of your plugins page ? As it says there, the Debug Bar plugin needs to be active for this plugin to work. If the Debug Bar plugin is not active, this plugin will automatically de-activate itself.
must-use plugins directory.[Enhancement] Added a section showing potentially unnecessary/inefficient load_textdomain calls.
[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.
[Compatibility] Fix WP 4.5 compatibility – the check whether a text-domain load call was made (ab)used a bug in the is_textdomain_loaded() function. This bug was fixed in WP 4.5. Fixed by creating a work-around to still be able to provide this information.