Replace a stale cached translation
First prove the stored translation is current. Open it in the Translation Manager and compare it with a logged-out response.
Locate the stale layer
- Request the target URL in a private session.
- Bypass the CDN or full-page cache using its supported method.
- Compare the raw response with the browser display.
- Check object cache, page cache, fragment cache, menu cache, and browser cache in that order.
- Verify the base-language route has not been cached under the target URL.
POM Translate invalidates its own locale-sensitive caches when supported strings, translations, slugs, and custom URLs change. It cannot guarantee that every theme fragment, reverse proxy, or CDN reacts to those events.
Correct cache variation
External cache keys must distinguish at least site, route or object, and locale. Cookies alone are not a safe multilingual page-cache key when public content has stable language URLs.
Purge the smallest affected entry. For a translated slug change, purge the previous and current paths as well as navigation that links to them. For menu text, purge every page that embeds the cached menu.
Do not repeatedly resave the translation to force invalidation. Fix the cache rule or connect integration-owned caches to pom_translate_translation_changed, pom_translate_slug_changed, or the matching public lifecycle action.
The problem is resolved when independent logged-out requests for two locales return different current content without manual cache bypass.