Minor fix. Changing Settings \u2192 Reading now automatically triggers cache regeneration. No manual action required after upgrading.<\/p>","1.1.36":"
Fix for sites using a static front page with a separate Posts Page: post changes now correctly re-queue and regenerate the Posts Page. No manual action required.<\/p>","1.1.35":"
Important fix. Resolves a redirect loop bug ( Important fix. Resolves a mod_rewrite recursion loop on certain hosting configurations and adds explicit Cache-Control headers so CDNs (Cloudflare, CloudFront, Fastly, etc.) cache correctly. Upgrade is applied automatically on the first request after update; purge your CDN cache after upgrading.<\/p>","1.1.33":" Important fix. Resolves a regression where browsers could receive corrupted compressed content (ERR_CONTENT_DECODING_FAILED), appearing as blank pages or unreadable content on hosts that enable mod_brotli globally. Upgrade is applied automatically on the first request after update; remember to purge any CDN cache in front of the site.<\/p>","1.1.32":" Important fix. Resolves a regression where mobile browsers received cached pages as a "download.tgz" archive instead of rendering them. Upgrade is applied automatically on the first request after update; remember to purge any CDN cache in front of the site.<\/p>","1.1.31":" Important fix. Restores serving of pre-compressed (.gz \/ .br) cached pages on Apache configurations whose defaults deny access under wp-content. Upgrade is applied automatically on the first request after update.<\/p>","1.1.28":" Recommended update. Adds a deactivation prompt so your cache is not silently deleted. Fixes a fatal error on the Settings page.<\/p>","1.1.27":" Maintenance update for WordPress.org compatibility. Removes all feature gates and upgrade prompts \u2014 the plugin is now fully functional with no restrictions. Fixes inline script placement and adds required external services disclosure.<\/p>","1.1.26":" Security update. Fixes missing output escaping in the admin dashboard and pages list, and a missing wp_unslash() call on a POST field. All issues are admin-only. Update recommended for all users.<\/p>","1.1.20":" Adds Amazon CloudFront CDN support and WordPress Multisite support (available in Cyclone Static Pro). Also adds a configurable throttle delay to reduce server load during cache generation.<\/p>","1.1.2":" Recommended update. Improves .htaccess resilience \u2014 the Cyclone block now restores itself automatically if the .htaccess file is deleted and regenerated.<\/p>","1.1.1":" Recommended update. Adds pre-compressed gzip delivery for faster page loads.<\/p>","1.1.0":" Important fix. Resolves REST API 404 errors that could break post saving and other WordPress editor functions when Cyclone Static was active.<\/p>"},"ratings":[],"assets_icons":{"icon.svg":{"filename":"icon.svg","revision":3552549,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-772x250.jpg":{"filename":"banner-772x250.jpg","revision":3552549,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.1.38"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Dashboard \u2014 status, statistics, and action buttons","2":"Posts & Pages list \u2014 cache status for every post and page","3":"Settings \u2014 background processing, exclusions, and advanced options"}},"plugin_section":[],"plugin_tags":[2436,146,247,794,17693],"plugin_category":[52,54],"plugin_contributors":[264828],"plugin_business_model":[],"class_list":["post-293491","plugin","type-plugin","status-publish","hentry","plugin_tags-apache","plugin_tags-cache","plugin_tags-performance","plugin_tags-speed","plugin_tags-static","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_contributors-kryptonmediagroup","plugin_committers-kryptonmediagroup"],"banners":{"banner":"https:\/\/ps.w.org\/cyclone-static\/assets\/banner-772x250.jpg?rev=3552549","banner_2x":false,"banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/cyclone-static\/assets\/icon.svg?rev=3552549","icon":"https:\/\/ps.w.org\/cyclone-static\/assets\/icon.svg?rev=3552549","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"\n Cyclone Static generates fully-rendered static HTML files for every page on your WordPress site and instructs Apache to serve them directly \u2014 bypassing PHP, WordPress, and the database for anonymous visitors.<\/p>\n\n When a static file exists for a requested URL, Apache reads it from disk and sends it without starting PHP or querying the database. The visitor receives a complete HTML page. Their browser runs your JavaScript, plays your audio, renders your animations \u2014 everything works as it did before, because the static file contains the same HTML WordPress would have generated.<\/p>\n\n Logged-in users, POST requests, query strings, and administrative paths bypass the static cache and receive live WordPress as normal.<\/p>\n\n Nginx users:<\/strong> Cyclone Static manages .htaccess automatically on Apache. If your server runs Nginx, the Settings page includes a ready-to-paste Nginx server block under Settings \u2192 Nginx Configuration<\/strong>.<\/p>\n\n The free version works automatically alongside W3 Total Cache \u2014 CDN purges are routed through W3TC when it is active.<\/p>\n\n Direct API integration with Bunny.net, Cloudflare, KeyCDN, and Amazon CloudFront is available in Cyclone Static Pro.<\/p>\n\n Cyclone Static does not collect, transmit, or store any personal data. The queue table stores only URLs. No external service is contacted except the CDN purge APIs you explicitly configure.<\/p>\n\n Support is provided via the WordPress.org community forums. Post your question there \u2014 answers are public, so search first as your question may already be answered. For private inquiries, you can reach us at support@kryptonmediagroup.com. Confirmed bugs are addressed through plugin updates. Private one-on-one support is not offered via the forums.<\/p>\n\n Cyclone Static can optionally connect to the following third-party services to purge cached content from your CDN. These connections are only made when you configure a CDN provider under Settings \u2192 CDN Integration<\/strong> and a purge is triggered. No data is sent to these services unless you explicitly configure them.<\/p>\n\n Used for CDN cache purging. Your Bunny.net API key and Pull Zone ID are sent to the Bunny.net API.\n* Service: https:\/\/bunny.net\/\n* API documentation: https:\/\/docs.bunny.net\/reference\/purgepublicpullzone\n* Privacy policy: https:\/\/bunny.net\/privacy\/<\/p>\n\n Used for CDN cache purging. Your Cloudflare API token and Zone ID are sent to the Cloudflare API.\n* Service: https:\/\/www.cloudflare.com\/\n* API documentation: https:\/\/developers.cloudflare.com\/api\/resources\/cache\/methods\/purge\/\n* Privacy policy: https:\/\/www.cloudflare.com\/privacypolicy\/<\/p>\n\n Used for CDN cache purging. Your KeyCDN API key and Zone ID are sent to the KeyCDN API.\n* Service: https:\/\/www.keycdn.com\/\n* API documentation: https:\/\/www.keycdn.com\/api\n* Privacy policy: https:\/\/www.keycdn.com\/privacy<\/p>\n\n Used for CDN cache invalidation. Your AWS Access Key, Secret Key, and CloudFront Distribution ID are sent to the Amazon CloudFront API.\n* Service: https:\/\/aws.amazon.com\/cloudfront\/\n* API documentation: https:\/\/docs.aws.amazon.com\/cloudfront\/latest\/APIReference\/API_CreateInvalidation.html\n* Privacy policy: https:\/\/aws.amazon.com\/privacy\/<\/p>\n\n\n At default settings (2 pages every 60 seconds), a 4,000-page site takes several hours for initial full generation. Increase Batch Size<\/strong> in Settings to speed this up on servers with capacity to spare.<\/p>\n\n After initial generation, the cache maintains itself automatically as you publish and update content.<\/p>\n\n\n Yes. Cyclone Static captures the fully-rendered HTML output of each page as WordPress and your page builder produce it, including all JavaScript and CSS references. The static file closely matches what a live WordPress request would produce.<\/p><\/dd>\n No. Logged-in users bypass the static cache and receive live WordPress. Divi's visual builder, preview functions, and WordPress admin features work as before.<\/p><\/dd>\n Deactivation removes the Cyclone Static block from .htaccess \u2014 Apache falls through to WordPress for all requests. A prompt appears asking what to do with your cached files: Keep cache files<\/strong> (recommended if you plan to reactivate \u2014 files are served again immediately upon reactivation) or Delete cache files<\/strong> (removes them from disk now). If you dismiss the prompt without choosing, your files are kept.<\/p><\/dd>\n Deleting the plugin removes the .htaccess rules, drops the queue database table, and removes plugin settings. Your cached files are only deleted if you chose Delete cache files<\/strong> when you deactivated \u2014 if you chose to keep them or never saw the prompt, they remain on disk at their original location.<\/p><\/dd>\n Yes. Cyclone Static installs its .htaccess rules before W3TC rules, so static files are served by Apache before W3TC is consulted. CDN purges are routed through W3TC automatically when it is active.<\/p><\/dd>\n Yes, but you must follow the safe removal procedure. See the Removing W3 Total Cache<\/strong> guide in the collapsible section on the Cyclone Settings page. Removing W3TC without preparation can break your site's styles and scripts.<\/p><\/dd>\n The free version works behind Cloudflare without any special configuration \u2014 Cloudflare will cache and serve your static files as normal, and its CDN cache will refresh as files expire or are manually purged from the Cloudflare dashboard. Direct Cloudflare cache purging via API is available in Cyclone Static Pro.<\/p><\/dd>\n Yes, with manual configuration. Cyclone Static manages .htaccess automatically on Apache but cannot write Nginx config files. The Settings page includes a ready-to-paste Nginx server block under Settings \u2192 Nginx Configuration<\/strong>. Copy that snippet into your site's server block before the location block that passes requests to PHP-FPM.<\/p><\/dd>\n Yes, when the php-brotli extension is installed on your server. Cyclone Static automatically generates a pre-compressed index.html.br alongside the standard index.html.gz for every cached page. Apache serves the best variant the browser supports \u2014 Brotli first, then gzip, then uncompressed. If php-brotli is not installed, gzip and uncompressed files are generated as normal with no configuration required.<\/p><\/dd>\n When a new comment is posted and approved, Cyclone Static automatically re-queues the parent post for regeneration so the cached page reflects the updated comment count and list. Comments awaiting moderation do not trigger a regeneration \u2014 the page is only updated when the comment transitions to approved status.<\/p><\/dd>\n It depends on the complexity of your pages. A typical WordPress page generates a static file of 50\u2013300 KB. A 4,000-page site would require roughly 200 MB \u2013 1.2 GB. Cyclone Static displays your current cache size and available disk space on the Dashboard.<\/p><\/dd>\n Cyclone Static can run on WooCommerce sites with manual configuration. Add \/cart\/, \/checkout\/, \/my-account\/, and \/wc-api\/ to the exclusions list under Settings \u2192 Exclusions<\/strong> \u2014 this prevents session-sensitive pages from being cached. Product pages cache and serve correctly for anonymous visitors; Add to Cart functions normally via WooCommerce's AJAX handling. Stock level display may lag until pages regenerate.<\/p><\/dd>\n No. Multisite support is available in Cyclone Static Pro, distributed from kryptonmediagroup.com\/cyclone-static.<\/p><\/dd>\n\n<\/dl>\n\n\n[L]<\/code> vs [END]<\/code> on cache-serving RewriteRules) that caused Apache to log AH00124 internal-redirect errors at high volume. Upgrade is applied automatically on the first request after update.<\/p>","1.1.34":"Key features<\/h4>\n\n
\n
System requirements<\/h4>\n\n
\n
CDN support<\/h4>\n\n
Privacy<\/h4>\n\n
Support<\/h3>\n\n
External Services<\/h3>\n\n
Bunny.net<\/h4>\n\n
Cloudflare<\/h4>\n\n
KeyCDN<\/h4>\n\n
Amazon CloudFront<\/h4>\n\n
\n
cyclone-static.zip<\/code> via Plugins \u2192 Add New \u2192 Upload Plugin<\/strong><\/li>\nInitial generation time<\/h4>\n\n
\n
Does this work with page builders like Divi and Extra?<\/h3><\/dt>\n
Does this break my admin or editor experience?<\/h3><\/dt>\n
What happens if I deactivate the plugin?<\/h3><\/dt>\n
What happens if I delete the plugin?<\/h3><\/dt>\n
Does it work with W3 Total Cache?<\/h3><\/dt>\n
Can I remove W3 Total Cache if I install Cyclone Static?<\/h3><\/dt>\n
Does it work with Cloudflare?<\/h3><\/dt>\n
Does it work with Nginx?<\/h3><\/dt>\n
Does it support Brotli compression?<\/h3><\/dt>\n
What happens to cached pages when a comment is posted?<\/h3><\/dt>\n
What is the disk space requirement?<\/h3><\/dt>\n
Does it support WooCommerce?<\/h3><\/dt>\n
Does it support WordPress Multisite?<\/h3><\/dt>\n
1.1.38<\/h4>\n\n
\n
1.1.37<\/h4>\n\n
\n
1.1.36<\/h4>\n\n
\n
1.1.35<\/h4>\n\n
\n
[END]<\/code> flag instead of [L]<\/code>. The [L]<\/code> flag ends the current rewrite pass but restarts the engine with the new URL, allowing the WordPress block to match the internal cache-file path and enter a redirect loop. [END]<\/code> terminates all rewrite processing unconditionally, preventing the loop entirely. Sites with high traffic could accumulate tens of thousands of AH00124 errors per day in the Apache error log.<\/li>\n<\/ul>\n\n1.1.34<\/h4>\n\n
\n
public, max-age=31536000, immutable<\/code>; the plain-HTML fallback receives public, max-age=3600<\/code>. Existing users: purge your CDN cache after upgrading.<\/li>\n<\/ul>\n\n1.1.33<\/h4>\n\n
\n
Accept-Encoding: br<\/code>, producing a corrupted body that browsers reject with ERR_CONTENT_DECODING_FAILED (blank pages or raw compressed bytes rendered as text). The cache directory's .htaccess now declares Content-Encoding via AddEncoding<\/code> in mod_mime's type_checker phase, which runs before the output filter chain so mod_brotli correctly detects the encoding and skips re-compression. Upgrading installs are migrated automatically on the next request. Remember to purge any CDN cache in front of the site after the upgrade \u2014 edge caches may have pinned the bad responses.<\/li>\n<\/ul>\n\n1.1.32<\/h4>\n\n
\n
1.1.31<\/h4>\n\n
\n
1.1.30<\/h4>\n\n
\n
1.1.29<\/h4>\n\n
\n
<script><\/code> in deactivation modal moved to wp_add_inline_script() per WP.org coding standards<\/li>\n1.1.28<\/h4>\n\n
\n
1.1.27<\/h4>\n\n
\n
<script><\/code> blocks in settings view moved to wp_add_inline_script() per WP.org coding standards<\/li>\n1.1.26<\/h4>\n\n
\n
1.1.20<\/h4>\n\n
\n
1.1.6<\/h4>\n\n
\n
1.1.5<\/h4>\n\n
\n
1.1.4<\/h4>\n\n
\n
1.1.3<\/h4>\n\n
\n
1.1.2<\/h4>\n\n
\n
1.1.1<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n