[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fVAT2U5LgA1UmTIq6LlvtxRZh52v3sWRFZQRv4xVHPos":3,"$f-orIWPP02VF7s2nbqwq8AmC4iviLtDvDqezCRbEiT04":134,"$f2dViTcALTSzAGYfYP-noLhr8iyHtgsZYUBrESRglMgs":139},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"discovery_status":28,"vulnerabilities":29,"developer":30,"crawl_stats":26,"alternatives":36,"analysis":26,"fingerprints":26},"fastcgi-cache-for-ploi","FastCGI Cache for Ploi","1.0.1","Filipe Seabra","https:\u002F\u002Fprofiles.wordpress.org\u002Ffiliprimo\u002F","\u003Cp>FastCGI Cache for Ploi keeps your Ploi-hosted site fast \u003Cem>and\u003C\u002Fem> fresh. When you publish or update content, it calls the Ploi API to flush your site’s Nginx FastCGI cache automatically, so visitors never see stale pages — and you never have to purge by hand.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What it does\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Flushes the FastCGI cache automatically on the events you choose: post publish\u002Fupdate, post deletion, comments, theme switch, Customizer saves, and navigation-menu changes.\u003C\u002Fli>\n\u003Cli>Coalesces bursts of changes into a single flush so a bulk edit doesn’t hammer the API.\u003C\u002Fli>\n\u003Cli>One-click \u003Cstrong>Flush now\u003C\u002Fstrong> button for manual purges.\u003C\u002Fli>\n\u003Cli>A \u003Cstrong>Recent flushes\u003C\u002Fstrong> log so you can see what triggered each flush and whether it succeeded.\u003C\u002Fli>\n\u003Cli>Stores your Ploi API token encrypted at rest.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>How it works\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Connect the plugin to Ploi with a Ploi API token, pick the server and site to target, and choose which events should trigger a flush. From then on it runs in the background.\u003C\u002Fp>\n\u003Cp>This plugin requires a third-party service (the Ploi API) to function — see the \u003Cem>External services\u003C\u002Fem> section below.\u003C\u002Fp>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>This plugin connects to the \u003Cstrong>Ploi API\u003C\u002Fstrong> (https:\u002F\u002Fploi.io), a third-party service, to flush your site’s Nginx FastCGI cache. This connection is required for the plugin to do its job.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>When data is sent to Ploi\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>When you click \u003Cstrong>Connect\u003C\u002Fstrong> — to validate your token and list your servers.\u003C\u002Fli>\n\u003Cli>When you select a server — to list that server’s sites.\u003C\u002Fli>\n\u003Cli>When a flush runs — either automatically (on a content change you enabled) or manually (the \u003Cstrong>Flush now\u003C\u002Fstrong> button).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>What data is sent to Ploi\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Your \u003Cstrong>Ploi API token\u003C\u002Fstrong> — sent as an authorization header on every request.\u003C\u002Fli>\n\u003Cli>The \u003Cstrong>server ID\u003C\u002Fstrong> and \u003Cstrong>site ID\u003C\u002Fstrong> you selected — sent in the request URL when listing sites and when flushing.\u003C\u002Fli>\n\u003Cli>The \u003Cstrong>flush request\u003C\u002Fstrong> itself — an instruction to purge the selected site’s FastCGI cache.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>No post content, personal data, or visitor information is sent to Ploi. Requests are made to \u003Ccode>https:\u002F\u002Fploi.io\u002Fapi\u002F...\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Your use of the Ploi service is governed by Ploi’s legal terms:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Terms of Service: https:\u002F\u002Fploi.io\u002Fterms-of-service\u003C\u002Fli>\n\u003Cli>Privacy Policy: https:\u002F\u002Fploi.io\u002Fprivacy-policy\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Source code & build\u003C\u002Fh3>\n\u003Cp>The compiled admin assets in \u003Ccode>public\u002Fbuild\u002F\u003C\u002Fcode> are minified. The complete, human-readable source (front-end included) and the build steps live in the plugin’s public repository: https:\u002F\u002Fgithub.com\u002Ffilipecsweb\u002Fwp-plugin-fastcgi-cache-for-ploi\u003C\u002Fp>\n\u003Ch3>Disclaimer\u003C\u002Fh3>\n\u003Cp>Ploi is a trademark of its respective owner. This plugin is not affiliated with or endorsed by Ploi.\u003C\u002Fp>\n","Automatically flush your Ploi-managed site's Nginx FastCGI cache the moment content changes — no manual purging.",0,117,"2026-07-12T20:16:00.000Z","7.0.2","6.5","8.2",[18,19,20,21,22],"cache","fastcgi-cache","nginx","performance","purge","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffastcgi-cache-for-ploi\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffastcgi-cache-for-ploi.1.0.1.zip",100,null,"2026-07-22T17:31:50.256Z","no_bundle",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":11,"avg_security_score":25,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"filiprimo",1,30,94,"2026-08-28T19:51:11.929Z",[37,60,78,95,116],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":25,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":50,"tags":51,"homepage":56,"download_link":57,"security_score":34,"vuln_count":58,"unpatched_count":11,"last_vuln_date":59,"fetched_at":27},"tnc-toolbox","TNC Toolbox: Web Performance","2.1.4","Merlot Digital (by TNC)","https:\u002F\u002Fprofiles.wordpress.org\u002Fleopardhost\u002F","\u003Cp>TNC Toolbox enhances your WordPress experience with multi-stack caching support.\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>Now supporting both \u003Cstrong>ea-NGINX (cPanel\u002FWHM)\u003C\u002Fstrong> and \u003Cstrong>LiteSpeed (OpenLiteSpeed\u002FEnterprise)\u003C\u002Fstrong> web stacks, with automatic server detection!\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>\u003Cstrong>Multi-Stack Support\u003C\u002Fstrong>: ea-NGINX (cPanel) and LiteSpeed (OpenLS\u002FEnterprise)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Auto-Detection\u003C\u002Fstrong>: Automatically detects your web server and configures appropriately\u003C\u002Fli>\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\u003Cli>\u003Cstrong>LiteSpeed\u003C\u002Fstrong>: Recommends LiteSpeed Cache plugin for optimal performance\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>For NGINX Stack (cPanel\u002FWHM):\u003C\u002Fstrong>\u003Cbr \u002F>\n– ea-NGINX (reverse proxy caching) is meant to be 2nd-level\u003Cbr \u002F>\n– Make sure your WP site also has on-site caching, like WP Super Cache\u003Cbr \u002F>\n– You can go further with caching: browser-caching assets!\u003C\u002Fp>\n\u003Cp>\u003Cstrong>For LiteSpeed Stack:\u003C\u002Fstrong>\u003Cbr \u002F>\n– Use the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Flitespeed-cache\u002F\" rel=\"ugc\">LiteSpeed Cache plugin\u003C\u002Fa>\u003Cbr \u002F>\n– See \u003Ca href=\"https:\u002F\u002Fdocs.openlitespeed.org\u002Fconfig\u002Flscache\u002F\" rel=\"nofollow ugc\">LiteSpeed Cache documentation\u003C\u002Fa> for configuration\u003C\u002Fp>\n\u003Cp>\u003Cstrong>3-layer Cache (NGINX):\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","Multi-stack caching for WordPress: ea-NGINX (cPanel) and LiteSpeed (OpenLS\u002FEnterprise). Auto-detects web server!",1000,31736,4,"2026-03-27T11:10:00.000Z","6.9.5","",[52,53,54,20,55],"automatic-purge","cache-purge","litespeed","web-performance","https:\u002F\u002Fmerlot.digital","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftnc-toolbox.2.1.4.zip",2,"2025-11-29 00:00:00",{"slug":61,"name":62,"version":63,"author":64,"author_profile":65,"description":66,"short_description":67,"active_installs":68,"downloaded":69,"rating":25,"num_ratings":47,"last_updated":70,"tested_up_to":14,"requires_at_least":15,"requires_php":71,"tags":72,"homepage":74,"download_link":75,"security_score":76,"vuln_count":32,"unpatched_count":11,"last_vuln_date":77,"fetched_at":27},"fastcgi-cache-purge-and-preload-nginx","Nginx Cache Purge Preload","2.1.7","Hasan CALISIR","https:\u002F\u002Fprofiles.wordpress.org\u002Fpsauxit\u002F","\u003Cp>\u003Cstrong>NPP\u003C\u002Fstrong> lets WordPress users manage \u003Cstrong>Nginx Cache Purge and Preload\u003C\u002Fstrong> (FastCGI, Proxy, SCGI, UWSGI) operations directly from the WordPress admin dashboard — actively warming the cache via site crawl, so your Nginx cache is always preloaded and ready.\u003C\u002Fp>\n\u003Cp>NPP is the only Nginx cache plugin that doesn’t just clear the table — it sets the whole banquet. No other Nginx cache plugin comes close to its feature list, purge architecture, preload intelligence on WordPress.\u003C\u002Fp>\n\u003Ch3>🖥️ Quick WP-CLI\u003C\u002Fh3>\n\u003Cp>Manage your Nginx cache entirely from the command line. Perfect for automation, cron jobs, panels, and headless workflows.\u003C\u002Fp>\n\u003Cp>Purge: \u003Ccode>wp npp purge\u003C\u002Fcode> | \u003Ccode>wp npp purge --page-url=\u003Curl>\u003C\u002Fcode>\u003Cbr \u002F>\nPreload: \u003Ccode>wp npp preload\u003C\u002Fcode> | \u003Ccode>wp npp preload --page-url=\u003Curl>\u003C\u002Fcode> | \u003Ccode>wp npp preload --stop\u003C\u002Fcode>\u003Cbr \u002F>\nGet Full command list: \u003Ccode>wp help npp\u003C\u002Fcode> | \u003Ccode>wp help npp \u003Csubcommand>\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>➡️ \u003Cstrong>Resources:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>• Visit the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fpsaux-it\u002Fnginx-fastcgi-cache-purge-and-preload\" rel=\"nofollow ugc\">NPP Main Development Repository\u003C\u002Fa> – Docs, issues & contributions and more.\u003Cbr \u002F>\n• Visit the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fpsaux-it\u002Fnginx-fastcgi-cache-purge-and-preload\u002Ftree\u002Fmain\u002Fsafexec\" rel=\"nofollow ugc\">safexec Main Development Repository\u003C\u002Fa> – NPP’s privilege-dropping C wrapper.\u003Cbr \u002F>\n• Explore \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fpsaux-it\u002Fwordpress-nginx-cache-docker\" rel=\"nofollow ugc\">NPP Containerized\u003C\u002Fa> – Ready to run full stack Nginx Docker setup.\u003Cbr \u002F>\n• Read the \u003Ca href=\"https:\u002F\u002Fwww.psauxit.com\u002Fnginx-fastcgi-cache-purge-preload-for-wordpress\u002F\" rel=\"nofollow ugc\">NPP Main Architecture\u003C\u002Fa> – Technical deep dive article.\u003Cbr \u002F>\n• Refer to the plugin’s \u003Cstrong>Help tab\u003C\u002Fstrong> for more deeper additional guidance.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cp>🧹 \u003Cstrong>Purge All Nginx Cache\u003C\u002Fstrong>: Completely clear all cached data stored by Nginx.\u003C\u002Fp>\n\u003Cp>🔄 \u003Cstrong>Preload All Nginx Cache\u003C\u002Fstrong>: Warm the Nginx cache with the most recent data for the entire website.\u003C\u002Fp>\n\u003Cp>🎯 \u003Cstrong>HTTP Purge (ngx_cache_purge)\u003C\u002Fstrong>: When the Nginx cache module (ngx_cache_purge) is available, NPP uses it as the fastest purge path. Falls back gracefully to index and filesystem purge when the module is not present.\u003C\u002Fp>\n\u003Cp>🗂️ \u003Cstrong>INDEX Purge\u003C\u002Fstrong>: Leverages the preload-generated URL \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Filepath index to directly resolve and purge cache without filesystem traversal. If the cache exists and is valid, purge is executed immediately for near-instant performance.\u003C\u002Fp>\n\u003Cp>⚡ \u003Cstrong>RG Purge\u003C\u002Fstrong>: ripgrep-powered cache file lookup that replaces slow PHP directory scanning for single-URL purges, enabling near-instant deletes on large or FUSE-mounted caches. Automatically falls back to standard scan if unavailable.\u003C\u002Fp>\n\u003Cp>🚀 \u003Cstrong>Auto Preload Nginx Cache\u003C\u002Fstrong>: Automatically preloads the cache when Auto Purge is enabled for a POST\u002FPAGE or after the Purge All action.\u003C\u002Fp>\n\u003Cp>🧼 \u003Cstrong>Auto Purge Nginx Cache\u003C\u002Fstrong>: Purge cache on Post\u002FPage content changes, comment status updates, theme\u002Fplugin updates, or when compatible Cache Plugins trigger a purge. Nginx cache is preloaded automatically if Auto Preload is enabled (for the entire site or individual page).\u003C\u002Fp>\n\u003Cp>🔗 \u003Cstrong>Purge Scope (Related Pages)\u003C\u002Fstrong>: Automatically purge related pages such as the Homepage, WooCommerce Shop page, and Category\u002FTag archives when a single URL is purged. Optionally preload those pages to keep the cache warm.\u003C\u002Fp>\n\u003Cp>📡 \u003Cstrong>Preload Feeds\u003C\u002Fstrong>: Take full control of RSS\u002FAtom feed caching. Decide site‑wide or per‑URL whether the main feed, per‑post comment feeds, and taxonomy RSS feeds are included in the preload process.\u003C\u002Fp>\n\u003Cp>⏰ \u003Cstrong>Schedule Nginx Cache Purge & Preload via WP Cron\u003C\u002Fstrong>: Automate the purge and preload process using WordPress Cron jobs.\u003C\u002Fp>\n\u003Cp>🧭 \u003Cstrong>Proxy Support for Preload\u003C\u002Fstrong>: Route preload requests through a proxy server for edge-case environments and containerized deployments.\u003C\u002Fp>\n\u003Cp>⏱️ \u003Cstrong>Live Preload Progress Monitoring\u003C\u002Fstrong>: Watch the Nginx cache preload process in real time — complete with a dynamic progress bar, currently processed URL, 404 tracking, server load, and total completion time.\u003C\u002Fp>\n\u003Cp>🌐 \u003Cstrong>Remote Nginx Cache Purge & Preload via REST API\u003C\u002Fstrong>: Remotely trigger cache purging and preloading through REST API endpoints.\u003C\u002Fp>\n\u003Cp>⚙️ \u003Cstrong>Manual Nginx Cache Purge & Preload\u003C\u002Fstrong>: Allow manual purging and preloading of cache through the table view in the Advanced Tab.\u003C\u002Fp>\n\u003Cp>📚 \u003Cstrong>Nginx Cache Analyzer\u003C\u002Fstrong>: Full HIT\u002FMISS cache analyzer dashboard, from the last preload crawl with what is currently stored in the Nginx cache. Instantly spot uncached pages and Purge or Preload them directly in the Advanced Tab.\u003C\u002Fp>\n\u003Cp>🪫 \u003Cstrong>Preload All MISS\u003C\u002Fstrong>: A targeted replacement for the expensive Preload All. Instead of purging and re‑caching everything (Preload All), it targets and populates only the cache entries that are not yet warmed. Perfect for sites with high cache coverage (>50%) where a full Preload All be wasteful.\u003C\u002Fp>\n\u003Cp>🔍 \u003Cstrong>On-Page Nginx Cache Purge & Preload\u003C\u002Fstrong>: Manually purge and preload Nginx cache for the currently visited page directly from the frontend.\u003C\u002Fp>\n\u003Cp>🗝️ \u003Cstrong>Custom Cache Key Support\u003C\u002Fstrong>: Define a regex pattern to parse URLs based on your custom \u003Ccode>_cache_key\u003C\u002Fcode> format.\u003C\u002Fp>\n\u003Cp>📊 \u003Cstrong>Monitor Plugin and Nginx Cache Status\u003C\u002Fstrong>: Monitor plugin status, cache status, and Nginx status from the Status tab.\u003C\u002Fp>\n\u003Cp>📈 \u003Cstrong>Cache Coverage Ratio\u003C\u002Fstrong>: Live gauge in the WordPress dashboard widget showing the cache coverage ratio, based on the last preload snapshot. Refreshable on demand without a page reload.\u003C\u002Fp>\n\u003Cp>☁️ \u003Cstrong>Cloudflare APO Sync\u003C\u002Fstrong>: Automatically mirrors NPP purge actions to Cloudflare APO to keep edge cache synchronized with your Nginx cache.\u003C\u002Fp>\n\u003Cp>🔴 \u003Cstrong>Redis Object Cache Sync\u003C\u002Fstrong>: Coordinates cache invalidation between NPP and Redis Object Cache during NPP-driven operations. NPP Purge All and Preload workflows handle Redis flushing at the appropriate stage to ensure both cache layers stay aligned.\u003C\u002Fp>\n\u003Cp>🛒 \u003Cstrong>WooCommerce Auto-Purge\u003C\u002Fstrong>: Automatically purges Nginx cache when WooCommerce product stock quantity changes, stock status changes (in stock \u002F out of stock \u002F on backorder), or when an order is cancelled and stock is restored.\u003C\u002Fp>\n\u003Cp>🖲️ \u003Cstrong>WP-CLI Support\u003C\u002Fstrong>: Manage Nginx cache directly from the command line. Purge and preload cache, view status reports, inspect logs, update settings, flush cache, and manage scheduled tasks without accessing the WordPress admin dashboard.\u003C\u002Fp>\n\u003Cp>🔒 \u003Cstrong>Concurrent Purge Serialization\u003C\u002Fstrong>: Atomic lock mechanism prevents simultaneous purge operations from colliding, ensuring cache integrity during concurrent admin actions or background events.\u003C\u002Fp>\n\u003Cp>🧩 \u003Cstrong>Modular by Design\u003C\u002Fstrong>: Easily integrate with external scripts and automation tools.\u003C\u002Fp>\n\u003Cp>🖥️ \u003Cstrong>User-Friendly Interface\u003C\u002Fstrong>: Easy-to-use AJAX-powered settings, integrated into the WordPress admin bar and dashboard for quick access.\u003C\u002Fp>\n\u003Cp>📋 \u003Cstrong>Admin Notices and Logs\u003C\u002Fstrong>: Receive notifications and view logs for plugin status and all cache-related actions within the WordPress admin area.\u003C\u002Fp>\n\u003Cp>📧 \u003Cstrong>Email Notifications\u003C\u002Fstrong>: Receive email alerts upon completion of preload actions, with customizable templates to suit your needs.\u003C\u002Fp>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cp>This plugin is developed and maintained by Hasan CALISIR.\u003C\u002Fp>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>Prior to version 2.1.5, NPP optionally collected basic anonymous usage data when users explicitly opted in. As of version 2.1.5, all data collection and the opt-in mechanism have been completely removed. NPP collects no data whatsoever.\u003C\u002Fp>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>For support and assistance, please contact Hasan CALISIR at hasan.calisir@psauxit.com.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This plugin is licensed under the GPLv2 or later.For more information, visit the plugin development page: \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fpsaux-it\u002Fnginx-fastcgi-cache-purge-and-preload\" rel=\"nofollow ugc\">Nginx Cache Purge Preload\u003C\u002Fa>\u003C\u002Fp>\n","The most comprehensive free solution for managing Nginx (FastCGI, Proxy, SCGI, UWSGI) cache operations directly from your WordPress dashboard.",200,5957,"2026-06-08T04:58:00.000Z","7.4",[18,20,21,73,22],"preload","https:\u002F\u002Fgithub.com\u002Fpsaux-it\u002Fnginx-fastcgi-cache-purge-and-preload","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffastcgi-cache-purge-and-preload-nginx.2.1.7.zip",98,"2025-07-21 20:50:46",{"slug":79,"name":80,"version":81,"author":82,"author_profile":83,"description":84,"short_description":85,"active_installs":86,"downloaded":87,"rating":25,"num_ratings":32,"last_updated":88,"tested_up_to":89,"requires_at_least":90,"requires_php":50,"tags":91,"homepage":92,"download_link":93,"security_score":94,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"nginx-manager","NGINX Manager","1.3.4.4","Hpatoio","https:\u002F\u002Fprofiles.wordpress.org\u002Fhpatoio\u002F","\u003Cp>Each time an element of your blog is modified (post, page, media, custom post) its cached version, and of all the related elements (categories, archives and custom taxonomies) are deleted.\u003C\u002Fp>\n\u003Cp>In this way your cache has always the latest version of the page.\u003C\u002Fp>\n\u003Cp>Extra :\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Two extra HTTP header are added to the response so that you can see if the page you are viewing is cached and when it was cached.\u003C\u002Fli>\n\u003Cli>A logging system allow you to see which page were cached and when.\u003C\u002Fli>\n\u003Cli>You can add personal URLs to be purged when the post is modified\u003C\u002Fli>\n\u003Cli>Purge of future posts is handled with an external script.\u003C\u002Fli>\n\u003Cli>Integration with NextGEN Gallery plugin.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Credits :\u003C\u002Fp>\n\u003Cul>\n\u003Cli>This plugin is based on the structure of famous NextGEN Gallery plugin.\u003C\u002Fli>\n\u003C\u002Ful>\n","Easily purge Nginx cache. Each time a post is modified clear the cached version of the page and of all the related page.",20,6822,"2014-05-05T10:32:00.000Z","3.9.40","3.0",[18,20,21,22],"http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fnginx-manager\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnginx-manager.zip",85,{"slug":96,"name":97,"version":98,"author":99,"author_profile":100,"description":101,"short_description":102,"active_installs":103,"downloaded":104,"rating":105,"num_ratings":106,"last_updated":107,"tested_up_to":108,"requires_at_least":90,"requires_php":50,"tags":109,"homepage":113,"download_link":114,"security_score":115,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"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",[53,110,20,111,112],"fastcgi","permalinks","redis-cache","https:\u002F\u002Frtcamp.com\u002Fnginx-helper\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnginx-helper.2.3.5.zip",92,{"slug":117,"name":118,"version":119,"author":120,"author_profile":121,"description":122,"short_description":123,"active_installs":124,"downloaded":125,"rating":105,"num_ratings":126,"last_updated":127,"tested_up_to":14,"requires_at_least":128,"requires_php":71,"tags":129,"homepage":132,"download_link":133,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"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.",40000,2342003,26,"2026-06-24T17:42:00.000Z","5.0",[18,20,130,22,131],"proxy","varnish","https:\u002F\u002Fgithub.com\u002Fdvershinin\u002Fvarnish-http-purge","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fvarnish-http-purge.5.12.0.zip",{"error":135,"url":136,"statusCode":137,"statusMessage":138,"message":138},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Ffastcgi-cache-for-ploi\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":58,"versions":140},[141,147],{"version":6,"download_url":24,"svn_tag_url":142,"released_at":26,"has_diff":143,"diff_files_changed":144,"diff_lines":26,"trac_diff_url":145,"vulnerabilities":146,"is_current":135},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffastcgi-cache-for-ploi\u002Ftags\u002F1.0.1\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffastcgi-cache-for-ploi%2Ftags%2F1.0.0&new_path=%2Ffastcgi-cache-for-ploi%2Ftags%2F1.0.1",[],{"version":148,"download_url":149,"svn_tag_url":150,"released_at":26,"has_diff":143,"diff_files_changed":151,"diff_lines":26,"trac_diff_url":26,"vulnerabilities":152,"is_current":143},"1.0.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffastcgi-cache-for-ploi.1.0.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffastcgi-cache-for-ploi\u002Ftags\u002F1.0.0\u002F",[],[]]