Compatibility release for WordPress 7.1. No functional changes.<\/p>","1.1.0":"
Adds an optional Redis Object Cache module (persistent object cache with a crash-safe fallback). The page cache is unchanged. Enable the Object Cache from the new admin tab; a reachable Redis server and the PHP redis extension are required.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3604442,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3604442,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3604442,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3604442,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.1","1.0.2","1.0.3","1.1.1"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[146,7913,3853,247,45952],"plugin_category":[52,54],"plugin_contributors":[255540],"plugin_business_model":[],"class_list":["post-336362","plugin","type-plugin","status-publish","hentry","plugin_tags-cache","plugin_tags-object-cache","plugin_tags-page-cache","plugin_tags-performance","plugin_tags-redis","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_contributors-flexatech","plugin_committers-flexatech"],"banners":{"banner":"https:\/\/ps.w.org\/flexa-cache\/assets\/banner-772x250.png?rev=3604442","banner_2x":"https:\/\/ps.w.org\/flexa-cache\/assets\/banner-1544x500.png?rev=3604442","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/flexa-cache\/assets\/icon-128x128.png?rev=3604442","icon_2x":"https:\/\/ps.w.org\/flexa-cache\/assets\/icon-256x256.png?rev=3604442","generated":false},"screenshots":[],"raw_content":"\n
Flexa Cache is a full-featured WordPress page-cache and front-end optimization plugin. It installs a self-contained Page Cache<\/strong><\/p>\n\n Front-End Optimization<\/strong><\/p>\n\n Developer-Friendly<\/strong><\/p>\n\n Object Cache (Redis)<\/strong><\/p>\n\n Source code for compiled JavaScript and CSS<\/strong><\/p>\n\n The plugin ships a compiled admin UI in https:\/\/github.com\/flexatech\/flexa-cache<\/p>\n\n The admin UI is built with npm and Vite:<\/p>\n\n After a plugin update:<\/strong> deactivate and reactivate Flexa Cache once so the On activation, Flexa Cache installs an Yes. Cart, checkout, and account pages are automatically excluded from the cache. The cache is also purged when a product's stock level or price changes.<\/p><\/dd>\n The static file cache works on any server (the drop-in uses PHP Click Delete Cache<\/strong> in the Flexa Cache settings page, use The Minify JS toggle is a documented safe no-op when used alone. JavaScript is only ever concatenated (via Combine JS), never minified in isolation \u2014 the plugin ships no JS parser. If you want JS minification, enable Combine JS together with Minify JS.<\/p><\/dd>\n Flexa Cache checks for a foreign In the WordPress admin sidebar, click Flexa Cache<\/strong> (located below Settings). Settings are organised into five sections: Cache, Invalidation, Performance, Exclusions, and Danger Zone.<\/p><\/dd>\n The Object Cache is a persistent store for WordPress's internal data (options, transients, meta, query results) that normally lives in the database. Backing it with Redis means those lookups are served from memory across requests, which reduces database load \u2014 especially on WooCommerce and other dynamic sites. It requires a reachable Redis server and the PHP Nothing breaks. Flexa Cache detects the failure mid-request, serves from its in-memory layer for the rest of the request, and opens a short-lived circuit breaker so the next requests do not stampede a dead server. An admin notice and a Site Health warning appear, and the cache recovers automatically once Redis is back.<\/p><\/dd>\n No. The connection settings (including the password) are written to a marked block in Those advanced topologies (Cluster, Sentinel, Replicated master\/replica, and the Relay\/Predis clients) ship in the separate Flexa Cache Pro<\/strong> add-on. The free plugin covers a single Redis server, which suits the large majority of sites.<\/p><\/dd>\n\n<\/dl>\n\n\nadvanced-cache.php<\/code> drop-in that serves compressed static HTML files before WordPress even loads \u2014 the same technique used by WP Fastest Cache and W3 Total Cache \u2014 giving you maximum TTFB improvement on both Apache and nginx hosts.<\/p>\n\n\n
.gz<\/code> files served natively<\/li>\nindex-mobile.html<\/code>) when Mobile Theme is enabled<\/li>\n\n
.htaccess<\/code> block for dynamic (non-cached) responses<\/li>\n.htaccess<\/code> block<\/li>\nloading=\"lazy\"<\/code> + decoding=\"async\"<\/code> on images and iframes<\/li>\ndefer<\/code> to render-blocking scripts<\/li>\n<link><\/code> to preload + onload<\/code> swap with <noscript><\/code> fallback<\/li>\n\n
wp flexa-cache clear [--url=<url>]<\/code>, wp flexa-cache status<\/code>, wp flexa-cache preload [start|status|cancel]<\/code><\/li>\n\/flexa-cache\/v1\/cache\/purge<\/code>, \/cache\/stats<\/code>, \/cache\/preload<\/code><\/li>\nflexa_cache\/engine\/is_cacheable<\/code>, flexa_cache\/engine\/buffer<\/code>, flexa_cache\/store\/dir<\/code>, flexa_cache\/purged<\/code>, flexa_cache\/settings\/languages<\/code>, and more<\/li>\n?flexa_cache_optimize=0<\/code> disables optimization for a single admin request<\/li>\n\n
object-cache.php<\/code> drop-in with an in-memory L1 + Redis L2 layout<\/li>\nwp-config.php<\/code> (secrets never touch the database)<\/li>\nanalytics<\/code>, watch<\/code>, groups<\/code>, slowlog<\/code>)<\/li>\nassets\/dist\/<\/code>. The human-readable\nsource (apps\/admin\/src<\/code>) and the build tooling are publicly available at:<\/p>\n\n\n
npm install<\/code><\/li>\nnpm run build<\/code> (or npm run dev<\/code> for a watched dev build with HMR)<\/li>\n<\/ol>\n\n\n\n
\/wp-content\/plugins\/flexa-cache<\/code>, or install through the WordPress Plugins<\/strong> screen.<\/li>\nadvanced-cache.php<\/code> drop-in is refreshed. This step is only needed after an update that changes the drop-in \u2014 the release notes will say so when it applies.<\/p>\n\n\n\n
How does the page cache work?<\/h3><\/dt>\n
advanced-cache.php<\/code> drop-in into wp-content\/<\/code> and adds define('WP_CACHE', true)<\/code> to wp-config.php<\/code>. On the next uncached request, the plugin generates a static HTML file. Every subsequent request for that URL is served directly from the file \u2014 no PHP execution, no database query.<\/p><\/dd>\nDoes Flexa Cache work with WooCommerce?<\/h3><\/dt>\n
Does it work on nginx?<\/h3><\/dt>\n
readfile()<\/code>). The Gzip and Browser Caching toggles write Apache .htaccess<\/code> rules; the plugin's class docblocks include the nginx equivalent snippets for hosts that need them.<\/p><\/dd>\nHow do I clear the cache?<\/h3><\/dt>\n
wp flexa-cache clear<\/code> from the command line, or call POST \/wp-json\/flexa-cache\/v1\/cache\/purge<\/code>. To clear a single URL, use the per-URL input in the Cache Stats panel or wp flexa-cache clear --url=https:\/\/example.com\/page\/<\/code>.<\/p><\/dd>\nWhat does \"Minify JS\" do?<\/h3><\/dt>\n
Will it conflict with other caching plugins?<\/h3><\/dt>\n
advanced-cache.php<\/code> on activation and refuses to overwrite it. If you already have a caching plugin installed, deactivate it and remove its drop-in before activating Flexa Cache.<\/p><\/dd>\nWhere are the plugin settings?<\/h3><\/dt>\n
What is the Object Cache and do I need Redis?<\/h3><\/dt>\n
redis<\/code> extension. It is independent of the page cache; you can run either or both.<\/p><\/dd>\nWhat happens if Redis goes down?<\/h3><\/dt>\n
Does enabling the Object Cache store my Redis password in the database?<\/h3><\/dt>\n
wp-config.php<\/code>, never to the options table, and the password is masked in every diagnostic, REST, and CLI output.<\/p><\/dd>\nCan I use Redis Cluster, Sentinel, or Relay?<\/h3><\/dt>\n
1.1.1<\/h4>\n\n
\n
wp_add_inline_script()<\/code> before\/after data (most visibly WordPress core's wp-i18n<\/code>, whose after-script calls wp.i18n.setLocaleData()<\/code>) is now left un-delayed, un-deferred, and un-combined, because that inline companion runs at parse time and would otherwise throw \"wp is not defined\". The Combine JS path recovers the handle from the tag's id<\/code> attribute so it can protect the same scripts even though it operates on the rendered buffer. This also resolves knock-on breakage of scripts that depend on those globals.<\/li>\nhoverintent-js<\/code>; Combine JS \/ Delay JS \/ Render-Blocking now auto-exclude it alongside admin-bar<\/code> (it was previously left in), so the submenu opens reliably.<\/li>\n@wordpress\/components<\/code>, jQuery UI, or block-editor assets affected by 7.1.<\/li>\n<\/ul>\n\n1.1.0<\/h4>\n\n
\n
object-cache.php<\/code> drop-in (in-memory L1 + Redis L2). Caches options, transients, and meta\/query data across requests.<\/li>\nwp-config.php<\/code>, secrets never in the database), metrics, groups table, and flush controls.<\/li>\non_error<\/code> policy, and a Site Health check. Redis outages never cause a white screen.<\/li>\n*-queries<\/code> TTL.<\/li>\nflexa_cache\/object_cache\/trace<\/code> hook.<\/li>\nwp flexa-cache oc<\/code> (enable<\/code>, disable<\/code>, status<\/code>, flush<\/code>, diagnostics<\/code>, analytics<\/code>, watch<\/code>, groups<\/code>, slowlog<\/code>, cli<\/code>, reset<\/code>), and REST endpoints under \/flexa-cache\/v1\/object-cache<\/code>.<\/li>\n1.0.3<\/h4>\n\n
\n
\/ping<\/code> starter REST endpoint left over from the plugin scaffold.<\/li>\nnpm install<\/code> \u2192 npm run build<\/code>) alongside the public repository link.<\/li>\n<\/ul>\n\n1.0.2<\/h4>\n\n
\n
:<\/code>, which previously fused descendant combinators into compound selectors before a pseudo-class (:root :where(\u2026)<\/code> \u2192 :root:where(\u2026)<\/code>) and silently dropped WordPress global-styles rules \u2014 most visibly Gutenberg button styles. Whitespace around { } ; ,<\/code> is still collapsed.<\/li>\n<\/ul>\n\n1.0.1<\/h4>\n\n
\n
manage_options<\/code> capability instead of upload_files<\/code>, so only administrators can trigger site-wide cache operations.<\/li>\nwp_kses_post()<\/code> before it is echoed.<\/li>\n<script><\/code> fallback in the delay-JS loader; the core wp_print_inline_script_tag()<\/code> helper is now always used.<\/li>\n1.0.0<\/h4>\n\n
\n