[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fAYnJDS25nm4KmTz5X_vu5KxyIf2GT49VxlNe42RLbtc":3,"$fqbXAHdsqYKMVeI--py8T14r2cifYwithIWD4Z3TpJMQ":128,"$f62sOd8PUnlXNnFpP9frwg9J-sHJ-4uecl7JVo6NXkZY":133},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"discovery_status":29,"vulnerabilities":30,"developer":31,"crawl_stats":27,"alternatives":37,"analysis":27,"fingerprints":27},"lookit-cache-purge-for-sucuri","Lookit Cache Purge for Sucuri","1.0.0","lookitdesign","https:\u002F\u002Fprofiles.wordpress.org\u002Flookitdesign\u002F","\u003Cp>Sucuri’s Website Firewall caches your pages on its global edge network. That caching makes your site fast, but it also means that when you update a page, visitors may continue to see the old version for up to 2 minutes — or longer.\u003C\u002Fp>\n\u003Cp>Sucuri’s dashboard has a “Clear Cache – Per File” feature that lets you purge a single URL from the edge cache. But to use it, you have to leave WordPress, log into the Sucuri WAF dashboard, navigate to Performance, and paste the path manually. Meanwhile, tools like WP Rocket’s Sucuri add-on only support full-site cache clearing — the nuclear option.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Lookit® Cache Purge for Sucuri fills this gap.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>A clean “🛡 Sucuri Cache Purge” menu appears in your WordPress admin bar with two options:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Purge This URL\u003C\u002Fstrong> — clears only the page you are currently editing or viewing\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Purge Entire Site\u003C\u002Fstrong> — full cache purge when you need it (with a confirmation dialog)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The plugin uses Sucuri’s documented Website Firewall API. It does not touch any other Sucuri settings — no WAF rules, no SSL, no security options. Cache purge only.\u003C\u002Fp>\n\u003Ch4>Why This Plugin Exists\u003C\u002Fh4>\n\u003Cp>Sucuri’s own dashboard can clear a single URL, but there’s no easy way to do it from inside WordPress while you’re editing content. WP Rocket’s Sucuri add-on only offers full-site purging. The official Sucuri WordPress plugin is a security tool, not a cache-clearing tool. This plugin does exactly one thing: give you a button in the WordPress admin bar to purge a URL from Sucuri’s edge cache — without leaving the editor.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Context-aware: automatically detects the URL of the post or page you are editing or viewing\u003C\u002Fli>\n\u003Cli>Works in both wp-admin (post editor) and on the frontend (when logged in as an administrator)\u003C\u002Fli>\n\u003Cli>Full-site purge option with confirmation dialog\u003C\u002Fli>\n\u003Cli>Built-in rate limiting: 6 purges per minute per user, to prevent accidental hammering\u003C\u002Fli>\n\u003Cli>Handles Sucuri’s API rate limit (HTTP 429) gracefully, with clear retry-wait messages\u003C\u002Fli>\n\u003Cli>Lightweight — no zone settings, no DNS, no security toggles, no bloat\u003C\u002Fli>\n\u003Cli>Secure — uses Sucuri’s documented API with a scoped API Key\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>A Sucuri Website Firewall (WAF) account with your site connected\u003C\u002Fli>\n\u003Cli>The “API Key (for plugin)” value from your Sucuri dashboard \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> API \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> API Details\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Setup\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Install and activate the plugin\u003C\u002Fli>\n\u003Cli>Go to \u003Cstrong>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Sucuri Cache Purge\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Paste your Sucuri “API Key (for plugin)” — it looks like \u003Ccode>32characters\u002F32characters\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Save. The \u003Cstrong>🛡 Sucuri Cache Purge\u003C\u002Fstrong> menu will now appear in your admin bar\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Important: Static Files Cache Differently\u003C\u002Fh4>\n\u003Cp>Sucuri caches static files — images, CSS, JS, PDFs, fonts — on its edge network for up to 72 hours, regardless of per-URL purging. If you update a stylesheet or an image, a per-URL purge will not be enough. Use “Purge Entire Site” instead, or use versioning (\u003Ccode>?ver=1.2.3\u003C\u002Fcode>) to force browsers to fetch the new version.\u003C\u002Fp>\n\u003Ch4>Important: 2-Minute Propagation\u003C\u002Fh4>\n\u003Cp>After a successful purge, Sucuri takes up to 2 minutes to fully flush the cache across its global edge network. If you do not see your change immediately, wait two minutes and reload. This is normal Sucuri behavior, not a plugin issue.\u003C\u002Fp>\n\u003Ch4>Documentation and Support\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Full documentation: https:\u002F\u002Flookitdesign.com\u002Fsoftware\u002Fsucuri-cache-purge\u002F\u003C\u002Fli>\n\u003Cli>Support: https:\u002F\u002Flookitdesign.com\u002Fsucuri-purge-support-form\u002F\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cem>Lookit® is a registered trademark of ZENOVA CORP. Sucuri is a trademark of its respective owner (a GoDaddy brand); this plugin is an independent integration and is not affiliated with, sponsored by, or endorsed by Sucuri.\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch3>External Services\u003C\u002Fh3>\n\u003Cp>This plugin connects to the Sucuri Website Firewall (WAF) API to purge cached pages from Sucuri’s global edge network. This connection is required for the plugin’s core function — without it, no cache purging can occur.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What the service is used for:\u003C\u002Fstrong>\u003Cbr \u002F>\nWhen you trigger a purge (a single URL or the entire site), the plugin sends a request to Sucuri’s WAF API asking it to clear the relevant cache.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What data is sent, and when:\u003C\u002Fstrong>\u003Cbr \u002F>\nA request is sent to Sucuri only when you click “Purge This URL” or “Purge Entire Site” in the admin bar. Each request includes:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Your Sucuri API Key and API Secret (the combined “API Key (for plugin)” value you enter in the plugin settings), used to authenticate the request\u003C\u002Fli>\n\u003Cli>For a single-URL purge: the path of the page being purged (for example, \u003Ccode>\u002Fabout\u002F\u003C\u002Fcode>)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>No data about your site’s visitors is collected or transmitted. The plugin does not send any personally identifiable information (PII).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Service endpoint:\u003C\u002Fstrong> https:\u002F\u002Fwaf.sucuri.net\u002Fapi?v2\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Service provider:\u003C\u002Fstrong> Sucuri (GoDaddy Media Temple, Inc. d\u002Fb\u002Fa Sucuri)\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Terms of Service: https:\u002F\u002Fsucuri.net\u002Fterms\u002F\u003C\u002Fli>\n\u003Cli>Privacy Policy: https:\u002F\u002Fsucuri.net\u002Fprivacy\u002F\u003C\u002Fli>\n\u003C\u002Ful>\n","Granular Sucuri cache purge from the WordPress admin bar. Purge a single URL, or the entire site, without leaving wp-admin.",10,91,0,"2026-07-14T03:32:00.000Z","7.0.2","5.9","7.4",[19,20,21,22,23],"admin-bar","cache","purge","sucuri","waf","https:\u002F\u002Flookitdesign.com\u002Fsoftware\u002Fsucuri-cache-purge\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flookit-cache-purge-for-sucuri.1.0.0.zip",100,null,"2026-07-22T17:31:50.256Z","no_bundle",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":26,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},2,40,30,94,"2026-08-29T06:40:26.219Z",[38,50,74,94,111],{"slug":39,"name":40,"version":6,"author":7,"author_profile":8,"description":41,"short_description":42,"active_installs":34,"downloaded":43,"rating":13,"num_ratings":13,"last_updated":44,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":45,"homepage":48,"download_link":49,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"lookit-cf-purge","Lookit Cloudflare Cache Purge","\u003Cp>Most Cloudflare integrations for WordPress give you only one option: purge everything. That is the nuclear option, and it is more expensive than it looks.\u003C\u002Fp>\n\u003Ch4>What happens when you purge everything\u003C\u002Fh4>\n\u003Cp>When you purge the entire cache in Cloudflare, every cached page is cleared at once — but Cloudflare does not rebuild those caches for you. A page is only re-cached \u003Cem>after\u003C\u002Fem> the next time someone requests it. That first request following a purge is a cache miss: it travels all the way back to your origin server, which is slow to render, and that visitor waits for the full render. Only the \u003Cem>next\u003C\u002Fem> visitor to the same page gets the fast, cached copy.\u003C\u002Fp>\n\u003Cp>The catch is traffic. Busy pages re-cache almost immediately. But pages that are visited infrequently can sit uncached for hours or even days, and the first person to land on each one pays the slow-render penalty. There is no way inside Cloudflare to warm the cache ahead of time or speed this up — re-caching happens only on demand, page by page, as real traffic trickles in.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Lookit® Cloudflare Cache Purge gives you granular control.\u003C\u002Fstrong> Instead of wiping everything and forcing your whole site back to origin speed, you clear only the page you actually changed — and every other page keeps its cache intact.\u003C\u002Fp>\n\u003Cp>From any page in WordPress — whether you are editing a post in wp-admin or viewing the live site while logged in — a lightweight \u003Cstrong>CF Purge\u003C\u002Fstrong> menu (☁) appears in the admin bar with three options:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Purge This URL\u003C\u002Fstrong> — clears only the page you are currently on or editing\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Purge Entire Site\u003C\u002Fstrong> — full cache purge when you genuinely need it (with a confirmation dialog so it is never accidental)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Or enter any URL\u003C\u002Fstrong> — type any URL on the site and purge it directly, without navigating to that page first\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The manual URL field is especially useful for URLs that do not correspond to a standard WordPress post or page — such as custom archive paths, Events Calendar URLs, or other custom post type archives.\u003C\u002Fp>\n\u003Ch4>Why this plugin exists\u003C\u002Fh4>\n\u003Cp>If you manage WordPress sites on Cloudflare with a caching plugin like WP Rocket, you have likely run into this problem: WP Rocket’s Cloudflare integration only supports full-site purge. The official Cloudflare WordPress plugin is heavyweight and touches your zone settings. Neither gives you a simple, context-aware button to clear just one URL.\u003C\u002Fp>\n\u003Cp>This plugin does exactly that — nothing more, nothing less. It connects to Cloudflare via a scoped API token, adds a clean menu to the admin bar, and stays completely out of your Cloudflare zone configuration.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Context-aware: automatically detects the URL of the post or page you are editing or viewing\u003C\u002Fli>\n\u003Cli>Works in both the wp-admin editor and the frontend (when logged in)\u003C\u002Fli>\n\u003Cli>Manual URL field for purging arbitrary URLs without navigating to them\u003C\u002Fli>\n\u003Cli>Full-site purge option with confirmation dialog\u003C\u002Fli>\n\u003Cli>Lightweight — no zone settings, no DNS, no SSL toggles, no bloat\u003C\u002Fli>\n\u003Cli>Secure — uses a scoped API token with minimum required permissions\u003C\u002Fli>\n\u003Cli>Compatible with WP Rocket, the official Cloudflare plugin, and any other caching setup\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>A Cloudflare account with your site’s domain active\u003C\u002Fli>\n\u003Cli>A Cloudflare API Token with \u003Cstrong>Zone \u002F Cache Purge \u002F Purge\u003C\u002Fstrong> and \u003Cstrong>Zone \u002F Zone \u002F Read\u003C\u002Fstrong> permissions\u003C\u002Fli>\n\u003Cli>Your Cloudflare Zone ID (found on the domain’s Overview page in the Cloudflare dashboard)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Setup\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Install and activate the plugin\u003C\u002Fli>\n\u003Cli>Go to \u003Cstrong>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> CF Purge Settings\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Paste your Cloudflare API Token and Zone ID\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Test Cloudflare Connection\u003C\u002Fstrong> to verify\u003C\u002Fli>\n\u003Cli>The \u003Cstrong>☁ CF Purge\u003C\u002Fstrong> menu will now appear in your admin bar\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Creating a Scoped API Token\u003C\u002Fh4>\n\u003Cp>In your Cloudflare dashboard: \u003Cstrong>My Profile \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> API Tokens \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Create Token \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Create Custom Token\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Set these permissions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Zone \u002F Cache Purge \u002F Purge\u003C\u002Fli>\n\u003Cli>Zone \u002F Zone \u002F Read\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Set Zone Resources to the specific zone for this site. This keeps the token scoped and secure.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Do not use your Global API Key.\u003C\u002Fstrong> A scoped token is always the correct approach.\u003C\u002Fp>\n\u003Ch4>Documentation and support\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Full documentation: https:\u002F\u002Flookitdesign.com\u002Fsoftware\u002Fcloudflare-cache-purge\u002F\u003C\u002Fli>\n\u003Cli>Support: https:\u002F\u002Flookitdesign.com\u002Fcloudflare-purge-support-form\u002F\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cem>Lookit® is a registered trademark of ZENOVA CORP. Cloudflare is a registered trademark of Cloudflare, Inc.; this plugin is an independent integration and is not affiliated with, sponsored by, or endorsed by Cloudflare.\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch3>External Services\u003C\u002Fh3>\n\u003Cp>This plugin connects to the Cloudflare API to purge cached files from the Cloudflare CDN. This is required for the core functionality of the plugin — without it, no cache purging can occur.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What data is sent and when:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When you trigger a cache purge (manually or via the Test Connection button), this plugin sends the following data to Cloudflare’s API:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Your Cloudflare Zone ID (to identify which zone to purge)\u003C\u002Fli>\n\u003Cli>Your Cloudflare API Token (for authentication)\u003C\u002Fli>\n\u003Cli>The specific URL(s) to purge, or a full-site purge flag\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>No visitor data, personal information, or site content is ever transmitted. API credentials are stored in your WordPress database and are only sent directly to Cloudflare’s API endpoint (\u003Ccode>https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u003C\u002Fcode>).\u003C\u002Fp>\n\u003Cp>This service is provided by Cloudflare, Inc.:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Terms of Service: https:\u002F\u002Fwww.cloudflare.com\u002Fterms\u002F\u003C\u002Fli>\n\u003Cli>Privacy Policy: https:\u002F\u002Fwww.cloudflare.com\u002Fprivacypolicy\u002F\u003C\u002Fli>\n\u003C\u002Ful>\n","Granular Cloudflare cache control from the admin bar — purge a single page, any URL, or the entire site, right from wp-admin.",147,"2026-06-12T04:58:00.000Z",[19,20,46,47,21],"cdn","cloudflare","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flookit-cf-purge.1.0.0.zip",{"slug":51,"name":52,"version":53,"author":54,"author_profile":55,"description":56,"short_description":57,"active_installs":58,"downloaded":59,"rating":60,"num_ratings":61,"last_updated":62,"tested_up_to":63,"requires_at_least":64,"requires_php":48,"tags":65,"homepage":71,"download_link":72,"security_score":73,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"nginx-helper","Nginx Helper","2.3.5","rtCamp","https:\u002F\u002Fprofiles.wordpress.org\u002Frtcamp\u002F","\u003Col>\n\u003Cli>Removes \u003Ccode>index.php\u003C\u002Fcode> from permalinks when using WordPress with nginx.\u003C\u002Fli>\n\u003Cli>Adds support for purging redis-cache when used as full-page cache created using \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fopenresty\u002Fsrcache-nginx-module#caching-with-redis\" rel=\"nofollow ugc\">nginx-srcache-module\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Adds support for nginx fastcgi_cache_purge & proxy_cache_purge directive from \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FFRiCKLE\u002Fngx_cache_purge\" title=\"ngx_cache_purge module\" rel=\"nofollow ugc\">module\u003C\u002Fa>. Provides settings so you can customize purging rules.\u003C\u002Fli>\n\u003Cli>Adds support for nginx \u003Ccode>map{..}\u003C\u002Fcode> on a WordPress-multisite network installation. Using it, Nginx can serve PHP file uploads even if PHP\u002FMySQL crashes. Please check the tutorial list below for related Nginx configurations.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Tutorials\u003C\u002Fh4>\n\u003Cp>You will need to follow one or more tutorials below to get desired functionality:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Feasyengine.io\u002Fwordpress-nginx\u002Ftutorials\u002Fmultisite\u002Fstatic-files-handling\u002F\" rel=\"nofollow ugc\">Nginx Map + WordPress-Multisite + Static Files Handling\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Feasyengine.io\u002Fwordpress-nginx\u002Ftutorials\u002Fsingle-site\u002Ffastcgi-cache-with-purging\u002F\" rel=\"nofollow ugc\">Nginx + WordPress + fastcgi_purge_cache\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Feasyengine.io\u002Fwordpress-nginx\u002Ftutorials\u002Fmultisite\u002Fsubdirectories\u002Ffastcgi-cache-with-purging\u002F\" rel=\"nofollow ugc\">Nginx + WordPress-Multisite (Subdirectories) + fastcgi_purge_cache\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Feasyengine.io\u002Fwordpress-nginx\u002Ftutorials\u002Fmultisite\u002Fsubdomains\u002Ffastcgi-cache-with-purging\u002F\" rel=\"nofollow ugc\">Nginx + WordPress-Multisite (Subdomains\u002Fdomain-mapping) + fastcgi_purge_cache\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Feasyengine.io\u002Fwordpress-nginx\u002Ftutorials\u002F\" rel=\"nofollow ugc\">Other WordPress-Nginx Tutorials\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Cleans nginx's fastcgi\u002Fproxy cache or redis-cache whenever a post is edited\u002Fpublished. Also does a few more things.",200000,6231579,88,31,"2025-08-21T06:49:00.000Z","6.8.6","3.0",[66,67,68,69,70],"cache-purge","fastcgi","nginx","permalinks","redis-cache","https:\u002F\u002Frtcamp.com\u002Fnginx-helper\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnginx-helper.2.3.5.zip",92,{"slug":75,"name":76,"version":77,"author":78,"author_profile":79,"description":80,"short_description":81,"active_installs":82,"downloaded":83,"rating":84,"num_ratings":85,"last_updated":86,"tested_up_to":15,"requires_at_least":87,"requires_php":48,"tags":88,"homepage":92,"download_link":93,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"clear-cache-for-widgets","Clear Cache for Me","2.5","webheadcoder","https:\u002F\u002Fprofiles.wordpress.org\u002Fwebheadllc\u002F","\u003Cp>W3 Total Cache and WP Super Cache are great caching plugins, but they do not know when a widget is updated.  WPEngine is the best place to host your WordPress installation, but their caching system is no smarter when it comes to updating widgets and menus.  I created this plugin because my website did not see any changes when saving widgets or menus using these caching systems.  Clear Cache For Me will purge ALL your cache each time you do a save without having to press an additional button.  It may be overkill, which may be why it’s not built in, but some people need simplicity.\u003C\u002Fp>\n\u003Cp>In addition to clearing those pesky caching engines, Clear Cache for Me can force your browser to reload your current theme’s CSS and JS files.  I modify my theme’s CSS and JS files every so often and always have trouble with the browser not getting the latest version.  So now after clicking on the “Clear Cache Now!” button on the dashboard the browser will be forced to reload the current theme’s CSS and JS files.  If you do not click the “Clear Cache Now!” button, the browser will cache the CSS and JS files like it normally does.\u003C\u002Fp>\n\u003Cp>The popular Qode themes has a options to set your own custom CSS and JS.  Sometimes you may not see your changes for a long while because your browser is trying to get the cached file.  Whenever you save your Qode’s options, the CSS and JS files will be forced to reload in the browser on the public side.\u003C\u002Fp>\n\u003Cp>Works with the following caching plugins:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Autoptimize\u003C\u002Fli>\n\u003Cli>Breeze Cache\u003C\u002Fli>\n\u003Cli>Cache Enabler\u003C\u002Fli>\n\u003Cli>Cloudflare\u003C\u002Fli>\n\u003Cli>GoDaddy Cache\u003C\u002Fli>\n\u003Cli>Kinsta Cache\u003C\u002Fli>\n\u003Cli>LiteSpeed Cache\u003C\u002Fli>\n\u003Cli>Elementor (CSS cache)\u003C\u002Fli>\n\u003Cli>Premium Addons for Elementor\u003C\u002Fli>\n\u003Cli>SiteGround SuperCacher\u003C\u002Fli>\n\u003Cli>Super Page Cache\u003C\u002Fli>\n\u003Cli>WP Fastest Cache\u003C\u002Fli>\n\u003Cli>WP Optimize Cache\u003C\u002Fli>\n\u003Cli>WP Rocket\u003C\u002Fli>\n\u003Cli>WP Super Cache\u003C\u002Fli>\n\u003Cli>W3 Total Cache\u003C\u002Fli>\n\u003Cli>WPEngine Cache\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Clears all cache for following actions (requires a caching system above to be active):\u003C\u002Fp>\n\u003Cul>\n\u003Cli>When Widgets are saved.\u003C\u002Fli>\n\u003Cli>When Customizer is saved.\u003C\u002Fli>\n\u003Cli>When Menus are saved.\u003C\u002Fli>\n\u003Cli>When a fields in Advanced Custom Fields are saved.\u003C\u002Fli>\n\u003Cli>When a Contact Form 7 form is saved.\u003C\u002Fli>\n\u003Cli>When a Formidable Form form is saved.\u003C\u002Fli>\n\u003Cli>When WooThemes settings are saved.\u003C\u002Fli>\n\u003Cli>When NextGen Gallery albums and galleries are updated (beta – may not clear cache on all actions).\u003C\u002Fli>\n\u003Cli>When Qode options are saved this plugin forces browsers to reload the custom css and custom js.\u003C\u002Fli>\n\u003Cli>When a WP Forms forms or settings are saved.\u003C\u002Fli>\n\u003Cli>When WooCommerce settings are saved. (Cache should already be clearing when products are saved.)\u003C\u002Fli>\n\u003Cli>When settings from the Insert Headers and Footers plugin by WPBeginner are saved.  \u003C\u002Fli>\n\u003Cli>When Settings from a settings page is saved.  This includes settings from WordPress core, Yoast SEO, and most other plugins using the Settings API.\u003C\u002Fli>\n\u003Cli>When WordPress is updated.\u003C\u002Fli>\n\u003Cli>When plugins are updated, activated, and deactivated.\u003C\u002Fli>\n\u003Cli>When WordPress, plugins, and themes are automaticallly updated.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwebheadcoder.com\u002Fclear-cache-for-me\u002F\" rel=\"nofollow ugc\">See the plugin’s homepage for more details\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Note:  Since some caching systems run in the \u003Ccode>shutdown\u003C\u002Fcode> hook, this plugin also runs in that hook.  This means if PHP does not have enough time, some code including any hooks within the \u003Ccode>ccfm_clear_cache_for_all()\u003C\u002Fcode> function are not guaranteed to run.  If you need code to run, consider using the \u003Ccode>ccfm_clear_cache_for_me_setup\u003C\u002Fcode> hook.\u003C\u002Fp>\n\u003Cp>Some plugins may have “auto purge” (like Cloudflare), but it doesn’t cover all the items this plugin covers.\u003C\u002Fp>\n\u003Ch3>Developer Options\u003C\u002Fh3>\n\u003Ch4>ccfm_supported_caching_exists\u003C\u002Fh4>\n\u003Cp>Use this filter to determine if this plugin should do anything including showing the button on the dashboard.  Return true if a caching system is supported.\u003Cbr \u002F>\nDefault: True if any of the supported caching systems is active.\u003Cbr \u002F>\nSee Example 1 below.\u003C\u002Fp>\n\u003Ch4>ccfm_admin_init or ccfm_init_actions\u003C\u002Fh4>\n\u003Cp>Use this action to add hooks when cache is to be cleared.  Or do any other setup activity.\u003C\u002Fp>\n\u003Ch4>ccfm_clear_cache_for_me_before\u003C\u002Fh4>\n\u003Cp>Use this action to clear cache from an unsupported caching system before the default caching systems clear their cache.\u003C\u002Fp>\n\u003Ch4>ccfm_clear_cache_for_me\u003C\u002Fh4>\n\u003Cp>Use this action to clear cache from an unsupported caching system after the default caching systems clear their cache.\u003C\u002Fp>\n\u003Ch4>Example\u003C\u002Fh4>\n\u003Cp>If you were using an unsupported caching system you’ll need to identify the caching plugin’s class or function which clears the cache.  As an example, if the unsupported caching system called the \u003Ccode>MyOtherCache::clear_all()\u003C\u002Fcode> function, you would use the following code to get this plugin to clear the cache.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php\nfunction my_other_cache_enable( $return = false ) {\n    if ( class_exists( 'MyOtherCache' ) )\n        return true;\n    return $return;\n}\nadd_filter('ccfm_supported_caching_exists', 'my_other_cache_enable');\n\nfunction my_other_cache_clear() {\n    if ( my_other_cache_enable() )\n        MyOtherCache::clear_all();\n}\nadd_action('ccfm_clear_cache_for_me', 'my_other_cache_clear');\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Purges cache on WPEngine, W3TC, WP Super Cache, WP Fastest Cache when widgets, menus, settings update.  Forces browsers to reload CSS and JS files.",40000,766839,96,29,"2026-06-18T02:06:00.000Z","3.8",[20,89,90,91,21],"clear","css","js","https:\u002F\u002Fwebheadcoder.com\u002Fclear-cache-for-me\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fclear-cache-for-widgets.2.5.zip",{"slug":95,"name":96,"version":97,"author":98,"author_profile":99,"description":100,"short_description":101,"active_installs":82,"downloaded":102,"rating":60,"num_ratings":103,"last_updated":104,"tested_up_to":15,"requires_at_least":105,"requires_php":17,"tags":106,"homepage":109,"download_link":110,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"varnish-http-purge","Proxy Cache Purge","5.12.0","Danila Vershinin","https:\u002F\u002Fprofiles.wordpress.org\u002Fdvershinin\u002F","\u003Cp>\u003Cstrong>This plugin \u003Cem>does not\u003C\u002Fem> install nor configure a cache proxy. It acts as an interface with such services.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>One common method of caching content for websites is via the use of reverse proxy caching. Common examples of this are \u003Ca href=\"https:\u002F\u002Fwww.varnish-cache.org\u002F\" rel=\"nofollow ugc\">Varnish\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwww.nginx.org\u002F\" rel=\"nofollow ugc\">NGINX\u003C\u002Fa>. These systems allow a website to update content and have the visitor’s experience cached without the need for complex plugins storing the files locally and using up a user’s disk space.\u003C\u002Fp>\n\u003Cp>A reverse proxy cache is installed in front of a server and reviews requests. If the page being requested is already cached, it delivers the cached content. Otherwise it generates the page and the cache on demand.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The Proxy Cache Purge plugin sends a request to delete (aka flush) the cached data of a page or post every time it’s modified.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>How It Works\u003C\u002Fh4>\n\u003Cp>When content on a site is updated by WordPress, the plugin reaches out to the proxy cache service with the URL of the page, requesting the cache be deleted.\u003C\u002Fp>\n\u003Cp>Not all pages are deleted from the cache on every change. For example, when a post, page, or custom post type is edited, or a new comment is added, \u003Cem>only\u003C\u002Fem> the following pages will purge:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The front page\u003C\u002Fli>\n\u003Cli>The post\u002Fpage edited\u003C\u002Fli>\n\u003Cli>Any categories, tags, and\u002For custom taxonomies associated with the page\u003C\u002Fli>\n\u003Cli>Related feeds\u003C\u002Fli>\n\u003Cli>Associated JSON API pages\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In addition, your \u003Cem>entire\u003C\u002Fem> cache will be deleted on the following actions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Changing themes\u003C\u002Fli>\n\u003Cli>Pressing the \u003Cstrong>Empty Cache\u003C\u002Fstrong> button on the toolbar\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Plugins can hook into the purge actions as well, to filter their own events to trigger a purge.\u003C\u002Fp>\n\u003Cp>On a multisite network using subfolders, only \u003Cstrong>network admins\u003C\u002Fstrong> can purge the main site.\u003C\u002Fp>\n\u003Ch4>Keep Your Cache Warm\u003C\u002Fh4>\n\u003Cp>Purging is only half the story. Once Proxy Cache Purge empties a page, the cache for that URL is gone, so the next visitor triggers a full uncached render and waits for it. On busy sites this “cache stampede” shows up as slow pages right after every update.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.getpagespeed.com\u002Fcacheability-pro?ref=vhp-readme\" rel=\"nofollow ugc\">Cacheability Pro\u003C\u002Fa> is a companion plugin that closes that gap: it automatically re-warms purged URLs in the background so visitors keep hitting fast, cached responses, and it tunes your cache headers so more of your pages stay cacheable in the first place. Proxy Cache Purge handles invalidation; Cacheability Pro handles everything around it.\u003C\u002Fp>\n\u003Ch4>Monitor Your Cache\u003C\u002Fh4>\n\u003Cp>Proxy Cache Purge keeps your cache fresh, but how often is it actually being hit? If you run your own Varnish or NGINX server, \u003Ca href=\"https:\u002F\u002Famplify.getpagespeed.com\u002Fvarnish-monitoring?ref=vhp-amplify-readme\" rel=\"nofollow ugc\">GetPageSpeed Amplify\u003C\u002Fa> shows your cache hit rate, request volume, and backend health over time, with a free tier. Proxy Cache Purge handles invalidation; Amplify shows you whether the cache is doing its job.\u003C\u002Fp>\n\u003Ch4>Development Mode\u003C\u002Fh4>\n\u003Cp>If you’re working on a site and need to turn off caching in one of two ways:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Add \u003Ccode>define( 'VHP_DEVMODE', true );\u003C\u002Fcode> to your \u003Ccode>wp-config.php\u003C\u002Fcode> file\u003C\u002Fli>\n\u003Cli>Go to Proxy Cache -> Settings and enable Debug Mode for 24 hours at a time\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>That will break cache on page loads. It is \u003Cem>not\u003C\u002Fem> recommended for production!\u003C\u002Fp>\n\u003Ch4>Cache Tags (BETA)\u003C\u002Fh4>\n\u003Cp>As of version 5.4.0, Proxy Cache Purge includes an \u003Cstrong>optional Cache Tags \u002F Surrogate Keys purge mode\u003C\u002Fstrong>. This feature is marked as \u003Cstrong>BETA\u003C\u002Fstrong> and is disabled by default.\u003C\u002Fp>\n\u003Cp>When enabled, the plugin:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Adds cache-tag headers to WordPress responses (for example, tagging pages by post ID, post type, taxonomy terms, author, and archives).\u003C\u002Fli>\n\u003Cli>Uses tag-based purges instead of individual URL purges when content is updated, which can reduce purge traffic and improve consistency on complex sites.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Requirements:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A proxy cache that supports Cache Tags \u002F Surrogate Keys and advertises this via standard \u003Ccode>Surrogate-Capability\u003C\u002Fcode> headers (for example, \u003Ccode>Surrogate-Capability: vhp=\"Surrogate\u002F1.0 tags\u002F1\"\u003C\u002Fcode>).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>How to enable:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Go to \u003Cstrong>Proxy Cache \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Purge Method\u003C\u002Fstrong> and check \u003Cstrong>“Use Cache Tags (Surrogate Keys)”\u003C\u002Fstrong>. The checkbox is only enabled when your cache tells WordPress it supports tags (or when you explicitly enable it via a define).\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Alternatively, you can force-enable or force-disable detection via \u003Ccode>wp-config.php\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cp>define( ‘VHP_VARNISH_TAGS’, true );  \u002F\u002F Force treat cache as tag-capable\u003Cbr \u002F>\ndefine( ‘VHP_VARNISH_TAGS’, false ); \u002F\u002F Force treat cache as not tag-capable\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Because this feature depends on your cache configuration, it is recommended that you test it carefully in staging before enabling it on production.\u003C\u002Fp>\n\u003Ch4>Background Purging with WP-Cron\u003C\u002Fh4>\n\u003Cp>On busy sites, sending many PURGE requests directly from admin requests can slow things down. When you define \u003Ccode>DISABLE_WP_CRON\u003C\u002Fcode> as \u003Ccode>true\u003C\u002Fcode> in \u003Ccode>wp-config.php\u003C\u002Fcode> (because you are running a real system cron that calls \u003Ccode>wp-cron.php\u003C\u002Fcode>), Proxy Cache Purge automatically switches to an asynchronous mode:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Purge requests (both URL-based and tag-based, when Cache Tags are enabled) are collected into a small per-site queue.\u003C\u002Fli>\n\u003Cli>The queue is processed by WP-Cron in the background, keeping your admin and content-editing actions responsive even when many URLs or tags must be invalidated.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Object-cache purges (the “Purge Database Cache” option) remain synchronous and are not affected by this behaviour. The Proxy Cache settings page and Site Health integration expose basic queue status so you can verify that background purging is healthy; if the queue appears large or very old, check that your system cron is correctly invoking WordPress cron.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Important: Cron Frequency and Cache Freshness\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When using background purging, the frequency of your system cron determines how quickly cache invalidations are processed. The longer the interval between cron runs, the longer visitors may see stale content after updates.\u003C\u002Fp>\n\u003Cp>For minimal stale content, run your system cron every minute:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>* * * * * \u002Fusr\u002Fbin\u002Fphp \u002Fvar\u002Fwww\u002Fhtml\u002Fwp-cron.php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If you can tolerate slightly longer delays, every 2-5 minutes is also acceptable. However, running cron less frequently (e.g., every 15 minutes) means cache purges may be delayed by that amount after content changes.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> Scheduled posts are handled specially. When a scheduled post is published via WP-Cron, the cache is purged synchronously within the same cron run, ensuring immediate cache invalidation without waiting for the next cron execution.\u003C\u002Fp>\n\u003Cp>For detailed instructions on setting up a proper Linux-based WordPress cron, see: \u003Ca href=\"https:\u002F\u002Fwww.getpagespeed.com\u002Fweb-apps\u002Fwordpress\u002Fwordpress-cron-optimization\" rel=\"nofollow ugc\">WordPress Cron Optimization\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Disabling Background Purging\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you have \u003Ccode>DISABLE_WP_CRON\u003C\u002Fcode> defined but do not want background purging (for example, on low-traffic sites where immediate purges are preferred), you can force-disable cron-based purging by adding this to your \u003Ccode>wp-config.php\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'VHP_DISABLE_CRON_PURGING', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>With this constant set, all cache purges will execute immediately during the request, regardless of the \u003Ccode>DISABLE_WP_CRON\u003C\u002Fcode> setting.\u003C\u002Fp>\n\u003Ch3>WP-CLI\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Purge\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Purge commands let you empty the cache.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish purge\u003C\u002Fcode> – Flush the entire site cache (equivalent to clicking “Empty Cache” in admin)\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --all\u003C\u002Fcode> – Explicitly flush the entire site cache\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge \u003Curl>\u003C\u002Fcode> – Flush cache for a specific URL and all content below it (wildcard)\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge \u003Curl> --url-only\u003C\u002Fcode> – Flush cache for only the exact URL specified (no wildcard)\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --tag=\u003Ctag>\u003C\u002Fcode> – Flush cache by tag (requires Cache Tags mode to be enabled)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish purge\u003C\u002Fcode> – Purge entire site\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --all\u003C\u002Fcode> – Same as above, more explicit\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge https:\u002F\u002Fexample.com\u002Fhello-world\u002F\u003C\u002Fcode> – Purge this URL and everything below it\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge https:\u002F\u002Fexample.com\u002Fhello-world\u002F --url-only\u003C\u002Fcode> – Purge only this exact URL\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge https:\u002F\u002Fexample.com\u002Fwp-content\u002Fthemes\u002F --wildcard\u003C\u002Fcode> – Purge all theme files\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --tag=p-123\u003C\u002Fcode> – Purge all pages tagged with post ID 123\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --tag=pt-post\u003C\u002Fcode> – Purge all cached pages of post type “post”\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Debug\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Debugging can help you figure out why your cache isn’t working as well as it could. The default is for your home page, but you can pass any URL on your domain.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish debug [\u003Curl>]\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Available parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>[--include-headers]\u003C\u002Fcode> —  Include headers in debug check output\u003C\u002Fli>\n\u003Cli>\u003Ccode>[--include-grep]\u003C\u002Fcode> — Grep active theme and plugin directories for common issues\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>DevMode\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Development mode allows you to disable the cache, temporarily.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish devmode [\u003Cactivate|deactivate|toggle>]\u003C\u002Fcode> – Change development mode state\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Async purge queue (cron-mode)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When you define \u003Ccode>DISABLE_WP_CRON\u003C\u002Fcode> as \u003Ccode>true\u003C\u002Fcode> and run a real system cron for WordPress, Proxy Cache Purge can move heavy purge work into a small background queue that is processed by WP‑Cron.\u003C\u002Fp>\n\u003Cp>You can inspect and manage that queue via WP‑CLI:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish queue status\u003C\u002Fcode> – show whether cron-mode is active, if a full purge is queued, counts of queued URLs\u002Ftags, and the last queue run time.\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish queue process\u003C\u002Fcode> – process any items currently in the queue (useful to run after deploys or cache‑sensitive operations).\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish queue clear\u003C\u002Fcode> – clear the queue without sending any PURGE requests.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>These commands do not replace your normal WordPress cron (you still need a cron entry that calls \u003Ccode>wp cron event run --due-now\u003C\u002Fcode> or hits \u003Ccode>wp-cron.php\u003C\u002Fcode>), but they give you a simple operational handle when using cron‑mode.\u003C\u002Fp>\n\u003Ch4>Understanding Purge Behavior\u003C\u002Fh4>\n\u003Cp>There are different types of cache purges, and they behave differently:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Manual Purges (Admin Bar)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>“Purge Cache (All Pages)”\u003C\u002Fstrong> – Sends a single regex purge request to invalidate the entire cache. Always executes immediately.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>“Purge Cache (this page)”\u003C\u002Fstrong> – Purges only the exact URL you’re viewing. Always executes immediately.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Manual purges are always immediate, even when background cron-mode is enabled. This is intentional: when you click a button, you expect immediate results.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Automatic Purges (Post Save\u002FUpdate)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When you save or update a post, the plugin automatically purges:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The post’s URL\u003C\u002Fli>\n\u003Cli>The homepage\u003C\u002Fli>\n\u003Cli>Category archive pages\u003C\u002Fli>\n\u003Cli>Tag archive pages\u003C\u002Fli>\n\u003Cli>Author archive page\u003C\u002Fli>\n\u003Cli>Date-based archives\u003C\u002Fli>\n\u003Cli>RSS feeds\u003C\u002Fli>\n\u003Cli>Related REST API endpoints\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This can be 20-50+ URLs depending on your site structure. When cron-mode is enabled, these automatic purges are queued and processed in the background to avoid slowing down the post editor.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key Difference\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>  Action\u003Cbr \u002F>\n  URLs Purged\u003Cbr \u002F>\n  Uses Cron Queue?\u003C\u002Fp>\n\u003Cp>  “Purge Cache (All Pages)”\u003Cbr \u002F>\n  1 (regex)\u003Cbr \u002F>\n  No – always immediate\u003C\u002Fp>\n\u003Cp>  “Purge Cache (this page)”\u003Cbr \u002F>\n  1\u003Cbr \u002F>\n  No – always immediate\u003C\u002Fp>\n\u003Cp>  Post save\u002Fupdate\u003Cbr \u002F>\n  20-50+\u003Cbr \u002F>\n  Yes (if cron-mode enabled)\u003C\u002Fp>\n\u003Cp>If you need to immediately purge all URLs related to a specific post (not just the post URL), save the post – the automatic purge will handle all related URLs.\u003C\u002Fp>\n","Automatically empty proxy cached content when your site is modified.",2342003,26,"2026-06-24T17:42:00.000Z","5.0",[20,68,107,21,108],"proxy","varnish","https:\u002F\u002Fgithub.com\u002Fdvershinin\u002Fvarnish-http-purge","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fvarnish-http-purge.5.12.0.zip",{"slug":112,"name":113,"version":114,"author":115,"author_profile":116,"description":117,"short_description":118,"active_installs":119,"downloaded":120,"rating":73,"num_ratings":121,"last_updated":122,"tested_up_to":15,"requires_at_least":123,"requires_php":48,"tags":124,"homepage":126,"download_link":127,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"nginx-cache","Nginx Cache","1.0.8","Till Krüss","https:\u002F\u002Fprofiles.wordpress.org\u002Ftillkruess\u002F","\u003Cp>Purge the \u003Ca href=\"http:\u002F\u002Fnginx.org\" rel=\"nofollow ugc\">Nginx\u003C\u002Fa> cache (FastCGI, Proxy, uWSGI) automatically when content changes or manually within WordPress.\u003C\u002Fp>\n\u003Cp>Requirements:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFilesystem_API\" rel=\"nofollow ugc\">Filesystem API\u003C\u002Fa> needs to function without asking for credentials.\u003C\u002Fli>\n\u003Cli>Nginx and PHP need to run under the same user, or PHP’s user needs write access to Nginx’s cache path.\u003C\u002Fli>\n\u003C\u002Ful>\n","Purge the Nginx cache (FastCGI, Proxy, uWSGI) automatically when content changes or manually within WordPress.",10000,321121,23,"2026-05-04T17:54:00.000Z","3.1",[20,67,125,68,21],"flush","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fnginx-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnginx-cache.1.0.8.zip",{"error":129,"url":130,"statusCode":131,"statusMessage":132,"message":132},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Flookit-cache-purge-for-sucuri\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":134,"versions":135},1,[136],{"version":6,"download_url":25,"svn_tag_url":137,"released_at":27,"has_diff":138,"diff_files_changed":139,"diff_lines":27,"trac_diff_url":27,"vulnerabilities":140,"is_current":129},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Flookit-cache-purge-for-sucuri\u002Ftags\u002F1.0.0\u002F",false,[],[]]