Error: The actual loaded translation content does not match the textdomain: bp-ass

[JonathanReeve]

I've been getting errors while trying to add custom translations for buddypress-group-email-subscription. My translation doesn't seem to take effect in /wp-content/languages/buddypress-group-email-subscription, or in /wp-content/languages/bp-ass. (I describe more of the details of my attempts on this Stack Exchange question.) When I use the plugin Codestyling Localization in conjunction with Codestyling Localization Preserver (not my preferred method of translating, but a common one, and has built-in error checking), it complains "Error: The actual loaded translation content does not match the textdomain: bp-ass" as in the screenshot below:

Could this have something to do with the discrepancy between the namespaces buddypress-group-email-subscription and bp-ass? It's also possible I'm doing something wrong here in trying to add this translations file.

[r-a-y]

Could this have something to do with the discrepancy between the namespaces buddypress-group-email-subscription and bp-ass?

A little bit. WordPress recently started offering plugin translations with the language domain needing to be the same as the plugin slug. I'm guessing Codestyling Localization follows this convention.

Until we switch up our domains, you do not need a language file to change one line of text.

Try the gettext filter: http://codex.wordpress.org/Plugin_API/Filter_Reference/gettext

Make sure you only run it on the page where the string exists and try to remove your filter after your string is translated to avoid your function call being run on every output string.

[JonathanReeve]

Thanks, @r-a-y! That sounds way easier than the way I'd imagined it. I'll give that a try.