Clear JSON after translation changes

Progressive archive files can contain localized item markup, labels, messages, slugs, and next-request URLs. POM Cache can clear those files when POM Translate reports a supported translation change.

Enable the integration

1. Open Settings → POM Cache → General.
2. Find Progressive JSON runtime.
3. Confirm Progressive JSON cache is Enabled.
4. Set Purge JSON on translation changes to Enabled.
5. Save.

This control is useful only when the translation workflow emits the supported POM Translate change notifications. It is independent of the post- and term-change settings.

Translation changes that trigger a purge

POM Cache listens for changes to:

• a registered source string;
• a stored translation;
• a translated public slug.

A matching notification clears the complete current-site JSON cache, including all locale prefixes. This avoids leaving one language with a stale label or a next URL that contains an old slug.

The purge is intentionally broader than the changed string. The same translation may appear in many archive contexts and batches.

What is not implied

Enabling this switch does not:

• translate content;
• generate missing translations;
• clear the static HTML cache;
• invalidate a CDN;
• detect direct database edits that bypass the supported translation workflow;
• delete JSON on another multisite site.

If translated text also appears in cached HTML shells, enable the appropriate HTML invalidation or clear HTML manually after the translation batch.

Verify one locale change

1. Generate a progressive batch for at least two languages.
2. Confirm the JSON count is greater than zero.
3. Change a visible archive translation through POM Translate.
4. Confirm the current site's JSON count returns to zero.
5. Request the translated archive again.
6. Inspect the regenerated JSON and visible cards;
7. Request the default-language archive and verify it regenerates independently;
8. Verify any CDN copy of the translated route is current.

Test a slug translation separately because its effect includes routing:

1. Record the old progressive URL;
2. Change the translated slug through the supported interface;
3. Confirm JSON clears;
4. Load the archive from its current translated public page;
5. Confirm the new JSON URL succeeds and contains current next links;
6. Remove or invalidate old CDN paths according to the site's redirect policy.

Machine translation batches

A bulk translation can emit many change events. The safe end state is one completely cleared JSON tree followed by normal regeneration.

Plan the operation so editors know whether visitors may see old batches during the run. At completion:

1. Select Delete Progressive JSON Cache even if automatic deletion already ran;
2. Clear HTML if translated strings appear there;
3. Regenerate representative routes in every public language;
4. Verify URLs, labels, empty-state messages, and pagination;
5. Invalidate related CDN viewer paths.

This final clear removes any files created midway through the translation batch with a mixture of old and new strings.

Diagnose a translation that remains stale

First determine where the old text is coming from:

• initial page shell: inspect and clear HTML;
• later progressive batch at origin: inspect and clear JSON;
• correct origin but old public response: inspect CDN freshness;
• new JSON generated with old wording: verify the source translation and archive rendering rather than the cache.

Do not assume every stale translated screen is a JSON problem. Use Clear HTML and JSON caches independently to isolate the layer.