The drop-in (wp-content/wp-recache-cache.php) runs before WordPress loads, so it cannot read options from the DB. Today it therefore ignores cache_duration TTL and the exclusion list; staleness is only masked by purge-on-update and purge-on-exclusion-change, and TTL expiry never applies on the drop-in path.
Spec:
Activation and every settings save regenerate wp-content/wp-recache-config.php returning an array: cache_duration, exclude_urls, rejected_cookies (#10), separate_mobile_cache
The drop-in requires this file when present and enforces TTL + exclusions + cookies itself
Deactivation/uninstall removes the config file
The drop-in (wp-content/wp-recache-cache.php) runs before WordPress loads, so it cannot read options from the DB. Today it therefore ignores cache_duration TTL and the exclusion list; staleness is only masked by purge-on-update and purge-on-exclusion-change, and TTL expiry never applies on the drop-in path.
**Spec:**
- Activation and every settings save regenerate wp-content/wp-recache-config.php returning an array: cache_duration, exclude_urls, rejected_cookies (#10), separate_mobile_cache
- The drop-in requires this file when present and enforces TTL + exclusions + cookies itself
- Deactivation/uninstall removes the config file
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The drop-in (wp-content/wp-recache-cache.php) runs before WordPress loads, so it cannot read options from the DB. Today it therefore ignores cache_duration TTL and the exclusion list; staleness is only masked by purge-on-update and purge-on-exclusion-change, and TTL expiry never applies on the drop-in path.
Spec: