Clear JSON after taxonomy changes
Taxonomy terms can affect archive headings, groups, navigation, labels, hierarchy, filtering, and display order. Enable term invalidation when any of those values appear in progressive archive JSON.
Turn on term invalidation
- Go to Settings → POM Cache → General.
- Locate Progressive JSON runtime.
- Set Progressive JSON cache to Enabled;
- Set Purge JSON on term changes to Enabled;
- Save the settings.
This JSON switch does not enable Purge HTML on term changes. The HTML page and the JSON batches are different stores.
Term operations covered
The JSON tree is cleared after WordPress reports that a term was:
- created;
- edited;
- deleted.
POM Cache also clears when the term-order metadata used by compatible POM archive interfaces changes. Reordering a taxonomy can change the sequence of archive groups even though no term label changed.
Other arbitrary term metadata does not automatically trigger JSON deletion through this specific metadata path. If a custom field changes visible progressive output, its integration should clear JSON or you should perform a manual clear.
What about assigning a term to a post?
An assignment changes which posts belong to a term, so POM Cache handles it with Purge JSON on post changes.
Use this distinction:
| Editorial action | Required JSON switch |
|---|---|
| Rename or delete a category | Purge JSON on term changes |
| Change term hierarchy or supported term order | Purge JSON on term changes |
| Move a product from one category to another | Purge JSON on post changes |
| Edit the product title shown in the category | Purge JSON on post changes |
Enable both on most taxonomy-driven catalogs.
Why the complete current-site cache is cleared
A term change may alter:
- the presence or title of a split-by-term section;
- several archive pages after reordering;
- navigation links embedded in multiple batches;
- contextual templates;
- localized variants of the same grouping.
POM Cache therefore removes the entire progressive JSON tree for the current site rather than one term folder. The first later request to each route regenerates it.
Test rename, order, and assignment separately
- Generate JSON for a taxonomy-driven progressive archive;
- Rename a visible term;
- Confirm Progressive JSON Cache Contents returns to zero;
- Reload the archive and verify the new label;
- Reorder terms through the compatible interface and repeat;
- Change a post's term assignment;
- Verify the assignment clears JSON only when the post-change switch is enabled.
This test prevents a common misconfiguration where the term switch is enabled but the post switch is expected to cover assignments.
CDN considerations
Term changes often affect several viewer paths: the archive HTML, multiple JSON batches, and perhaps a taxonomy landing page. Clear the correct POM Cache stores first, verify the corrected origin, and then invalidate the smallest adequate CDN path set.
Avoid invalidating only the visible taxonomy page if its browser later requests stale /pom-json/ batches from the edge.
For a full comparison of HTML and JSON actions, see Clear HTML and JSON caches independently.