وردپرس 118

مخزن داخلی

دریافت وردپرس
ورود/ثبت نام
Cyclone Static

Cyclone Static

توسط

ورود به سیستم برای دانلود
ثبت گزارش خرابی

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.

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.

Logged-in users, POST requests, query strings, and administrative paths bypass the static cache and receive live WordPress as normal.

Key features

  • Static file serving — Apache serves files directly from disk. PHP and the database are not involved in serving anonymous page requests.
  • Automatic regeneration — When you publish or update a post or page, it is automatically queued for regeneration. You do not need to do anything.
  • Reduced attack surface — 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.
  • CDN integration — Works alongside W3 Total Cache. Direct integration with Bunny.net, Cloudflare, KeyCDN, and Amazon CloudFront is available in Cyclone Static Pro.
  • W3 Total Cache compatible — Installs its .htaccess rules before W3TC rules. Works alongside or without W3TC.
  • Non-destructive — 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.
  • Free and open — No license required. Support via the WordPress.org community forums.

System requirements

  • WordPress 6.0 or later
  • PHP 8.0 or later
  • Apache web server with mod_rewrite enabled
  • .htaccess support enabled (AllowOverride All or equivalent)
  • WordPress Multisite is not supported in this version — Multisite support is available in Cyclone Static Pro

Nginx users: 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 Nginx Configuration.

CDN support

The free version works automatically alongside W3 Total Cache — CDN purges are routed through W3TC when it is active.

Direct API integration with Bunny.net, Cloudflare, KeyCDN, and Amazon CloudFront is available in Cyclone Static Pro.

Privacy

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.

Support

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.

External Services

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 CDN Integration and a purge is triggered. No data is sent to these services unless you explicitly configure them.

Bunny.net

Used for CDN cache purging. Your Bunny.net API key and Pull Zone ID are sent to the Bunny.net API.
* Service: https://bunny.net/
* API documentation: https://docs.bunny.net/reference/purgepublicpullzone
* Privacy policy: https://bunny.net/privacy/

Cloudflare

Used for CDN cache purging. Your Cloudflare API token and Zone ID are sent to the Cloudflare API.
* Service: https://www.cloudflare.com/
* API documentation: https://developers.cloudflare.com/api/resources/cache/methods/purge/
* Privacy policy: https://www.cloudflare.com/privacypolicy/

KeyCDN

Used for CDN cache purging. Your KeyCDN API key and Zone ID are sent to the KeyCDN API.
* Service: https://www.keycdn.com/
* API documentation: https://www.keycdn.com/api
* Privacy policy: https://www.keycdn.com/privacy

Amazon CloudFront

Used for CDN cache invalidation. Your AWS Access Key, Secret Key, and CloudFront Distribution ID are sent to the Amazon CloudFront API.
* Service: https://aws.amazon.com/cloudfront/
* API documentation: https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_CreateInvalidation.html
* Privacy policy: https://aws.amazon.com/privacy/

  1. Upload cyclone-static.zip via Plugins Add New Upload Plugin
  2. Activate the plugin
  3. Go to Cyclone Static Dashboard
  4. Confirm .htaccess Rules shows ✓ Installed in the System Info panel
  5. Click Discover from Sitemap to queue all pages for initial generation
  6. Monitor the Queue Depth stat card until generation is complete

Initial generation time

At default settings (2 pages every 60 seconds), a 4,000-page site takes several hours for initial full generation. Increase Batch Size in Settings to speed this up on servers with capacity to spare.

After initial generation, the cache maintains itself automatically as you publish and update content.

سوالات متداول

Does this work with page builders like Divi and Extra?

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.

Does this break my admin or editor experience?

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.

What happens if I deactivate the plugin?

Deactivation removes the Cyclone Static block from .htaccess — Apache falls through to WordPress for all requests. A prompt appears asking what to do with your cached files: Keep cache files (recommended if you plan to reactivate — files are served again immediately upon reactivation) or Delete cache files (removes them from disk now). If you dismiss the prompt without choosing, your files are kept.

What happens if I delete the plugin?

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 when you deactivated — if you chose to keep them or never saw the prompt, they remain on disk at their original location.

Does it work with W3 Total Cache?

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.

Can I remove W3 Total Cache if I install Cyclone Static?

Yes, but you must follow the safe removal procedure. See the Removing W3 Total Cache guide in the collapsible section on the Cyclone Settings page. Removing W3TC without preparation can break your site’s styles and scripts.

Does it work with Cloudflare?

The free version works behind Cloudflare without any special configuration — 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.

Does it work with Nginx?

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 Nginx Configuration. Copy that snippet into your site’s server block before the location block that passes requests to PHP-FPM.

Does it support Brotli compression?

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 — Brotli first, then gzip, then uncompressed. If php-brotli is not installed, gzip and uncompressed files are generated as normal with no configuration required.

What happens to cached pages when a comment is posted?

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 — the page is only updated when the comment transitions to approved status.

What is the disk space requirement?

It depends on the complexity of your pages. A typical WordPress page generates a static file of 50–300 KB. A 4,000-page site would require roughly 200 MB – 1.2 GB. Cyclone Static displays your current cache size and available disk space on the Dashboard.

Does it support WooCommerce?

Cyclone Static can run on WooCommerce sites with manual configuration. Add /cart/, /checkout/, /my-account/, and /wc-api/ to the exclusions list under Settings Exclusions — 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.

Does it support WordPress Multisite?

No. Multisite support is available in Cyclone Static Pro, distributed from kryptonmediagroup.com/cyclone-static.

تصویری برای این آیتم موجود نیست.
نظری برای این آیتم موجود نیست.
0 0 رای ها
امتیازدهی
اشتراک در
اطلاع از
0 نظرات
قدیمی‌ترین
تازه‌ترین بیشترین رأی
هیچ نسخه‌ای برای این آیتم موجود نیست.
بدون امتیاز

قیمت:

رایگان

نگارش

آخرین انتشار

20 خرداد 1405

آخرین بروزرسانی

2 ماه پیش

نصب های فعال

-

نگارش وردپرس

وردپرس 6.0+

تست شده از نسخه

وردپرس 6.9.4

نگارش PHP

PHP 8.0+

تگ ها

نسخه ها

0 نسخه

نیاز به پشتیبانی دارید ؟

کارشناسان ما آماده پاسخگویی هستند

افزونه های مرتبط