[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fLZAJPeBZQkPB_kHShPojeOeYAIjylKF72ir-o_HIWo4":3},{"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":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":24,"download_link":25,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29,"vulnerabilities":30,"developer":31,"crawl_stats":28,"alternatives":36,"analysis":138,"fingerprints":205},"cache-purge-helper","Cache Purge Helper","0.1.3","jordantrizz","https:\u002F\u002Fprofiles.wordpress.org\u002Fjordantrizz\u002F","\u003Cp>This plugin will trigger a cache purge using the LSCache or Nginx Helper plugin when hooks are fired by popular plugins or themes.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>If using the LSCache plugin, Litespeed Enterprise or Openlightspeed is required to purge server cache.\u003C\u002Fli>\n\u003Cli>If using the Nginx Helper plugin, Nginx cache method FastCGI or Nginx Redi Cache is required to purge server cache.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The following themes and plugins hooks are used.\u003C\u002Fp>\n\u003Ch3>WordPress Core Hooks\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>upgrader_process_complete\u003C\u002Fli>\n\u003Cli>activated_plugin\u003C\u002Fli>\n\u003Cli>deactivated_plugin\u003C\u002Fli>\n\u003Cli>switch_theme\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Beaver Builder Plugin\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>fl_builder_cache_cleared\u003C\u002Fli>\n\u003Cli>fl_builder_after_save_layout\u003C\u002Fli>\n\u003Cli>fl_builder_after_save_user_template\u003C\u002Fli>\n\u003Cli>upgrader_process_complete\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Elementor Plugin\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>elementor\u002Fcore\u002Ffiles\u002Fclear_cache\u003C\u002Fli>\n\u003Cli>update_option__elementor_global_css\u003C\u002Fli>\n\u003Cli>delete_option__elementor_global_css\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Autoptimizer Plugin\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>delete_option__elementor_global_css\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Oxygen Theme\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>wp_ajax_oxygen_vsb_cache_generated\u003C\u002Fli>\n\u003Cli>update_option__oxygen_vsb_universal_css_url\u003C\u002Fli>\n\u003Cli>update_option__oxygen_vsb_css_files_state\u003C\u002Fli>\n\u003C\u002Ful>\n","A helper plugin to purge cache via the LSCache and Nginx Helper plugins for popular WordPress plugins and themes.",300,8997,100,2,"2021-12-21T21:00:00.000Z","5.8.13","3.0","7.4",[20,21,22,23],"cache","litespeed","nginx","purge","https:\u002F\u002Fwpinfo.net","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-purge-helper.0.1.4.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":11,"avg_security_score":26,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},1,30,84,"2026-04-05T09:47:45.238Z",[37,59,79,98,118],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":17,"requires_php":51,"tags":52,"homepage":57,"download_link":58,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"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.",100000,6119694,88,31,"2025-08-21T06:49:00.000Z","6.8.5","",[53,54,22,55,56],"cache-purge","fastcgi","permalinks","redis-cache","https:\u002F\u002Frtcamp.com\u002Fnginx-helper\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnginx-helper.2.3.5.zip",{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":47,"num_ratings":69,"last_updated":70,"tested_up_to":71,"requires_at_least":72,"requires_php":73,"tags":74,"homepage":77,"download_link":78,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"varnish-http-purge","Proxy Cache Purge","5.7.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>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.",40000,2164070,26,"2026-03-13T00:00:00.000Z","6.3.8","5.0","5.6",[20,22,75,23,76],"proxy","varnish","https:\u002F\u002Fgithub.com\u002Fdvershinin\u002Fvarnish-http-purge","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fvarnish-http-purge.5.7.0.zip",{"slug":80,"name":81,"version":82,"author":83,"author_profile":84,"description":85,"short_description":86,"active_installs":87,"downloaded":88,"rating":89,"num_ratings":90,"last_updated":91,"tested_up_to":92,"requires_at_least":93,"requires_php":51,"tags":94,"homepage":96,"download_link":97,"security_score":89,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"nginx-cache","Nginx Cache","1.0.7","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,307696,92,23,"2024-11-26T20:26:00.000Z","6.7.5","3.1",[20,54,95,22,23],"flush","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fnginx-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnginx-cache.1.0.7.zip",{"slug":99,"name":100,"version":101,"author":102,"author_profile":103,"description":104,"short_description":105,"active_installs":106,"downloaded":107,"rating":13,"num_ratings":108,"last_updated":109,"tested_up_to":50,"requires_at_least":110,"requires_php":111,"tags":112,"homepage":114,"download_link":115,"security_score":116,"vuln_count":32,"unpatched_count":27,"last_vuln_date":117,"fetched_at":29},"hestia-nginx-cache","Hestia Nginx Cache","2.4.3","Juni","https:\u002F\u002Fprofiles.wordpress.org\u002Fjakobbouchard\u002F","\u003Cp>\u003Cstrong>Important\u003C\u002Fstrong>: Hestia 1.6.12 fixes an issue where purging the cache could make the website unavailable, resulting in a 502 error. If you aren’t using this version, please upgrade!\u003C\u002Fp>\n\u003Cp>This plugin automatically purges the Nginx cache after you make a website change such as updating a post or changing your theme.\u003C\u002Fp>\n\u003Cp>You also have the ability to manually purge the cache using a button in the WordPress admin bar.\u003C\u002Fp>\n","Purged the Nginx cache automatically after making website changes. Uses the new HestiaCP API, released in 1.6.0.",1000,14525,9,"2025-06-25T22:48:00.000Z","4.8","5.4",[20,95,113,22,23],"hestia","https:\u002F\u002Fgithub.com\u002Fimjuniper\u002Fhestia-nginx-cache","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhestia-nginx-cache.2.4.3.zip",99,"2024-12-30 00:00:00",{"slug":119,"name":120,"version":121,"author":122,"author_profile":123,"description":124,"short_description":125,"active_installs":106,"downloaded":126,"rating":13,"num_ratings":127,"last_updated":128,"tested_up_to":129,"requires_at_least":51,"requires_php":51,"tags":130,"homepage":134,"download_link":135,"security_score":136,"vuln_count":14,"unpatched_count":27,"last_vuln_date":137,"fetched_at":29},"tnc-toolbox","TNC Toolbox: Web Performance","2.1.2","Merlot Digital (by TNC)","https:\u002F\u002Fprofiles.wordpress.org\u002Fleopardhost\u002F","\u003Cp>TNC Toolbox aims to enhance your WordPress experience with NGINX-on-cPanel (ea-nginx).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Built for our Managed Server clients, we’ve open-sourced it so others can enjoy it too!\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>With a heavy focus on the Apache + NGINX as Reverse Caching Proxy web stack, the plugin aims to help with Website Management, Performance and Security.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>❤️ \u003Cstrong>FOSS by \u003Ca href=\"https:\u002F\u002Ftnc.works\" rel=\"nofollow ugc\">The Network Crew Pty Ltd\u003C\u002Fa> (TNC) for \u003Ca href=\"https:\u002F\u002Fmerlot.digital\" rel=\"nofollow ugc\">Merlot Digital\u003C\u002Fa> & the world.\u003C\u002Fstrong> ❤️\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch3>Functionality\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>At the moment, TNC Toolbox:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Allows you to enable, disable and purge the NGINX User Cache\u003C\u002Fli>\n\u003Cli>Purges the NGINX Cache magically on post\u002Fpage publish\u002Fupdate!\u003C\u002Fli>\n\u003Cli>Also purges the Cache when the WP Core is successfully updated\u003C\u002Fli>\n\u003Cli>Lets you know if the plugin is activated but not yet configured\u003C\u002Fli>\n\u003Cli>Only allows Admins to enable\u002Fdisable caching & edit configs\u003C\u002Fli>\n\u003Cli>Shows you the status of cP UAPI via disk usage info\u003C\u002Fli>\n\u003Cli>Purge when any ACF config options are saved\u003C\u002Fli>\n\u003Cli>Supports scheduled post publishing!\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Eager for even more capabilities?\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>We plan to add further features as clients & the community request it.\u003C\u002Fp>\n\u003Cp>\u003Cem>Please let us know your ideas on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FThe-Network-Crew\u002FTNC-Toolbox-for-WordPress\u002F\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa> – we’d love to hear from you!\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch3>Caching Deployments\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Caching ideals:\u003C\u002Fstrong>\u003Cbr \u002F>\n– Don’t forget, ea-NGINX (reverse proxy caching) is meant to be 2nd-level\u003Cbr \u002F>\n– ie. Make sure your WP site also has on-site caching, like WP Super Cache\u003Cbr \u002F>\n– You can go further with caching, and should: like browser-caching assets!\u003C\u002Fp>\n\u003Cp>\u003Cstrong>3-layer Cache:\u003C\u002Fstrong>\u003Cbr \u002F>\n1. NGINX Caching Proxy (ahead of Apache)\u003Cbr \u002F>\n2. WP Super Cache, WP Rocket, etc on-site\u003Cbr \u002F>\n3. htaccess\u002Fetc rules for Browser Caching\u003C\u002Fp>\n\u003Cp>\u003Cstrong>This way, you can ensure maximum efficiency!\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The key is to purge when stale, so properly configuring your WP Plugin Cache is critical to ensuring that you don’t end up with cache misses due to stale data that could’ve\u002Fshould’ve been purged by garbage collection, preloading, etc, rule-sets.\u003C\u002Fp>\n\u003Ch3>Updating from v1 to v2.x.x\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>On every website running the plugin, check that:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Website is reporting v2.x.x plugin version.\u003C\u002Fli>\n\u003Cli>Plugin has been activated post-update. *\u003C\u002Fli>\n\u003Cli>Config exists in the plugin settings.\u003C\u002Fli>\n\u003Cli>API status checker reports OK.\u003C\u002Fli>\n\u003Cli>\u002Fwp-content\u002Ftnc-toolbox-config\u002F folder is gone.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cem>(* Change to main plugin file name may result in deactivation)\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch3>Verifying cP+WHM Logs\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>If you’d like to ensure actions are firing properly at a deeper level:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>WHM > Tweak Settings > Logging > Enable cPanel API Log > On\u003C\u002Fli>\n\u003Cli>WHM > Terminal > \u003Ccode>tail -f \u002Fusr\u002Flocal\u002Fcpanel\u002Flogs\u002Fapi_log\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>WordPress > Update a Post\u002FPage, or explicitly Purge\u003C\u002Fli>\n\u003Cli>WHM > Terminal > You should see the action fire!\u003C\u002Fli>\n\u003Cli>WHM > Terminal > Ctrl+C to close the tail\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Note: To do this, you require \u003Ccode>root\u003C\u002Fcode> access to the Server.\u003C\u002Fp>\n","Designed for ea-NGINX (Cache\u002FProxy) on cPanel+WHM. Made to help you fly online! 🚀",27896,4,"2026-01-13T08:07:00.000Z","6.9.4",[131,53,132,22,133],"automatic-purge","freeware","web-performance","https:\u002F\u002Fmerlot.digital","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftnc-toolbox.2.1.2.zip",93,"2025-11-29 00:00:00",{"attackSurface":139,"codeSignals":190,"taintFlows":197,"riskAssessment":198,"analyzedAt":204},{"hooks":140,"ajaxHandlers":182,"restRoutes":187,"shortcodes":188,"cronEvents":189,"entryPointCount":32,"unprotectedCount":32},[141,147,149,152,155,157,159,162,164,167,170,173,176,179],{"type":142,"name":143,"callback":144,"priority":145,"file":146,"line":34},"action","upgrader_process_complete","cphp_purge",10,"cache-purge-helper.php",{"type":142,"name":148,"callback":144,"priority":145,"file":146,"line":26},"activated_plugin",{"type":142,"name":150,"callback":144,"priority":145,"file":146,"line":151},"deactivated_plugin",86,{"type":142,"name":153,"callback":144,"priority":145,"file":146,"line":154},"switch_theme",87,{"type":142,"name":156,"callback":144,"priority":145,"file":146,"line":89},"fl_builder_cache_cleared",{"type":142,"name":158,"callback":144,"priority":145,"file":146,"line":136},"fl_builder_after_save_layout",{"type":142,"name":160,"callback":144,"priority":145,"file":146,"line":161},"fl_builder_after_save_user_template",94,{"type":142,"name":143,"callback":144,"priority":145,"file":146,"line":163},95,{"type":142,"name":165,"callback":144,"priority":145,"file":146,"line":166},"elementor\u002Fcore\u002Ffiles\u002Fclear_cache",101,{"type":142,"name":168,"callback":144,"priority":145,"file":146,"line":169},"update_option__elementor_global_css",102,{"type":142,"name":171,"callback":144,"priority":145,"file":146,"line":172},"delete_option__elementor_global_css",103,{"type":142,"name":174,"callback":144,"priority":145,"file":146,"line":175},"autoptimize_action_cachepurged",109,{"type":142,"name":177,"callback":144,"priority":116,"file":146,"line":178},"update_option__oxygen_vsb_universal_css_url",116,{"type":142,"name":180,"callback":144,"priority":116,"file":146,"line":181},"update_option__oxygen_vsb_css_files_state",117,[183],{"action":184,"nopriv":185,"callback":144,"hasNonce":185,"hasCapCheck":185,"file":146,"line":186},"oxygen_vsb_cache_generated",false,115,[],[],[],{"dangerousFunctions":191,"sqlUsage":192,"outputEscaping":194,"fileOperations":27,"externalRequests":27,"nonceChecks":27,"capabilityChecks":27,"bundledLibraries":196},[],{"prepared":27,"raw":27,"locations":193},[],{"escaped":27,"rawEcho":27,"locations":195},[],[],[],{"summary":199,"deductions":200},"The cache-purge-helper plugin v0.1.3 exhibits a mixed security posture. On one hand, the code demonstrates good practices in several areas: it has no dangerous functions, all SQL queries utilize prepared statements, and all output is properly escaped. Furthermore, there are no recorded vulnerabilities (CVEs) associated with this plugin, indicating a potentially stable history. The absence of file operations and external HTTP requests also reduces common attack vectors.\n\nHowever, the plugin presents a significant security concern due to its attack surface. It exposes a single AJAX handler that lacks any authentication or capability checks. This unprotected entry point could potentially be exploited by an unauthenticated user to trigger actions within the plugin, depending on what the AJAX handler actually does. While taint analysis shows no unsanitized paths or critical\u002Fhigh severity issues, the presence of an unprotected AJAX endpoint is a direct vulnerability that could lead to unauthorized actions or privilege escalation if not properly secured within its logic.\n\nIn conclusion, while the underlying code quality regarding SQL and output escaping is commendable, the unprotected AJAX handler is a critical weakness. The lack of vulnerability history is positive but does not negate the immediate risk posed by the exposed functionality. Developers should prioritize adding proper authentication and authorization checks to this AJAX endpoint.",[201],{"reason":202,"points":203},"Unprotected AJAX handler",8,"2026-03-16T19:56:14.858Z",{"wat":206,"direct":211},{"assetPaths":207,"generatorPatterns":208,"scriptPaths":209,"versionParams":210},[],[],[],[],{"cssClasses":212,"htmlComments":213,"htmlAttributes":222,"restEndpoints":223,"jsGlobals":224,"shortcodeOutput":225},[],[214,215,216,217,218,219,220,221],"\u003C!-- Purge Cache Function","\u003C!-- Log to WordPress Debug Log Function","\u003C!-- Plugin Update Hooks","\u003C!-- Beaver Builder","\u003C!-- Elementor","\u003C!-- AutoOptimizer","\u003C!-- Oxygen","\u003C!-- EOF",[],[],[],[]]