Clear caches from the tools screen

The POM Cache settings screen provides separate, observable controls for HTML and progressive JSON. Use it when you want to preserve one warm store while deleting the other.

Open the current-site tools

On a single site:

1. Open Settings → POM Cache;
2. Select General.

On multisite, an authorized network administrator can use Network Admin → Settings → POM Cache → General. Always verify which site's current context the screen represents before clearing.

The page contains two maintenance sections:

Cache tools

Cache Contents shows the count and combined size of current-site static HTML pages.

Delete Cache removes that HTML tree only. A successful action reports:

Cache deleted for the current site.

Progressive JSON tools

Progressive JSON Cache Contents shows the count and combined size of non-empty current-site .json files.

Delete Progressive JSON Cache removes that JSON tree only. A successful action reports:

Progressive JSON cache deleted for the current site.

HTML-only procedure

Use this when the initial document is stale but progressive batches are correct:

1. Note Cache Contents;
2. Select Delete Cache under Cache tools;
3. Wait for the inline result;
4. Confirm the HTML count returns to zero;
5. Request the affected page at the origin;
6. Verify current content and a new HTML cache entry;
7. Confirm Progressive JSON Cache Contents was not reduced by the action.

JSON-only procedure

Use this when later archive results are stale but the page shell is correct:

1. Note Progressive JSON Cache Contents;
2. Select Delete Progressive JSON Cache;
3. Confirm the JSON count returns to zero;
4. Trigger one archive batch at the origin;
5. Verify current JSON and regeneration;
6. Confirm Cache Contents remains unchanged.

Why the status changes immediately

After a successful tool action, POM Cache discards the previous summary and scans the relevant current-site tree again. The displayed count and size therefore reflect the post-delete state.

The status is storage information, not traffic information. It does not show how many requests hit the cache or whether a CDN has a copy.

Permission and skipped deletion

The page and AJAX actions require permission to manage POM Cache settings. The deletion request also uses WordPress request verification.

A supported extension can deliberately suppress a site clear. In that case, the interface says deletion was skipped by configuration and retains a refreshed status summary. Resolve the authorized configuration; do not work around it with a broad filesystem deletion.

Choose the toolbar only when both are stale

The administration-bar Delete Cache action removes both HTML and JSON in one request. It is convenient, but unnecessarily broad when just one layer is wrong.

Use this diagnostic:

• stale before any progressive request: inspect HTML;
• correct shell, stale newly loaded cards: inspect JSON;
• both stale: clear both;
• correct origin, stale public visitor response: inspect browser/CDN.

Continue with Clear HTML and JSON caches independently for examples of each symptom.