Update translations after changing a term

Saving an enabled term makes POM Translate compare its current name and description with the stored source rows. Unchanged rows keep their translations. A changed source row is replaced and its attached translations must be resolved again; when exactly identical source text already exists elsewhere, POM Translate may reuse that matching translation.

Review a wording change

1. Record the current target-language archive and translation.
2. Edit the source term name or description in WordPress.
3. Save the term.
4. Open Translations → Translate contents.
5. Select the affected locale and filter to the term.
6. Review the updated source text and its status.
7. Write or approve the new translation.
8. Select Save translations.
9. Inspect every frontend location that displays the term.

Do not assume a small punctuation edit preserves the old target wording. The source record includes its original text and protected structure.

Understand slug behavior

Saving a new source slug updates the base-locale slug record. Existing localized slugs are not overwritten because POM Translate initializes them only when a locale has no stored value.

After a source slug change:

• confirm each additional-language slug remains appropriate;
• check the source archive and localized archives;
• update menus or external references where necessary;
• create redirects for withdrawn public routes outside the slug editor.

Moving a hierarchical term

Changing a category or another hierarchical term's parent changes the archive ancestry without changing its translated name or own localized slug. Verify the new parent chain in every language and complete any missing ancestor slugs.

Removing source text

Clearing a description removes that field from the term's current translation set on save. The name remains. Deleting the whole WordPress term is a separate destructive operation and should not be used merely to reset translations.