Repository navigation
v3.7.3 — Site-only WordPress object-cache refresh
Site-only WordPress object-cache refresh
The site-level Clear WP Engine + Cloudflare cache action now invalidates known WordPress object-cache entries for the selected subsite before dispatching WP Engine page-cache and Cloudflare zone purges. This refreshes stale WordPress data after direct database search-replace.
- Includes autoloaded and individual options, existing posts and metadata, terms and metadata, comments and metadata, taxonomy relationships, and core query versions.
- Never calls a backend or group flush, changes WP Engine's customer-wide cache generation, or clears other subsites' entries.
- Stops before page/CDN dispatch if scoped invalidation cannot be verified. Existing retries and network maintenance behavior remain intact.
- Opaque third-party keys and individually cached deleted records cannot be safely enumerated and are not included.
Validated with standalone/multisite regressions and a live WP Engine multisite purge: persistent Yoast option cache matches raw SQL, public JSON-LD has no old development hostname, and six sibling-site cache sentinels plus sibling autoloaded options survived unchanged.