David Perez

closemarketing

Pedro Mendonça

Manu Relaño

It gives you more information about all domains and translated mo files loaded in the actual installation, so you can debug what’s the problem with a plugin, theme, etc.
Only shows the debug info if you’re logged in in the footer.
You’ll have a info of all plugins loaded, textdomain used, if file is found and then the path where is the function of theme or plugin loaded. You can see the screenshots.
<h3>Developers</h3>
<a href="https://github.com/closemarketing/debug-mo-translations" rel="nofollow ugc">Official Repository GitHub</a>
<h3>Links</h3>
<ul>
<li><a href="https://close.marketing/" rel="nofollow ugc">Closemarketing</a></li>
<li><a href="https://profiles.wordpress.org/closemarketing/#content-plugins" rel="nofollow ugc">Closemarketing plugins</a></li>
<li><a href="https://twitter.com/pedro_gaspar" rel="nofollow ugc">Pedro Mendonça</a></li>
</ul>

Debug MO Translations

A very useful tool to discover where WordPress expects plugin and theme language files to be located.



Great for troubleshooting language file locations

very useful as it prints at the bottom all the possible paths that WordPress goes through.

works with 4.8

This plugin is a must-use to debug translation issues for WP core, themes and plugins.

Thanks! :-)

Quick solver for translation issues


Thanks, your plugin is very useful and saved my time!


Very useful plugin

Debugs all translated files that are loaded and not in WordPress.

Alex Kirk

This plugin ensures that any text coming from a translation file (<code>.po</code> or <code>.mo</code>) is run through an escaping function before it is output to the user.
Escaping refers to the modification of the text so that special control characters do not have an effect (for example <code><</code> in HTML).
Example: If an original text does not contain HTML, then a translated text should not be allowed to contain HTML either. Thus, an HTML link introduced by a translator should have no effect because this was not intended by the developer.
This plugin is in the proof-of-concept stage, it was created to test if the escaping of translated text can be handled in a general way, whether it severely affects the performance of a site, and if it breaks things.
For text without HTML, the text is sent through <code>esc_html()</code>, for text containing HTML tags, it is sent through <code>wp_kses()</code> which is provided with a list of allowed HTML tags and attributes, derived from the original string.
Thus this plugin tries to show a generic way of how to make sure that translated text is escaped. This is something that can eventually be ported to core.

Secure Gettext

Escapes translated text before it gets output. This adds an extra security layer around translated text.

Debug MO Translations vs Secure Gettext