Restore a missing registered string
Registered strings appear only after code calls pom_translate_register_string() with a non-empty stable name.
Check registration
- Confirm the integration is active.
- Find where registration runs and verify it executes after POM Translate loads.
- Confirm the name is stable and the source value is not empty.
- Reload the translation administration screen after registration.
- Search for the exact current source wording.
Registration should occur during bounded initialization, activation, settings save, or object save. If it happens only inside a frontend condition, the string may never exist when an administrator opens the Translation Manager.
Check source changes
Calling the helper again with the same name and new source updates the registered entry. Searching for the old wording can therefore make the string appear missing. Review target translations after any semantic source change.
pom_translate_translate_registered_string() deliberately refuses to auto-register unknown input. pom_translate_translate_string() can ensure a source entry exists, but rendering should not be used as an uncontrolled registration strategy.
Do not register gettext catalogs, customer data, order notes, or rapidly changing values as standalone site strings. If the missing text belongs to a post, term, menu, or software catalog, use that surface's workflow instead.