{"id":2255,"date":"2026-06-28T13:34:19","date_gmt":"2026-06-28T10:34:19","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=2255"},"modified":"2026-08-02T12:10:42","modified_gmt":"2026-08-02T12:10:42","slug":"wordpress-plugin-translations-not-showing-causes-and-fixes","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/wordpress-plugin-translations-not-showing-causes-and-fixes\/","title":{"rendered":"WordPress Plugin Translations Not Showing: Causes and Fixes"},"content":{"rendered":"

A plugin appears fully translated in its PO file, yet one WordPress site still shows an English label while another site on the same server shows German. The files exist, but the failing request uses a different locale and loads another text domain before the custom catalog is available.<\/p>\n

Start with one untranslated message and follow the complete runtime lookup: source text, context, domain, locale, catalog filename, directory, and load time. That evidence shows whether the problem is a missing translation, a stale build, a naming mismatch, or a separate JavaScript catalog.<\/p>\n

\nTable of contents<\/strong><\/p>\n
    \n
  1. What it means<\/a><\/li>\n
  2. A realistic WordPress example<\/a><\/li>\n
  3. Why it matters and when to use it<\/a><\/li>\n
  4. A straightforward route for beginners<\/a><\/li>\n
  5. The advanced route<\/a><\/li>\n
  6. Risks, common mistakes, backup, and rollback<\/a><\/li>\n
  7. How AIOWS helps: AIOWS Language Compiler<\/a><\/li>\n
  8. Related AIOWS articles<\/a><\/li>\n
  9. Conclusion and recommended route<\/a><\/li>\n
  10. Official sources<\/a><\/li>\n<\/ol>\n<\/div>\n

    What it means<\/h2>\n

    A plugin translation appears only when WordPress requests a message with the same source string, context, text domain, locale, and plural form found in a loaded catalog. The compiled file must also use the expected name and location.<\/p>\n

    PHP gettext strings normally come from MO files. JavaScript translations may require domain-specific JSON catalogs registered for the relevant script. A translated entry in a PO editor therefore proves neither that the runtime artifact was rebuilt nor that WordPress loaded it.<\/p>\n

    A realistic WordPress example<\/h2>\n

    A plugin label is translated in the German PO file and appears correctly on the public site. The same label remains English in the administrator area for one user. That account has a different user locale, and the plugin package does not contain the matching catalog for that locale.<\/p>\n

    Instead of recompiling the existing German file, the team captures the exact source message and request locale, confirms the plugin text domain, and checks the candidate language directories. A separate JavaScript label is traced to its JSON catalog rather than treated as an MO problem.<\/p>\n

    Why it matters and when to use it<\/h2>\n

    Use this method when a plugin translation is missing, stale, or inconsistent between the front end, administrator screens, users, or sites. A single-message trace prevents broad file replacements that happen to change one view while leaving the real mismatch unresolved.<\/p>\n

    Rebuild a catalog only when its source and runtime artifact demonstrably disagree. If the plugin changed the original source string, update the translation from an authoritative template or translator decision; do not invent a close-looking entry and expect gettext to match it.<\/p>\n

    A straightforward route for beginners<\/h2>\n
      \n
    1. Copy the exact untranslated text and note the page, screen, plugin version, current user, and active locale.<\/li>\n
    2. Confirm the source string, context, plural form, and text domain in the current plugin code.<\/li>\n
    3. Check whether the message is rendered by PHP or JavaScript.<\/li>\n
    4. List the standard plugin, global language, custom, and vendor-managed paths that can supply the catalog.<\/li>\n
    5. Compare filenames, timestamps, hashes, and update ownership before changing a file.<\/li>\n
    6. After the repair, test the exact message and an unaffected translation in a fresh front-end or administrator request.<\/li>\n<\/ol>\n

      The advanced route<\/h2>\n

      Build a lookup trace for one missing PHP message and one missing JavaScript message. Record the source text, context, domain, locale, generated filename, candidate directories, selected catalog, and the point at which the plugin registers translations.<\/p>\n