| 开发者 | hashtechlogic |
|---|---|
| 更新时间 | 2026年10月5日 01:29 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp-content/cache/cache-clearing/site-{ID}/). Themes and plugins can store data in it through a small developer API. Its size and file count are shown on the dashboard.wp_cache_flush()). If none is active it shows "Not detected".hash-tech-logic-cache-clearing folder to wp-content/plugins/, then activate it on the Plugins screen.
On multisite you can activate the plugin on individual sites or network-activate it. Each site is set up the first time its dashboard is visited.No. It works on its own. Other cache plugins are optional and are only purged if you turn on their integration.
Every module that is available and safe on this site: the plugin cache, transients (according to your setting), the persistent object cache if one is active and allowed, browser cache-busting if you turned it on, and any integrations you enabled. Anything that is not available is listed as "Skipped" with the reason.
At least one cache could not be cleared completely. The result lists each cache with its message, for example a file that could not be deleted because of folder permissions. The plugin never reports success when something failed.
Your site does not use a persistent object cache (an object-cache.php drop-in such as Redis Object Cache). Without one, WordPress keeps cached objects in memory for a single page load only, so there is nothing to flush.
It can. wp_cache_flush() clears the whole object cache. If other sites or apps share the same Redis or Memcached database, their cached data is cleared too. On multisite, flushing is disabled until a network administrator allows it under Settings → Advanced.
Transients are temporary by design and WordPress rebuilds them when needed, so clearing them is safe, but the next few page loads may be slightly slower. That is why the default is "expired transients only". The WP-Cron lock (doing_cron) is never deleted.
No website can delete files stored in a visitor's browser. Instead, turn on browser cache-busting under Settings → Advanced. Clearing it changes the version of your CSS and JavaScript URLs, so browsers download fresh copies.
Not in this version. The scanner detects Cloudflare, CloudFront, Fastly, Sucuri, Bunny CDN, QUIC.cloud and Akamai when they are visible in response headers, and several managed hosts. Clear those caches from their own dashboard. CDN integrations are planned.
Yes. Hover over a published page or post in Pages or Posts and click Clear cache, use the Page Cache box on the edit screen, or choose Clear This Page in the Admin Bar while viewing it. WordPress's own cached data for that post is refreshed, and every connected cache plugin that supports it (WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, WP Fastest Cache, Cache Enabler, SiteGround Speed Optimizer and Nginx Helper) purges only that page. Plugins that can only purge everything (Autoptimize, Elementor CSS files) are left alone and shown as skipped.
It uses WordPress's built-in scheduler (WP-Cron), which runs when someone visits your site. On a quiet site a run can start a little after the chosen time. Each run appears in the activity log as "Scheduled clear".
Only the caches you tick under "Caches to clear automatically". By default that is the plugin cache and transients (expired only), which are cheap to clear. You can add the object cache or integrations, but flushing those after every change can slow your site down until the caches warm up again.
Users with the manage_options capability (administrators). Developers can change this with the cache_clearing_capability filter.
Deleting the plugin removes only its own data: its options (settings, log, statistics, scan results, version, install date, asset version), its scheduled event, the review-request choice saved for each user, its short-lived notices and its own wp-content/cache/cache-clearing/ folder. On multisite this is done for every site. Nothing else is touched. Deactivating the plugin keeps your settings and log.
register_setting(), type "array" and a sanitize callback that validates every field.