Tour the POM Cache interface
POM Cache keeps its administration deliberately small. The interface separates runtime controls, maintenance tools, server configuration, and licensing so that a cache purge cannot be confused with a deployment change.
Open the settings
On a single-site installation, open:
Settings → POM Cache
On multisite, the normal network entry is:
Network Admin → Settings → POM Cache
A super administrator working with site-specific settings can also open Settings → POM Cache in that site’s administration. Current-site values take priority; an unset value can fall back to the main site’s effective setting.
Only administrators can open the settings. Network-level changes on multisite require the corresponding network permission.
General: Runtime
The Runtime section controls static HTML:
| Setting | Effect |
|---|---|
| Caching | Enables or disables HTML generation and PHP static delivery for the current site. |
| Purge HTML on post changes | Chooses whether relevant public post changes delete all current-site HTML, only that post's localized single files, or nothing. |
| Purge HTML on term changes | Deletes current-site HTML when taxonomy terms change. |
The two purge settings are disabled by default. The post-change setting also offers Edited post single only, which preserves unrelated HTML but does not refresh listings, navigation, or other pages that include post data. Choose the scope according to the site’s editorial workflow; leaving a purge disabled requires a deliberate manual purge after relevant changes.
Disabling Caching stops POM Cache’s PHP generation and delivery path. Existing files can still be reachable through previously installed Apache rules until they are deleted or the rules no longer match, so disabling the setting is not a complete emergency rollback by itself.
General: Cache tools
Cache Contents calculates the number and total size of current-site index.html files whenever the status is rendered.
Delete Cache removes the current site’s HTML cache. It does not remove progressive JSON or invalidate a CDN.
General: Configuration
Fix Configuration writes the current site’s POM Framework settings files using the effective fallback values.
Fix Configuration is useful when a site needs explicit local settings files. It does not repair wp-config.php, .htaccess, or advanced-cache.php.
General: Progressive JSON runtime
This section controls a cache that is independent from HTML:
| Setting | Purpose |
|---|---|
| Progressive JSON cache | Master switch for compatible progressive archive JSON. |
| PHP early static serving | Lets the drop-in serve an existing JSON file before WordPress finishes loading. |
| WordPress read fallback | Lets the compatible theme router read an existing file when an earlier layer did not serve it. |
| JSON writes | Stores an eligible dynamic JSON response after it is generated. |
| Maximum JSON file size | Rejects a file larger than the configured byte limit. |
| JSON Cache-Control header | Sets the header used by PHP early JSON delivery. |
| Purge JSON on post changes | Invalidates JSON after relevant post changes. |
| Purge JSON on term changes | Invalidates JSON after relevant taxonomy changes. |
| Purge JSON on translation changes | Invalidates JSON after supported translation changes. |
The master switch defaults to disabled. The serving and write controls do not make sense as a public workflow until a compatible progressive archive is configured.
General: Progressive JSON tools
Progressive JSON Cache Contents reports the file count and total size for the current site’s JSON tree.
Delete Progressive JSON Cache removes that JSON without deleting HTML. Use it when archive data changed but the surrounding static pages remain correct.
Advanced: Storage
Cache Location is the base directory. The default is wp-content/cache/; HTML is stored inside its pom-cache subdirectory.
Changing this path is a deployment decision. PHP, Apache, the rewrite rules, and every origin node must agree on the location. Do not change it merely to resolve a stale page.
Advanced: WordPress configuration
This read-only status checks:
- the installed Drop-in and its detected type;
- the expected and detected
POM_CACHE_HOME; - whether
WP_CACHEis enabled.
OK means the detected value matches the POM Cache expectation. Needs manual change includes the exact path or expected value to review. The interface never changes these files.
Advanced: Apache rules
Recommended .htaccess rules contains the static HTML rewrite block. Copy it manually before the standard WordPress rules after reviewing document-root, host, path, cookie, and multisite assumptions.
Recommended progressive JSON .htaccess rules is a separate optional block for direct JSON delivery. It also supplies the JSON content type, cache header, and Vary: Accept-Encoding behavior when the required Apache modules are available.
Saving ordinary settings does not install either block.
License
The License section contains the masked site or network key, validation state, plan, expiry, domain, and the Save and validate, Replace and validate, Revalidate, and Unlink actions appropriate to the current state.
It controls authorization and private updates, not whether an existing cached page can be delivered.
Admin-bar shortcut
Eligible logged-in editors and administrators see Delete Cache in the WordPress admin bar. Unlike the two separate settings-page buttons, this shortcut deletes both HTML and progressive JSON for the current site.
Use the settings page when only one layer should be purged. Use the shortcut when the complete current-site public cache must be rebuilt.
Now follow Verify your first cached page using only the HTML runtime controls.