What happens when original content changes
Saving an eligible source object makes POM Translate parse it again. Unchanged source rows retain their translations; changed or structurally replaced rows invalidate the target values attached to their previous source.
This is row-level behavior, not a blanket reset of the whole post.
Changes that can invalidate a row
POM Translate compares more than visible words. A stored row can be replaced when any of these changes:
- original extracted text;
- protected-placeholder map;
- normalized source identity;
- token position;
- block type or structural key.
Changing inline markup, moving builder components, or restructuring shortcodes can therefore create new work even when much of the wording looks familiar.
What happens during the save
For an existing changed string, POM Translate:
- recognizes that its source contract differs;
- removes translations attached to that string;
- updates the source row and structure;
- looks for translations of an exact matching source string that can be reused;
- refreshes relevant caches and downstream translation work.
If no exact match is reusable, the locale has no value for that row and frontend rendering falls back to the new source text.
Rows no longer used by the post structure are cleaned up during parsing.
Examples
| Source edit | Likely effect |
|---|---|
| Change only an unrelated paragraph | That paragraph requires attention; unchanged rows remain |
| Edit the canonical title | Title translations for the changed row are invalidated |
| Change a manual excerpt | Excerpt target values are invalidated |
| Move or rebuild a shortcode component | Structural rows may be replaced |
| Change a registered meta value | That metadata row requires translation again |
| Save without any relevant source change | Existing rows and translations remain |
Exact-match reuse can restore a target value previously translated for identical source wording, but editors should still verify its context.
Review after a source revision
- Save the published or private canonical object.
- reload its POM Translate locale summaries;
- note any reduced percentage or increased Missing count;
- open Manage translations;
- filter Pending;
- translate or approve the new rows;
- inspect the localized route;
- mark reviewed rows only after the new context passes.
Do not edit source wording and target translations simultaneously in separate tabs without refreshing. The source save can regenerate the row set behind an older translation screen.
Publication-status changes are broader
Changing the canonical object from published or private to draft, pending, or trash removes its post strings, metadata strings, and content skeleton under the default lifecycle.
That is different from editing one paragraph. Republish only after understanding that the translation workspace may need to be rebuilt.
Coordinate source editors and translators
For live multilingual content:
- stabilize source structure before translation;
- group source revisions into clear editorial batches;
- notify locale owners when a source row changes;
- check Pending after every material save;
- avoid cosmetic builder rearrangements during linguistic approval;
- retest slugs and related surfaces when meaning changes.
The old target wording is discarded deliberately so it cannot silently describe obsolete source content.
Return to Review translated content before publication for the reapproval checklist.