Comprehensive audit and hardening release across all 8 core caching pipelines, including early drop-in execution, selective bypass cookie router, Redis multi-driver resilience, contextual Admin Bar & WP-CLI invalidation, and Cloudflare edge synchronization.<\/p>","1.6.27":"
Hardened early drop-in and Apache\/LiteSpeed proxy feed\/sitemap bypass parity and automated config snapshot compilation.<\/p>","1.6.26":"
Recommended update for all Nginx, Plesk, and WooCommerce environments with official 502 Bad Gateway buffer resolution.<\/p>","1.6.24":"
WordPress 7.1 compatibility release. Recommended update for all users.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3660680,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3660680,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3660680,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3660680,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.6.23","1.6.24","1.6.25","1.6.34"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[262246],"plugin_tags":[146,68923,5896,247,286],"plugin_category":[45,52,54],"plugin_contributors":[276962,276961],"plugin_business_model":[],"class_list":["post-352324","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-cache","plugin_tags-full-page-cache","plugin_tags-page-speed","plugin_tags-performance","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_contributors-celsiusanderson","plugin_contributors-nasruleam","plugin_committers-celsiusanderson"],"banners":{"banner":"https:\/\/ps.w.org\/lumen-cache\/assets\/banner-772x250.png?rev=3660680","banner_2x":"https:\/\/ps.w.org\/lumen-cache\/assets\/banner-1544x500.png?rev=3660680","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/lumen-cache\/assets\/icon-128x128.png?rev=3660680","icon_2x":"https:\/\/ps.w.org\/lumen-cache\/assets\/icon-256x256.png?rev=3660680","generated":false},"screenshots":[],"raw_content":"\n
LumenCache implements a RAM-first full-page cache with a WordPress\n advanced-cache.php drop-in. On a cache HIT, the drop-in serves complete HTML\nbefore the normal WordPress bootstrap and database queries. This early-response\npath reduces application-layer work and keeps repeat page requests fast across\nNginx, Apache, and LiteSpeed.<\/p>\n\n
The cache is designed to fail open when its storage layer is unavailable, so a\ncache connection problem does not take the WordPress site offline.<\/p>\n\n
Academic Reference:\n\"Dynamic Resource Mapping in Zero-Reload Server Architectures: Eliminating\nApplication-Layer Latency and Extension Dependency in High-Concurrency CMS\npersonalised requests continue through the full WordPress stack.<\/p>\n\n
This architecture is intended to reduce repeated bootstrap work, database\nqueries, and extension overhead while preserving WordPress compatibility. It\nalso provides a practical bridge between academic performance research and\neveryday publishing workloads, including content-heavy sites, WooCommerce\ncatalogues, and membership-driven pages.<\/p>\n\n
Research author: Dean Nasrul Eam \u2014 Light & Composition University<\/strong>.<\/p>\n\n All settings are configurable from LumenCache \u2192 Settings<\/strong> in the WordPress\nadmin. Optionally override any setting via wp-config.php \u2014 constants always win:<\/p>\n\n LumenCache stores rendered page HTML and cache metadata in the in-memory cache\nservice configured by the site administrator. It does not send cache contents,\nvisitor data, or analytics data to a third-party LumenCache service. The\noptional user-state endpoint returns only the requested dynamic values to the\nrequesting browser; sites should review those values and their own privacy\npolicy before enabling personalized hydration.<\/p>\n\n\n Nginx has a default To resolve this, add the following FastCGI and proxy buffer directives to your Nginx configuration (within the After adding these directives, test and reload Nginx:\n nginx -t && systemctl reload nginx<\/p><\/dd>\n Two common causes:\n1. Nginx config not applied<\/strong> \u2014 visit Server Setup and paste the config blocks.\n2. WooCommerce session cookie<\/strong> \u2014 fixed in v1.1.0. Previous versions bypassed\n the cache for all<\/em> visitors on WooCommerce sites due to the always-present\n wp_woocommerce_session_* cookie.<\/p><\/dd>\n When Yes. LiteSpeed supports Apache-compatible Yes \u2014 constants always take precedence over admin settings. If you define a\nconstant, the corresponding field in the Settings tab is shown locked (read-only).<\/p><\/dd>\n\n<\/dl>\n\n\nEight-Subsystem Architecture<\/h4>\n\n
\n
sys_active_state<\/code> cookie routes\nlogged-in users and cart-active visitors to live PHP.<\/li>\n\/wp-json\/lumencache\/v1\/user-state<\/code> serves\npersonalised fragments for skeleton-hydration clients.<\/li>\nskeleton-hydration.js<\/code> replaces cached\nplaceholders with live content on load.<\/li>\nflush<\/code>, flush-url<\/code>, status<\/code> commands.<\/li>\n<\/ol>\n\nConfiguration (optional)<\/h4>\n\n
define( 'LUMENCACHE_REDIS_HOST', '127.0.0.1' );\ndefine( 'LUMENCACHE_REDIS_PORT', 6379 );\ndefine( 'LUMENCACHE_REDIS_SOCKET', '' );\ndefine( 'LUMENCACHE_REDIS_PASSWORD', '' );\ndefine( 'LUMENCACHE_REDIS_DATABASE', 0 );\ndefine( 'LUMENCACHE_REDIS_TIMEOUT', 1.0 );\ndefine( 'LUMENCACHE_REDIS_PREFIX', 'cache:' );\ndefine( 'LUMENCACHE_CACHE_TTL', 86400 );\ndefine( 'LUMENCACHE_CACHE_SALT', '' );\ndefine( 'LUMENCACHE_CACHE_QUERY_STRINGS', false );\ndefine( 'LUMENCACHE_PROXY_PASSWORD', '' );\n<\/code><\/pre>\n\nWP-CLI<\/h4>\n\n
wp lumencache flush\nwp lumencache flush-url https:\/\/example.com\/page\/\nwp lumencache status<h3>Privacy<\/h3>\n<\/code><\/pre>\n\n\n
Getting a 502 Bad Gateway on Nginx after activating or during WooCommerce use?<\/h3><\/dt>\n
fastcgi_buffer_size<\/code> of only 4KB\u20138KB. When combining rich caching headers with WooCommerce session cookies, the upstream response header exceeds this limit. Nginx immediately terminates the connection with:\n upstream sent too big header while reading response header from upstream, resulting in an instant 502 Bad Gateway error.<\/p>\n\nhttp {}<\/code>, server {}<\/code>, or PHP location<\/code> block):<\/p>\n\nfastcgi_buffer_size 32k;\nfastcgi_buffers 16 16k;\nfastcgi_busy_buffers_size 32k;\nproxy_buffer_size 32k;\nproxy_buffers 16 16k;\nproxy_busy_buffers_size 32k;\n<\/code><\/pre>\n\nWhy are 0 pages cached?<\/h3><\/dt>\n
Why can key salting affect server-level caching?<\/h3><\/dt>\n
LUMENCACHE_CACHE_SALT<\/code> is set, PHP stores keys as SHA-256 hashes. A\nserver-level configuration must use the same key strategy or it will produce\ncache misses. Disable the salt for a plain-key configuration, or use the\ncompatible hashed-key server template.<\/p><\/dd>\nDoes LumenCache work with LiteSpeed?<\/h3><\/dt>\n
.htaccess<\/code> rewrites. LumenCache uses\nthe Apache proxy mode on LiteSpeed. For better performance, ask your host\nwhich in-memory cache acceleration options are available.<\/p><\/dd>\nCan I still use wp-config.php constants?<\/h3><\/dt>\n
1.6.34 (September 15, 2026)<\/h4>\n\n
\n
lumencache_is_pro_active()<\/code> to verify defined( 'LUMENCACHE_PRO_VERSION' ) && get_option( 'lumencache_pro_status' ) === 'active'<\/code>, preventing false positive status if the Pro add-on is deactivated or uninstalled.<\/li>\nlumencache_purge_urls<\/code> into single-URL purge operations (purge_url<\/code>), ensuring Admin Bar \"Purge This URL\" and WP-CLI flush-url<\/code> actions automatically purge Cloudflare edge cache alongside local Redis.<\/li>\nserver\/lumen-cache-proxy.php<\/code>) on cache HITs, and updated Drop_In::write_config()<\/code> to synchronize compiled pro_active<\/code> state to deployed proxy files.<\/li>\nfrom_tab<\/code> retention to the Cloudflare purge form on the Cache Controls page, keeping administrators on their current tab after purging.<\/li>\n<\/ul>\n\n1.6.33 (September 15, 2026)<\/h4>\n\n
\n
wp-admin\/index.php<\/code> after flushing cache via redirect_to<\/code> handling, complete with dismissible success notice and refined button hover styling.<\/li>\nwp lumencache status<\/code> with --format<\/code> support (table, json, yaml, csv) and drop-in \/ WP_CACHE<\/code> status visibility; aligned flush-url<\/code> output with semantic WP-CLI warning conventions.<\/li>\nwc_load_cart<\/code>) during REST API user-state hydration requests; added LifterLMS course-progress resolution support.<\/li>\nlumencache_user_state_keys<\/code> and lumencache_resolve_user_state_{$key}<\/code> filters for developer extensibility.<\/li>\nX-WP-Nonce<\/code> header authentication across REST user-state hydration and Admin Bar AJAX flush handlers.<\/li>\n<\/ul>\n\n1.6.32 (September 15, 2026)<\/h4>\n\n
\n
lumencache_test_redis<\/code>) supporting both phpredis and Predis drivers, Unix sockets, host\/port, database indexes, connection timeouts, and authentication passwords.<\/li>\nhistory.replaceState<\/code>) on sidebar tab switches, preventing stale tab states across page reloads.<\/li>\ntab<\/code> and from_tab<\/code> state retention across all admin actions (cache flushes, drop-in deployment, settings save, salt save, and rewrite operations), preserving the user's active view after every submission.<\/li>\ncache:<\/code>) when clearing key prefix.<\/li>\nSettings::reset_cache()<\/code> method to reset in-process configuration memory.<\/li>\n<\/ul>\n\n1.6.31 (September 15, 2026)<\/h4>\n\n
\n
nginx_map_block()<\/code> and sample Nginx configurations with wp-postpass_<\/code> and comment_author_<\/code> cookie bypass rules, preventing cached responses for unlocked password-protected posts and returning commenters.<\/li>\n.htaccess<\/code> rewrite rules to directly exclude \/feed\/<\/code> requests and XML sitemaps before proxy evaluation, avoiding unnecessary PHP execution overhead.<\/li>\nwp-postpass_<\/code> and comment_author_<\/code> cookie rewrite conditions to .htaccess<\/code> configuration.<\/li>\nHtaccess::deploy_proxy()<\/code> to verify and ensure target upload directory existence with wp_mkdir_p()<\/code>.<\/li>\n\\Redis::OPT_READ_TIMEOUT<\/code>, Predis read_write_timeout<\/code>, and comment_author_<\/code> cookie bypass across both server\/lumen-cache-proxy.php<\/code> and server\/advanced-cache.php<\/code>.<\/li>\n<\/ul>\n\n1.6.30 (September 15, 2026)<\/h4>\n\n
\n
\\Redis::OPT_READ_TIMEOUT<\/code>) and Predis (read_write_timeout<\/code>) to protect PHP worker processes from hanging on stalled Redis operations.<\/li>\nkey_count()<\/code> to eliminate redundant full-keyspace SCAN operations across admin page views.<\/li>\ndelete()<\/code> and delete_pattern()<\/code> against PHP 8.1+ argument unpacking errors by guaranteeing integer-indexed array keys with array_values()<\/code>.<\/li>\nmemory_used()<\/code> across both phpredis and Predis drivers for accurate RAM usage reporting.<\/li>\nreconnect()<\/code> and get_prefix()<\/code> helper methods to Redis_Connector<\/code>.<\/li>\n<\/ul>\n\n1.6.29 (September 15, 2026)<\/h4>\n\n
\n
clear_active_cookie()<\/code>) when WooCommerce cart is emptied or subscriptions stop, ensuring sys_active_state<\/code> cookie is preserved while user remains logged in.<\/li>\n\/wc-api\/<\/code> to safeguard payment gateway callbacks and webhooks from being cached.<\/li>\nwoocommerce_variation_set_stock<\/code> to immediately purge stale caches when variable product inventory levels are updated.<\/li>\nsend_cookie()<\/code> with reverse proxy HTTPS detection via HTTP_X_FORWARDED_PROTO<\/code>.<\/li>\n<\/ul>\n\n1.6.28 (September 15, 2026)<\/h4>\n\n
\n
wp-postpass_<\/code> cookie).<\/li>\nerror_get_last()<\/code>) during output buffer capture to guarantee broken pages or fatal errors are never written to cache.<\/li>\ntransition_post_status<\/code>) so unpublishing or trashing a post immediately clears its cached HTML from Redis.<\/li>\ncomment_post<\/code>, edit_comment<\/code>, wp_set_comment_status<\/code>, delete_comment<\/code>, trashed_comment<\/code>, spammed_comment<\/code>) and created_term<\/code>.<\/li>\n1.6.27 (September 15, 2026)<\/h4>\n\n
\n
lumen-cache-proxy.php<\/code>) with complete feed bypass rules (\/feed\/<\/code> and ?feed=<\/code>) to prevent XML feeds from caching as HTML.<\/li>\nadvanced-cache.php<\/code> and lumen-cache-proxy.php<\/code> to cover core WordPress (wp-sitemap<\/code>), standard sitemaps (sitemap_index<\/code>), and paginated variants.<\/li>\nwp-content\/uploads\/lumen-cache-proxy.php<\/code> on file deployment and settings save.<\/li>\n<\/ul>\n\n1.6.26 (September 15, 2026)<\/h4>\n\n
\n
1.6.25 (September 4, 2026)<\/h4>\n\n
\n
1.6.24 (August 23, 2026)<\/h4>\n\n
\n
1.6.23 (August 15, 2026)<\/h4>\n\n
\n
server\/lumen-cache-proxy.php<\/code>.<\/li>\nHtaccess::deploy_proxy()<\/code> to automatically configure localized ABSPATH definitions upon file deployment.<\/li>\n<\/ul>\n\n1.6.22 (August 15, 2026)<\/h4>\n\n
\n
advanced-cache.php<\/code> is now completely self-contained with compiled configuration snapshot data.<\/li>\n1.6.21 (August 14, 2026)<\/h4>\n\n
\n
1.6.20 (August 11, 2026)<\/h4>\n\n
\n
assets\/css\/admin.css<\/code> to prevent connector lines from overlapping labels.<\/li>\n<\/ul>\n\n1.6.19 (August 11, 2026)<\/h4>\n\n
\n
lumen-cache-proxy.php<\/code> with native PHP casts since the proxy runs pre-bootstrap.<\/li>\nLUMENCACHE_PROXY_ABSPATH<\/code>) for WordPress index.php<\/code> and wp-config.php<\/code> inclusion.<\/li>\n<\/ul>\n\n1.6.18 (August 11, 2026)<\/h4>\n\n
\n
$redis->auth()<\/code> and $redis->select()<\/code> in connect_phpredis()<\/code>.<\/li>\n<\/ul>\n\n1.6.17 (August 11, 2026)<\/h4>\n\n
\n
LUMENCACHE_DEBUG<\/code> check for zero production overhead.<\/li>\n<\/ul>\n\n1.6.16 (August 11, 2026)<\/h4>\n\n
\n
advanced-cache.php<\/code> with native PHP casts and isset checks.<\/li>\nenable_wp_cache()<\/code> string replacement logic for reliable WP_CACHE<\/code> insertion into wp-config.php<\/code>.<\/li>\n<\/ul>\n\n1.6.15 (August 11, 2026)<\/h4>\n\n
\n
Lifecycle::uninstall()<\/code> now flushes all Redis keys before removing plugin files.<\/li>\n1.6.14 (August 11, 2026)<\/h4>\n\n
\n
ABSPATH<\/code> check to all server drop-ins.<\/li>\n