Repository navigation
Releases
v1.1.2
What's Changed
- ci: pin sympress/workflows to v1.3.2 by @brianvarskonst in #61
- fix: harden multisite settings, purge queue, config and full purge by @brianvarskonst in #62
Full Changelog: v1.1.1...v1.1.2
v1.1.1
What's Changed
- fix(deps): require patched Symfony Filesystem and HttpClient by @brianvarskonst in #60
Full Changelog: v1.1.0...v1.1.1
v1.1.0
Nginx Cache 1.1.0 makes automatic purges match what actually changed: site-wide settings now clear stale pages, WooCommerce sell-outs no longer wipe the whole cache, and multisite purges reach the site where the change happened.
- Site-wide settings and widgets purge the cache. Changing the site title, tagline, site icon, front page or posts page setting, posts per page, widget placement or the settings of a registered widget type now purges the whole cache. These values render on every page; before, cached pages kept the old output until they expired. The hooks only fire when a stored value actually changes (#55).
- WooCommerce sell-outs stay selective. Selling out a product assigns the internal
product_visibilityterm, and every variation save ran through the non-viewableproduct_variationpost type. Both forced a full purge, although the WooCommerce product hooks already purge the product, its parent, its archives and the shop. Variations that a plugin publishes as their own pages are still purged directly (#57). - Multisite purges run in the right site. Changes made through
switch_to_blog(), such as network admin edits of a subsite, collected the subsite's URLs but ran in the current site, which rejected them as foreign. The subsite stayed stale and the request remained in the current site's retry queue. Pending purges now run in the blog their hook fired in; sites created in the same request are skipped because they have no cache yet (#58). - Static analysis with PHPStan 2.3.3 passes again. Development only; no runtime change (#54, closes #12).
On upgrade: no configuration change. Option names, stored values and the generated Nginx configuration are unchanged, so no include regeneration or Nginx reload is needed. Expect a full purge after site title, reading-setting or widget changes, and fewer full purges on WooCommerce shops.
Implementation: #54, #55, #57, #58
Release preparation: #56
Release commit: 73c0bc23823f94cda77259193b3a78fe59d991ff. The SSH-signed tag was verified locally with the SymPress release key.
Validation: all eight QA checks passed on every fix PR and the release PR, and the post-merge QA run on main passed. Local QA in PHP 8.5 passed: 120 tests / 596 assertions, coding standards, static analysis and hook checks. The WordPress integration suites passed locally on MariaDB 11.8 and MySQL 8.4 with the CI-pinned images, plus the Redis and native Nginx 1.26 suites. Local test installs with an Nginx FastCGI cache (WordPress 7.1.2, WooCommerce 11.2.1) confirmed the behavior through X-Nginx-Cache on a single site, a subdirectory multisite and a subdomain multisite, including queue mode. The final checks ran against the released ZIP. The ZIP contains the production dependencies and passed checksum and source checks: 2,477 file checksums, 131 source files identical to the tag, and no development packages. Archive build and checks.
Download ns-nginx-cache-1.1.0.zip below for a ready-to-install WordPress package. The automatically generated GitHub source archives do not include the production dependencies. Composer users can update sympress/nginx-cache to ^1.1.0.
v1.0.11
Nginx Cache 1.0.11 lets responses that send a positive X-Accel-Expires enter the FastCGI cache for the TTL they request, while private responses stay out of it.
- Positive
X-Accel-Expiresvalues are honored. The generatedfastcgi_no_cacherule passed$upstream_http_x_accel_expiresdirectly, so any nonzero value prevented storage. Nginx now applies the header's native TTL semantics.X-Accel-Expires: 0,Set-Cookieand the existing bypass rules still prevent caching. - Private responses stay out of the cache. A positive
X-Accel-Expiresoverrides Nginx' ownCache-Controlchecks, so a new$sympress_cache_skip_cache_controlmap keeps responses withprivate,no-cacheorno-storeuncached, including mixed-case and qualified directives.
On upgrade: regenerate the HTTP and FastCGI includes together (wp nginx-cache config --section=http and --section=fastcgi) and reload Nginx. The FastCGI include references the new map from the HTTP include, so nginx -t rejects a mixed pair. Use Nginx 1.23 or newer: older versions only expose the first of repeated upstream Cache-Control headers to the map. Pages that send a positive X-Accel-Expires will now be served from the cache for that TTL. Option names and stored values are unchanged.
Implementation: #52
Release preparation: #53
Release commit: 045aea5183c0ecbad1e430e9fe6fc93507a875ea. The SSH-signed tag was verified locally with the SymPress release key.
Validation: all eight QA checks passed on the fix PR and the release PR, and the post-merge QA run on main passed. Local QA in PHP 8.5 also passed: 116 tests / 583 assertions, coding standards, static analysis and hook checks. A new unit test runs the generated Cache-Control regex against private and public directive samples and fails when the pattern is broken. Real Nginx 1.22 and 1.24 containers confirmed that 1.22 exposes only the first of repeated upstream Cache-Control headers while 1.24 combines them. The ZIP contains the production dependencies and passed checksum and source checks: 2,475 file checksums, 120 source files identical to the tag, and no development packages. Archive build and checks.
Download ns-nginx-cache-1.0.11.zip below for a ready-to-install WordPress package. The automatically generated GitHub source archives do not include the production dependencies. Composer users can update sympress/nginx-cache to ^1.0.11.
SHA-256 for ns-nginx-cache-1.0.11.zip:
84fe0f278fe5dc887575fd58768ddd494a17ecdb6a947687d418f06a45da6401
Nginx Cache 1.0.10
Nginx Cache 1.0.10 makes the generated one-minute 404 cache rule actually work. Previously every 404, including bot scans for missing files, reached PHP. It contains the same code as 1.0.9, whose tag was pushed unsigned and cannot be replaced because release tags are immutable; 1.0.10 is its signed successor.
- Anonymous 404 responses are cached for one minute. WordPress sends
Cache-Control: no-cache, must-revalidate, max-age=0, no-store, privatewith every 404, so Nginx never stored one and the generatedfastcgi_cache_valid 404 1mrule had no effect. Anonymous GET/HEAD 404s now sendCache-Control: public, max-age=60through the corenocache_headersfilter. Logged-in, admin, AJAX, cron and authorized requests keep WordPress' no-store headers, and every othernocache_headers()caller is unchanged.
On upgrade: option names, stored values and the generated Nginx configuration are unchanged, so no Nginx reload is required. 404 pages for anonymous visitors may now be served from the Nginx cache for up to 60 seconds. Publishing content at a previously missing URL purges that URL as before. Sites on 1.0.8 can upgrade directly, and sites on 1.0.9 get no functional change.
Implementation:
- #48 (closes #47). It also updates the development dependency PHPUnit to 13.4.5 for GHSA-9vw2-f4vp-x7gf, which
composer auditin the QA job rejected.
Release preparation: #49 (1.0.9, unsigned tag) and #50
Release commit: 256320b7ffeb5e456418e741c71d5ae23aae0d51. The SSH-signed tag was verified locally with the SymPress release key.
Validation: all eight QA checks passed on the fix PR and on both release PRs, and the post-merge QA run on main passed. Local QA also passed: 115 tests / 570 assertions, coding standards, static analysis and hook checks. An end-to-end check with real Nginx and PHP-FPM using the generated configuration and WordPress' exact 404 headers showed MISS MISS MISS before and MISS HIT HIT after the change, with logged-in requests bypassed. The ZIP contains the production dependencies and passed checksum and source checks: 2,475 file checksums, 124 source files identical to the tag, and no development packages. Archive build and checks.
Download ns-nginx-cache-1.0.10.zip below for a ready-to-install WordPress package. The automatically generated GitHub source archives do not include the production dependencies. Composer users can update sympress/nginx-cache to ^1.0.10.
SHA-256 for ns-nginx-cache-1.0.10.zip:
dc8cc270415d4a3cbd75ebeed17179d795bc5eb9891c2afc41d5d30ce8e03b0b
v1.0.9
Important
The v1.0.9 tag is not signed. Release tags in this repository are immutable, so it cannot be replaced with a signed tag. Nginx Cache 1.0.10 is the signed successor with identical code; prefer it for new installs and updates.
Nginx Cache 1.0.9 makes the generated one-minute 404 cache rule actually work. Previously every 404, including bot scans for missing files, reached PHP.
- Anonymous 404 responses are cached for one minute. WordPress sends
Cache-Control: no-cache, must-revalidate, max-age=0, no-store, privatewith every 404, so Nginx never stored one and the generatedfastcgi_cache_valid 404 1mrule had no effect. Anonymous GET/HEAD 404s now sendCache-Control: public, max-age=60through the corenocache_headersfilter. Logged-in, admin, AJAX, cron and authorized requests keep WordPress' no-store headers, and every othernocache_headers()caller is unchanged.
On upgrade: option names, stored values and the generated Nginx configuration are unchanged, so no Nginx reload is required. 404 pages for anonymous visitors may now be served from the Nginx cache for up to 60 seconds. Publishing content at a previously missing URL purges that URL as before.
Implementation:
- #48 (closes #47). It also updates the development dependency PHPUnit to 13.4.5 for GHSA-9vw2-f4vp-x7gf, which
composer auditin the QA job rejected.
Release preparation: #49
Release commit: 2c2eb483eb62749431bba8f7ea6b39605d94d3a2.
Validation: all eight QA checks passed on the fix PR and on the rebased release PR, and the post-merge QA run on main passed. Local QA also passed: 115 tests / 570 assertions, coding standards, static analysis and hook checks. An end-to-end check with real Nginx and PHP-FPM using the generated configuration and WordPress' exact 404 headers showed MISS MISS MISS before and MISS HIT HIT after the change, with logged-in requests bypassed. The ZIP contains the production dependencies and passed checksum and source checks: 2,475 file checksums, 124 source files identical to the release commit, and no development packages. Archive build and checks.
Download ns-nginx-cache-1.0.9.zip below for a ready-to-install WordPress package. The automatically generated GitHub source archives do not include the production dependencies. Composer users can update sympress/nginx-cache to ^1.0.9.
SHA-256 for ns-nginx-cache-1.0.9.zip:
ef3444518ec45a60138ac9ecc25383f6bb58ede0e60a1e7f7a853912e6d161fb
v1.0.8
Nginx Cache 1.0.8 fixes three prewarm and keep-warm reliability problems. A page now counts as warmed only once Nginx could actually cache it, a failing sitemap no longer keeps already known pages cold, and a first keep-warm run that never finishes is no longer reported as healthy.
- Prewarm success needs a complete response. An HTTP 200 whose body broke off or stalled after the headers used to be checkpointed as warmed, although Nginx stores no entry for an aborted transfer. The body is now streamed and discarded within the existing five-second limits, without buffering it in memory. An incomplete transfer is a retryable URL failure, and complete sibling URLs keep their progress.
- Sitemap failures no longer block known targets. A sitemap error, such as an HTTP 503, used to stop the purge follow-up before any known page (for example the home page) was requested and before cache layer, remote and Cloudflare work ran. Known targets are now warmed in batches that do not spend the retry budget, and the remaining follow-up work runs. Discovery is retried with backoff after every failed attempt, also while a known page is still failing. A later successful discovery adds just the missing targets.
- Precise discovery errors. Each failed sitemap is reported with its URL and a fixed reason: HTTP status, timeout, request failure, the 2 MiB budget, invalid XML, a non-sitemap document or forbidden XML declarations. Provider messages and response bodies are never stored. The latest failure appears as
sitemap_discovery_failureinwp nginx-cache side-effects detailsand the diagnostic report until discovery succeeds again. - Overdue first keep-warm cycle.
overdueused to require a completed cycle, so a first run that stalled, crashed on every attempt or never started kept Site Health at "good". The inactivity window now counts from the last completion, otherwise from the first cycle's start or first attempt, otherwise from its due cron event. Start-up, an event that is not yet due and a disabled keep-warm stay quiet, and a worker heartbeat does not replace a completed cycle.
On upgrade: option names, stored values and the generated Nginx configuration are unchanged, so no Nginx reload is required. Follow-up tasks queued by 1.0.7 continue unchanged. The sympress_nginx_cache_side_effects_processed payload additionally reports prewarm.discovery_complete. The new non-autoloaded diagnostic option sympress_nginx_cache_sitemap_discovery_failure is removed on uninstall.
Implementation:
Release preparation: #46
Release commit: f2f0c1c2bf810df628822590544ae09217b09675. The SSH-signed tag was verified locally with the SymPress release key.
Validation: all eight QA checks passed on each fix PR and on the release PR, each on its final rebased head, and the post-merge QA run on main passed. Local QA also passed: 113 tests / 566 assertions, coding standards, static analysis and hook checks. The WordPress 7.1.2 integration suites on MariaDB 11.8 passed with 314 assertions and 26 contention checks, plus 103 multisite checks. Every regression check was also confirmed to fail without its fix. The ZIP contains the production dependencies and passed checksum and source checks: 2,474 file checksums, 124 source files identical to the tag, and no development packages. Archive build and checks.
Download ns-nginx-cache-1.0.8.zip below for a ready-to-install WordPress package. The automatically generated GitHub source archives do not include the production dependencies. Composer users can update sympress/nginx-cache to ^1.0.8.
SHA-256 for ns-nginx-cache-1.0.8.zip:
3b03324f27c9d99cb64673d3730f86edd33a4eaf874358e8dea735bd1797c344
v1.0.7
Nginx Cache 1.0.7 shows how many of your public pages are actually cached, and keeps the hit-rate statistics complete across log rotation.
- Page coverage on the dashboard. The main card now compares public page URLs with the local cache files: the home page and language home pages, plus published content of all viewable post types. Every language version counts as its own URL. Each page is shown as cached, expired, not cached, excluded by a bypass rule, or unknown. Key variants of one URL count once. Intentionally excluded pages do not count as missing coverage.
- Bounded and side-effect free. At most 500 recently modified entries are checked per reload, and a limited check is labelled as such. The check only reads the filesystem: no HTTP requests, purges or prewarming. An unreadable cache root or an alternative purge backend shows "not determinable" instead of zero.
- HTTP hit rate moved to Tools. The request-based hit rate is now in the Tools tab (simple mode: "Technische Statistik"). Its label says that it counts individual HTTP requests in a sliding window, not pages or visitors.
- No gap after log rotation. The metrics reader also reads
<log>.1within the existing 1 MiB / 5,000-line budget, so copytruncate and rename/create rotation no longer drop still-current requests from the 60-minute window. Bytes still shared by both files during copytruncate are counted once. An unread recent generation, such as an archive that is already compressed (nodelaycompress), marks the window as incomplete.
On upgrade: option names, stored values and the generated Nginx configuration are unchanged, so no Nginx reload is required. Only the dashboard layout changes.
Implementation: #38 (closes #36 and #37)
Release preparation: #39
Release commit: bd8c6c90ac4193aed10faa232a8f6bd8090a7186. The SSH-signed tag was verified locally with the SymPress release key.
Validation: all eight QA checks on the release PR passed on the identical tree, and the post-merge QA run on main passed. Local QA also passed: 111 tests / 551 assertions, coding standards, static analysis and hook checks, plus the WordPress 7.1.2 integration suites on MariaDB 11.8. The ZIP contains the production dependencies and passed checksum and source checks: 2,473 file checksums, 125 source files identical to the tag, and no development packages. Archive build and checks.
Download ns-nginx-cache-1.0.7.zip below for a ready-to-install WordPress package. The automatically generated GitHub source archives do not include the production dependencies. Composer users can update sympress/nginx-cache to ^1.0.7.
SHA-256 for ns-nginx-cache-1.0.7.zip:
b144d20f71f641488edbcc89f921c2b901cd2193f08b968038b32efc5eacbf24
v1.0.6
Nginx Cache 1.0.6 puts every preload setting in one place: the Preload tab.
- One place for preload. The Preload tab now holds the prewarm switch, the fixed prewarm URLs, sitemap discovery and the sitemap URL (previously in the Cache tab), and the keep-warm retention mode (previously under the Cache tab's Nginx limits). It also exposes the "Prewarm only the changed URLs" scope, which until now could only be set through presets.
- No duplicate fields. The Cache tab and the dashboard no longer repeat preload fields. The dashboard shows the preload status (on/off, number of target URLs, sitemap on/off) and links to the Preload tab.
- Clearer help texts. The tab explains that preload and prewarm are the same feature and which options depend on the prewarm switch. The "prewarm only the changed URLs" option now states that full purges then warm nothing.
- Accurate quick action. The dashboard button formerly labeled "Prewarm" is now Purge and prewarm, because it purges the whole cache first.
On upgrade nothing changes in behavior. Option names and stored values are unchanged; only admin fields moved. The generated Nginx configuration is unchanged, so no Nginx reload is required.
Implementation: #33 (closes #32)
Release preparation: #34
Release commit: 925b078c991eb53fe8ccf97e27e41d0e650bbae6. The SSH-signed tag was verified locally with the SymPress release key.
Validation: all eight QA checks on the release PR passed on the identical tree, and the post-merge QA run on main passed. Local QA also passed: 105 tests / 530 assertions, coding standards, static analysis and hook checks, plus the WordPress 7.1.2 integration suites. The ZIP contains the production dependencies and passed checksum and source checks: 2,469 file checksums, 122 source files identical to the tag, and no development packages. Archive build and checks.
Download ns-nginx-cache-1.0.6.zip below for a ready-to-install WordPress package. The automatically generated GitHub source archives do not include the production dependencies. Composer users can update sympress/nginx-cache to ^1.0.6.
SHA-256 for ns-nginx-cache-1.0.6.zip:
e8a43e8fbed55179eeb9c55df8bd332753ea08375de37269219b0873cff8a674
v1.0.5
Nginx Cache 1.0.5 keeps prewarmed pages warm by default, keeps outdated prewarm targets from blocking a stored plan, and keeps failure details for local purge queues.
- Keep prewarmed pages warm (new default
keep_warm). A bounded background refresh requests the prewarm targets every half inactivity window, five URLs per cron tick. Successfully prewarmed, cacheable pages therefore no longer go cold during quiet periods. Freshness, purges, bypass rules andmax_sizeeviction still apply. The newevict_inactiveretention mode keeps the previous behavior for large or storage-constrained sites. Failures and missed cycles appear inwp nginx-cache diagnosticsand Site Health. - Outdated prewarm targets no longer block stored plans. Same-origin redirects are followed for up to three revalidated hops. Removed, rejected, externally redirected or looping targets are skipped and reported instead of exhausting the retry budget. Timeouts, rate limits and 5xx responses keep bounded retries.
- Purge queue failures keep safe evidence. Queue details and diagnostics show the failure time, the processing phase and safe exception metadata. Contending workers cannot overwrite this evidence.
Behavior change on upgrade. With prewarm enabled, sites still on the default 3600-second inactivity timeout switch to keep_warm and send bounded same-origin GET requests for their prewarm targets. Sites with a changed timeout keep inactivity eviction. The generated Nginx configuration is unchanged, so no Nginx reload is required. Keep-warm relies on the documented per-minute cron runner. See the retention migration notes.
Implementation: #26, #29, #30
Release preparation: #31
Release commit: 8c25a7121afe9b2121da263220391a218815ef62. The SSH-signed tag was verified locally with the SymPress release key.
Validation: all eight post-merge QA checks passed. Local QA also passed: 105 tests / 530 assertions, coding standards, static analysis and hook checks. The ZIP contains the production dependencies and passed checksum, source and WordPress runtime checks: 2,469 file checksums, 121 matching source files, 41 production packages and no development packages. Archive build and checks.
Download ns-nginx-cache-1.0.5.zip below for a ready-to-install WordPress package. The automatically generated GitHub source archives do not include the production dependencies. Composer users can update sympress/nginx-cache to ^1.0.5.
SHA-256 for ns-nginx-cache-1.0.5.zip:
68a4c4f921393e087f6a8137e3c1bc8fa9b35ba2890bbd2a255e645627da000b