ezCache

2.6.5

• Fixed: The DNS Prefetch and Preconnect fields are no longer replaced with “true”/”false”. They are domain-list text fields but were being cast to a boolean when the Performance screen loaded, which overwrote the saved domains.
• Fixed: Combining Google Fonts no longer drops the font-display value. The combined request now uses font-display: swap by default (Google’s recommendation), preserving fast text rendering (FCP/LCP). Filterable via ezcache_google_fonts_display.

2.6.4

• Fixed: URL exclusions (Rejected URIs) with a wildcard () at the end or in the middle of the pattern now work correctly. Previously only a wildcard directly after a slash matched, so patterns like *add_to_wishlist silently failed with no error.
• Added: Requests carrying a nonce or action parameter (_wpnonce, wc-ajax, add-to-cart, action, doing_wp_cron, add_to_wishlist and similar) are no longer cached. This prevents cache bloat from per-request values and avoids serving one visitor’s nonce to another. The list is filterable.

2.6.3

• Fixed: The cache no longer modifies non-HTML responses. Plain-text files (such as IndexNow verification keys and llms.txt), RSS/Atom feeds and other non-HTML output previously received the ezCache footer comment and other HTML optimizations, which could corrupt them and break IndexNow verification, for example. Only real HTML pages are processed and cached now; everything else passes through untouched.

2.6.2

• Fixed: Inline JavaScript minification no longer corrupts non-JavaScript script blocks such as JSON-LD structured data. The minifier turned true/false into !0/!1 (valid JavaScript but invalid JSON), which could break Google Rich Results with no visible error on the site. Only real JavaScript is minified now; JSON-LD, application/json and template blocks are left untouched. The same protection was added for non-CSS style blocks, and the page cache is flushed on update so previously cached pages are regenerated.

2.6.1

• Fixed: “Run Database Cleanup Now” now actually cleans the database. It previously reported success without deleting anything (it called a class left over from an internal rename). The button now also reports how many items were removed in each category.

2.6.0

• Added: Optional “Ignore tracking parameters when caching” setting (off by default, for advanced users). When enabled, pages are served from cache regardless of the value of tracking parameters such as gclid, fbclid or utm_*, so ad-campaign traffic is served from cache instead of creating a new cache entry per click. The ignored parameter list is configurable.