| 开发者 | stachredeker |
|---|---|
| 更新时间 | 2026年9月29日 21:34 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
wp-content/uploads/elementor/css/). Since Elementor 3.33 it deletes all of those files whenever a plugin is activated, deactivated or updated, when you switch themes, and when you use Elementor → Tools → Clear Files & Data (and after some of its own updates and settings changes). Elementor builds the files again the next time a page is generated.
W3 Total Cache, however, keeps serving the saved copies of your pages. Those copies still point at the CSS files that were just deleted, so visitors get pages without styling until someone clears the cache by hand.
This plugin notices when Elementor deletes its CSS files and purges the page cache right after. Then it visits your home page once in the background, so Elementor rebuilds its CSS and W3 Total Cache stores a fresh copy. Two minutes later it purges once more, to catch a page that a visitor happened to get cached in the meantime.
You do not need Elementor to use this plugin. Without Elementor it simply purges after updates, (de)activations and theme switches.
Only the page cache
By default the plugin purges only the page cache (W3 Total Cache's "Purge All Caches" is not used). That is all that is needed to fix outdated pages. "Purge All Caches" also empties the object, database and minify caches, and it makes Elementor delete its CSS files once more. If you want it anyway, see the FAQ.
For developers
acfw3tc_flush_scope (filter): 'page' (default) or 'all' (W3 Total Cache's "Purge All Caches").acfw3tc_enable_warmup (filter): return false to skip the background visit to your home page.acfw3tc_triggers (filter): the list of triggers that lead to a purge. Default: upgrade, translation, core_updated, plugin_activated, plugin_deactivated, theme_switched, elementor_css_cleared.acfw3tc_purged (action): fires after the plugin asked W3 Total Cache to purge, with the reasons, scope, W3 Total Cache function and phase (immediate or followup).add_filter( 'acfw3tc_flush_scope', function () { return 'all'; } );
Privacy notices
This plugin does not:
No. Without Elementor it purges the page cache after updates, plugin (de)activation and theme switches. With Elementor it also purges whenever Elementor deletes its generated CSS files.
Yes. It purges the cache of the site on which something changed. W3 Total Cache's functions work per site.
While your site is changing, a visitor may be served a page that was generated at just the wrong moment, and W3 Total Cache stores that page. The second purge removes it. This uses WP-Cron, which runs when someone visits a page that is not served from the cache (W3 Total Cache's cached pages do not start WP-Cron). On a quiet site it may therefore run a bit later than two minutes. If you run WP-Cron from a real server cron job, it runs on time.
Right after the purge, the plugin loads your home page twice in the background (once normally, once with ?acfw3tc-warmup=1). This makes Elementor rebuild its CSS files straight away and lets W3 Total Cache store a fresh copy. You will see these visits in your server log with the user agent ACF-W3TC-Warmup. The requests do not wait for an answer. You can switch them off with the acfw3tc_enable_warmup filter.
Yes. New translations change text on your pages, so a purge is useful, and version 1 of this plugin did the same. Only the page cache is purged, which is cheap. If you do not want this, remove translation with the acfw3tc_triggers filter. (Elementor itself deletes its CSS on translation updates too, unless its "Optimized CSS files" feature is on; that is always caught.)
No, W3 Total Cache already does that itself for the page you saved.
acfw3tc_flush_scope filter to get the old behaviour.console.log script into the update screen.acfw3tc_flush_scope, acfw3tc_enable_warmup, acfw3tc_triggers, action acfw3tc_purged.