kryptonmediagroup

<p>Cyclone Static generates fully-rendered static HTML files for every page on your WordPress site and instructs Apache to serve them directly — bypassing PHP, WordPress, and the database for anonymous visitors.</p>
<p>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 — everything works as it did before, because the static file contains the same HTML WordPress would have generated.</p>
<p>Logged-in users, POST requests, query strings, and administrative paths bypass the static cache and receive live WordPress as normal.</p>
<h4>Key features</h4>
<ul>
<li><strong>Static file serving</strong> — Apache serves files directly from disk. PHP and the database are not involved in serving anonymous page requests.</li>
<li><strong>Automatic regeneration</strong> — When you publish or update a post or page, it is automatically queued for regeneration. You do not need to do anything.</li>
<li><strong>Reduced attack surface</strong> — Static HTML files do not execute PHP or query a database. Common WordPress-targeted attack vectors that require a live PHP process — such as SQL injection via PHP, PHP code execution, and xmlrpc.php abuse — do not apply to anonymous page requests served as static files.</li>
<li><strong>CDN integration</strong> — Works alongside W3 Total Cache. Direct integration with Bunny.net, Cloudflare, KeyCDN, and Amazon CloudFront is available in Cyclone Static Pro.</li>
<li><strong>W3 Total Cache compatible</strong> — Installs its .htaccess rules before W3TC rules. Works alongside or without W3TC.</li>
<li><strong>Non-destructive</strong> — Deactivating the plugin removes the .htaccess rules and WordPress resumes normal operation. Your cached files are not deleted without your explicit consent — a prompt appears when you deactivate, asking whether to keep or delete them.</li>
<li><strong>Free and open</strong> — No license required. Support via the WordPress.org community forums.</li>
</ul>
<h4>System requirements</h4>
<ul>
<li>WordPress 6.0 or later</li>
<li>PHP 8.0 or later</li>
<li><strong>Apache web server</strong> with mod_rewrite enabled</li>
<li>.htaccess support enabled (AllowOverride All or equivalent)</li>
<li>WordPress Multisite is not supported in this version — Multisite support is available in Cyclone Static Pro</li>
</ul>
<p><strong>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 <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Nginx Configuration</strong>.</p>
<h4>CDN support</h4>
<p>The free version works automatically alongside W3 Total Cache — CDN purges are routed through W3TC when it is active.</p>
<p>Direct API integration with Bunny.net, Cloudflare, KeyCDN, and Amazon CloudFront is available in Cyclone Static Pro.</p>
<h4>Privacy</h4>
<p>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>
<h3>Support</h3>
<p>Support is provided via the WordPress.org community forums. Post your question there — 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>
<h3>External Services</h3>
<p>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 <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> CDN Integration</strong> and a purge is triggered. No data is sent to these services unless you explicitly configure them.</p>
<h4>Bunny.net</h4>
<p>Used for CDN cache purging. Your Bunny.net API key and Pull Zone ID are sent to the Bunny.net API.<br />
* Service: https://bunny.net/<br />
* API documentation: https://docs.bunny.net/reference/purgepublicpullzone<br />
* Privacy policy: https://bunny.net/privacy/</p>
<h4>Cloudflare</h4>
<p>Used for CDN cache purging. Your Cloudflare API token and Zone ID are sent to the Cloudflare API.<br />
* Service: https://www.cloudflare.com/<br />
* API documentation: https://developers.cloudflare.com/api/resources/cache/methods/purge/<br />
* Privacy policy: https://www.cloudflare.com/privacypolicy/</p>
<h4>KeyCDN</h4>
<p>Used for CDN cache purging. Your KeyCDN API key and Zone ID are sent to the KeyCDN API.<br />
* Service: https://www.keycdn.com/<br />
* API documentation: https://www.keycdn.com/api<br />
* Privacy policy: https://www.keycdn.com/privacy</p>
<h4>Amazon CloudFront</h4>
<p>Used for CDN cache invalidation. Your AWS Access Key, Secret Key, and CloudFront Distribution ID are sent to the Amazon CloudFront API.<br />
* Service: https://aws.amazon.com/cloudfront/<br />
* API documentation: https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_CreateInvalidation.html<br />
* Privacy policy: https://aws.amazon.com/privacy/</p>


Cyclone Static

Serve static HTML files directly from disk — no PHP, no database queries for anonymous visitors.

Viktor Szépe

<p>“It’s important to make resources (images, scripts, stylesheets, etc.) cacheable.”</p>
<p><a href="http://www.stevesouders.com/blog/2008/08/23/revving-filenames-dont-use-querystring/" rel="nofollow ugc">Steve Souders</a></p>
<p>It is much easier to use a CDN without Query String Parameters.<br />
This plugins alters only local resources’ URL-s.<br />
The <code>ver</code> Query String Parameter will be inserted into the filename.</p>
<p>For example <code>jquery.min.js?ver=1.10</code> becomes <code>jquery.min.110.js</code>.</p>
<p>To reverse this in the web server add this line to your nginx config:</p>
<pre><code>server {
    location ~ ^(.+)\.\d\d+\.(js|css|png|jpg|jpeg|gif|ico)$ {
        #try_files $uri $1.$2 /index.php?$args;
        try_files $uri $1.$2 =404;
    }
}
</code></pre>
<p>Or to your Apache configuration or <code>.htaccess</code> file.</p>
<pre><code>RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.+)\.\d\d+\.(js|css|png|jpg|jpeg|gif|ico)$ $1.$2 [NC,L]
</code></pre>
<h4>Testing the plugin before live usage</h4>
<p>You can test the plugin by replacing the two <code>add_filter()</code> calls with this</p>
<pre><code>require_once( dirname( dirname( dirname( dirname( __FILE__ ) ) ) ) . '/wp-load.php' );
wp();
echo o1_revving_src( $argv[1] ) . PHP_EOL;
</code></pre>
<p>Then start it from CLI: <code>php revving.php <TEST-URL></code></p>
<h4>Links</h4>
<p>Development of this plugin goes on on <a href="https://github.com/szepeviktor/resource-versioning" rel="nofollow ugc">GitHub</a>.</p>


Resource Versioning

Turn Query String Parameters into file revision numbers.

Cyclone Static vs Resource Versioning