Repair the saved settings files

POM Cache reads a small set of generated settings files early in the request, before normal WordPress plugin loading is complete. General → Cache tools → Configuration → Fix Configuration recreates those files for the current site from its effective settings.

Use this tool when the settings files are missing, incomplete, or no longer agree with the values shown in WordPress.

What Fix Configuration changes

The action saves the current site's effective values for:

• the static HTML cache runtime;
• cache storage;
• the progressive JSON runtime.

If a setting has no explicit saved value, the tool uses its effective fallback. POM Cache then reloads the runtime settings so the current request reflects the repaired files.

A successful operation displays:

POM Cache settings files were saved. Drop-in and wp-config.php files were not modified.

That final sentence is an important boundary, not just an informational note.

What it deliberately does not change

Fix Configuration does not:

• copy or replace wp-content/advanced-cache.php;
• add or edit WP_CACHE in wp-config.php;
• define or correct POM_CACHE_HOME;
• install or rewrite Apache rules;
• change CDN behavior;
• clear existing HTML or JSON files.

Those deployment-level files may require filesystem access outside the settings directory. POM Cache reports their status but leaves the changes under your control.

Repair procedure

1. Open Settings → POM Cache → Advanced and review WordPress configuration status.
2. Record any items marked Needs manual change. Those items will still require manual work after the repair.
3. Open General → Cache tools, locate Configuration, and find Fix Configuration.
4. Run Fix Configuration and wait for the success message.
5. Return to the POM Cache settings screen and confirm that your HTML, storage, and JSON choices are still correct.
6. Revisit Advanced → WordPress configuration.
7. Manually resolve any drop-in or constant issue using the exact paths and values displayed there.
8. Clear the affected cache store and test an anonymous eligible request.

On multisite, perform the repair in the intended site's context. Do not assume that fixing one site's generated settings updates every site in the network.

When the tool is not the answer

Do not use Fix Configuration merely because a page is not cached. An eligible request also depends on method, URL, cookies, response type, status, completion markers, permissions, and runtime switches.

If WordPress configuration status reports a drop-in mismatch or missing constants, follow Resolve “advanced-cache.php is not loaded”. If the status is correct but a route still remains dynamic, use Pages are not cached.

After changing storage

When the configured cache location changes, repair the settings files and verify the new location before removing anything from the old one. The repair action does not migrate cached files. Generate fresh content in the new location, confirm it is being read, and only then handle obsolete files using a narrowly scoped, reviewed filesystem operation.