| 开发者 |
jumedeenkhan
mozedia |
|---|---|
| 更新时间 | 2026年9月15日 00:27 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/cart/ or /checkout/, with wildcard support.Yes. The plugin uses a Cloudflare Cache Rule for full-page caching, which is available on the Free plan, and it's also works with Cloudflare premium plans.
No. The plugin creates, updates, and removes its own Cache Rule automatically as needed — including when you disable Full-Page Caching, disconnect, or change the connected domain.
It comes back automatically the next time you save any setting on the plugin's Settings page, as long as Full-Page Caching is still turned on.
No. The plugin only ever creates, updates, or removes the single rule it manages, identified by its own description. Any other rules on the zone are left exactly as they are, in their original order.
No. Logged-in users, comment authors, and password-protected pages are bypassed at Cloudflare's edge.
No. Normal content updates use selective purging so unaffected cached pages stay in the cache. A full purge only happens after a theme/plugin update or when you trigger it manually.
Yes — Cache Exclude URLs, Exclude by Page Type (front page, archives, search, 404s, feeds, AMP, and more), and cookie/query-parameter exclusions are all available on the Cache Settings tab.
Yes, from the Optimization tab, without needing to log into the Cloudflare dashboard.
An API Token is recommended because it can be scoped to only the permissions the plugin needs. A Global API Key also works.
No — Cloudflare's edge is your full-page cache once this plugin is active, so a separate origin-level page cache is redundant and best turned off. An object cache (like Redis Object Cache) for database queries is unrelated and fine to keep running.
Yes. Credentials are stored in your site's own database like any other WordPress setting, are never exposed on the front end, and are only sent to Cloudflare's API over HTTPS.
Yes. Use the Exclude Cookies setting to bypass cart/session cookies (e.g. woocommerce_*) so carts, checkouts, and account pages are never served from cache.
The plugin fails safely: it never overwrites or removes existing Cache Rules on a failed or unconfirmed API response, and your site keeps working normally either way.
Deactivating removes the managed Cache Rule from Cloudflare so caching stops immediately. Reactivating recreates it right away if you're already connected, and takes you back to Settings; otherwise it opens the Setup Wizard.