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.

Freemius

cyclonecode

<p>This plugin can be used to customize php settings for you WordPress installation.</p>
<p>The plugin will modify either the <strong>.htaccess</strong> file or <strong>.user.ini</strong> file in order to change the current php settings directly from within the settings page.</p>
<p>Since the configuration file needs to be modified this file <strong>must</strong> be writable for this plugin to work as expected.</p>
<h4>Apache module</h4>
<p>When PHP is running as an Apache module the <strong>.htaccess</strong> file will be used to set customized settings; make sure so that this file <strong>exists</strong> and is <strong>writable</strong> by the webserver.</p>
<h4>CGI/Fast-CGI</h4>
<p>If instead PHP is running in CGI/Fast-CGI mode then a custom INI file will be used. The name of this file depends on the value of <strong>user_ini.filename</strong> in the php configuration, by default it is <strong>.user.ini</strong>.<br />
You can check the name of you custom INI file in the <strong>PHP Information</strong> table. The custom INI file should be placed under the root folder and <strong>most</strong> be <strong>writable</strong> by the webserver.</p>
<p>Notice that there is also a <strong>User INI file cache TTL</strong> value in the information table, this value tells how long the custom INI file will be cached before it gets reloaded.<br />
For instance, if this value is set to 300 then any changes to your custom INI file will not be reflected for up to 5 minutes. The name for this setting in the php configuration is <strong>user_ini.cache_ttl</strong>.</p>
<p>One important thing is to make sure that your <code>.user.ini</code> file is blocked by your webserver. If you are running NGINX this can be done by adding:</p>
<pre><code>location ~ /\.user\.ini {
  deny all;
}
</code></pre>
<p>to your server configuration. The same thing using Apache is done by adding the following to the configuration if not already done:</p>
<pre><code><Files .user.ini>
order allow,deny
deny from all
</Files>
</code></pre>
<h4>Available Settings</h4>
<p>The settings table will display all non-system php settings that can be customized by the plugin. All modified settings will be displayed in red in this table.</p>
<p>Some settings might be displayed in red because they are changed somewhere else, perhaps through a customized php.ini file, by WordPress itself, a plugin or in some other way.<br />
For instance if you have enabled <strong>WP_DEBUG</strong> in your <strong>wp-config.php</strong> file the <strong>error_reporting</strong> setting will turn red.</p>
<p>If you have questions or perhaps some idea on things that should be added you can also try <a href="https://join.slack.com/t/cyclonecode/shared_invite/zt-6bdtbdab-n9QaMLM~exHP19zFDPN~AQ" rel="nofollow ugc">slack</a>.</p>
<h4>Multiple Configurations</h4>
<p>The premium version adds support for creating multiple named configurations which all can hold their own custom PHP settings.<br />
You will then be able to easily switch between the different configurations entries applying them to you configuration file.</p>
<h4>Environment Variables</h4>
<p>In the premium version, when running PHP as an apache module and using an <strong>.htaccess</strong> file for configuration, you are able<br />
to add custom environment variables. These will be accessible by using the super global <strong>$_SERVER</strong> array.<br />
In order for this to work you will need to have the mod_env module enabled in your apache setup.</p>
<h4>Resources</h4>
<p>A complete list of settings that can be modified can be found here: <a href="http://php.net/manual/en/ini.list.php" rel="nofollow ugc">List of php.ini directives</a><br />
Notice that directives marked as <code>PHP_INI_SYSTEM</code> can not be modified.</p>
<h3>Warning</h3>
<p>Make sure you know how a value should be configured and what different settings do before changing anything.<br />
This is important since some settings might render your page inaccessible, depending on what value you are using.<br />
A good example of this is the <strong>variables_order</strong> configuration:</p>
<blockquote>
<p>Sets the order of the EGPCS (Environment, Get, Post, Cookie, and Server) variable parsing. For example, if variables_order is set to “SP” then PHP will create the superglobals $_SERVER and $_POST, but not create $_ENV, $_GET, and $_COOKIE. Setting to “” means no superglobals will be set.</p>
</blockquote>
<p>If this value would be configured to <strong>EPCS</strong> then no <strong>$_GET</strong> superglobal would be set which would make your page inaccessible.</p>
<p>Another example is setting the <strong>post_max_size</strong> to a very low value so that no form data is sent to the server, which in turn would result in that form data is never saved.</p>
<p>If you by mistake changed some value and your site is now inaccessible you could simply manually remove everything from between the plugin markers in your <strong>.htaccess</strong> file:</p>
<pre><code># BEGIN CUSTOM PHP SETTINGS PRO
php_value variables_order EPCS  <-- Remove
# END CUSTOM PHP SETTINGS PRO
</code></pre>
<p>If you are running PHP in CGI/Fast-CGI mode then instead remove everything between the plugins markers in your <strong>.user.ini</strong> file:</p>
<pre><code>; BEGIN CUSTOM PHP SETTINGS
php_value variables_order EPCS  <-- Remove
; END CUSTOM PHP SETTINGS
</code></pre>
<h3>Support</h3>
<p>If you run into any trouble, don’t hesitate to add a new topic under the support section:<br />
<a href="https://wordpress.org/support/plugin/custom-php-settings/" rel="ugc">https://wordpress.org/support/plugin/custom-php-settings/</a></p>
<p>You can also try contacting me on <a href="https://join.slack.com/t/cyclonecode/shared_invite/zt-6bdtbdab-n9QaMLM~exHP19zFDPN~AQ" rel="nofollow ugc">slack</a>.</p>


Custom PHP Settings

Thanks for the awesome plugin. Now I no need to modify the php.ini file manually! Timesaver! Nearly 99% works.

No need to modify the php.ini file manually!

This plugin makes it possible to override php settings.

Cyclone Static vs Custom PHP Settings