• Hello,
    I am using your plugin to try and localize some of my installed plugins but I get the below errors on every plugin I have tried so far (about 5). What does this error actually mean? It says there is a coding error in the plugin, but every plugin can’t be faulty, right… or? I am using a child theme of Twenty Fourteen and WordPress 3.9.1.

    Error: The actual loaded translation content does not match the textdomain: (the textdomain name)
    Expect, that any text you translate will not occure as long as the textdomain is mismatching!
    This is a coding issue at the source files you try to translate, please contact the original Author and explain this mismatch.

    Warning: The actual loaded translation content contains mixed textdomains and is not pure translateable within one textdomain.
    It seems, that there is code contained extracted out of other plugins, themes or widgets and used by copy & paste inside some source files.
    The affected unknown textdomains are:

    https://wordpress.org/plugins/codestyling-localization/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hello,

    Did you get an answer to your question? How to fix it please? I am facing the same issue.

    Greg

    Thread Starter mepmepmep

    (@mepmepmep)

    Hi,

    No, I don’t have a solution for this problem but at least I think I understand why it occurs. Many plugin authors like to reference common words from the standard WordPress language files, like e.g. ‘post’, ‘page’ etc instead of duplicating these words in their own plugin language files. This is what causes two mixed textdomains. And from what I can understand the author of this plugin feels that this is a malpractice from plugin authors and does not want to support it (correct me if I’m wrong). I’m currently using an offline editor, PoEdit, to create the language files and then I upload them manually.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Textdomain error when trying to localize plugins’ is closed to new replies.