[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f5kYbHGkIuiOsw-umUzbzdMh_YY9HIxcwzAHmaabhhhM":3,"$fpEQ_QRH064z35XPMPlQr8FacaMvlSE59u1hcga_jGGw":135,"$f6FSXJE9G8UhFzi_m-uIpi7jbhQqaGX0n94KyQ-rpOVM":140},{"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":35,"analysis":26,"fingerprints":26},"urls-most-wanted-for-litespeed-lscache","URLs Most Wanted for LiteSpeed LScache","1.0.0","imedes","https:\u002F\u002Fprofiles.wordpress.org\u002Fimedes\u002F","\u003Cp>URLs Most Wanted gives the LiteSpeed Cache crawler the information it is missing: which URLs are actually worth warming.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What this means for your cache warmup\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Warm URLs that real visitors actually request, not every URL that happens to exist.\u003C\u002Fli>\n\u003Cli>Reduce unnecessary crawler work and server stress, especially on shared hosting.\u003C\u002Fli>\n\u003Cli>Finish useful warmup work faster by avoiding pages with little or no real demand.\u003C\u002Fli>\n\u003Cli>Warm cacheable visitor paths that a normal SEO sitemap may not contain, such as pagination and filter URLs.\u003C\u002Fli>\n\u003Cli>Use the LiteSpeed cache engine and the built-in LiteSpeed Cache crawler more economically, with demand as the decision basis.\u003C\u002Fli>\n\u003Cli>Record demand asynchronously with exceptionally low overhead, without affecting page delivery or PageSpeed measurements.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>LiteSpeed Cache provides a crawler. The LiteSpeed cache engine provides the technical foundation for fast cached delivery. But the standard setup cannot answer one important question:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Which URLs should the crawler warm first, and which URLs are not worth the effort?\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The usual answer is the sitemap.\u003C\u002Fp>\n\u003Cp>A sitemap is useful. It tells search engines which URLs exist and which content should be discoverable. But that is an SEO question, not a cache-warmup question.\u003C\u002Fp>\n\u003Cp>A URL can exist without being wanted. A URL can be listed in a sitemap without ever being visited. And many URLs that visitors actually use, such as pagination, filtered listings or other cacheable visitor paths, may not belong in a search-engine sitemap at all.\u003C\u002Fp>\n\u003Cp>So why should cache warmup treat every sitemap URL as equally important?\u003C\u002Fp>\n\u003Cp>It should not.\u003C\u002Fp>\n\u003Cp>Every crawl creates work. The crawler has to request URLs, generate cache entries and use server resources while it does so. On a powerful dedicated server this may be tolerable. On shared hosting, unnecessary crawler work can become visible server stress that affects the website while the warmup is running.\u003C\u002Fp>\n\u003Cp>LiteSpeed Cache includes a Server Load Limit, but on shared hosting that value may reflect the load of the entire server rather than the load created by one account. Choosing a threshold cannot make irrelevant crawl work useful. The workload you can control directly is the number of URLs the crawler has to process.\u003C\u002Fp>\n\u003Cp>The consequence is simple:\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>The less relevant work a warmup performs, the more efficiently it can serve the URLs that matter.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>A sitemap may change when content changes, but it cannot adapt to actual demand. It does not know which URLs visitors use today, which pages they ignore, or whether a cacheable URL outside the SEO sitemap has become important.\u003C\u002Fp>\n\u003Cp>That is the gap URLs Most Wanted closes.\u003C\u002Fp>\n\u003Cp>URLs Most Wanted records visitor-requested URLs and stores them with their hit count, creation date and last modified date. From this real usage data, it creates an alternative sitemap for the built-in LiteSpeed Cache crawler.\u003C\u002Fp>\n\u003Cp>Instead of warming a generic list of URLs because they exist, the crawler can warm the URLs that have proven to be useful.\u003C\u002Fp>\n\u003Cp>This is not prediction. It is proven demand.\u003C\u002Fp>\n\u003Cp>The recorded hit counts also reveal which URLs have no demonstrated warmup value. That does not automatically make their content disposable, but it makes clear where cache-warmup resources are not creating a benefit.\u003C\u002Fp>\n\u003Cp>In practice, a large share of a website’s URLs may receive little or no traffic. Long-term traffic analysis can reveal that up to 70% of URLs are rarely or never requested. Warming those URLs again and again is not cache strategy. It is resource waste.\u003C\u002Fp>\n\u003Cp>URLs Most Wanted changes the economics of cache warmup:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Less unnecessary crawling.\u003C\u002Fli>\n\u003Cli>Less avoidable server load.\u003C\u002Fli>\n\u003Cli>More focus on URLs with real visitor value.\u003C\u002Fli>\n\u003Cli>Better coverage of cacheable URLs that the normal SEO sitemap does not represent.\u003C\u002Fli>\n\u003Cli>A faster path to a warm cache where it creates an actual benefit.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The plugin does not replace the LiteSpeed Cache crawler. It gives the crawler a better source of URLs.\u003C\u002Fp>\n\u003Ch4>Built for LiteSpeed Cache\u003C\u002Fh4>\n\u003Cp>URLs Most Wanted is designed specifically for LiteSpeed Enterprise or OpenLiteSpeed together with the LiteSpeed Cache for WordPress plugin.\u003C\u002Fp>\n\u003Cp>The plugin uses a LiteSpeed capability that other LiteSpeed-focused solutions do not normally expose. It keeps the effort required for recording visitor demand exceptionally low. URL recording happens asynchronously and is designed not to affect frontend delivery or PageSpeed measurements.\u003C\u002Fp>\n\u003Cp>The result is deliberately simple: UMW collects the demand data, LiteSpeed Cache performs the warmup, and your server spends its resources where they have a reason to be spent.\u003C\u002Fp>\n\u003Ch4>Administration\u003C\u002Fh4>\n\u003Cp>URLs Most Wanted is intentionally unobtrusive. The administration screen lets you review saved URLs, their hit counts and timestamps. You can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Delete individual URLs or purge all saved URLs.\u003C\u002Fli>\n\u003Cli>Blacklist URLs that must not be used for warmup.\u003C\u002Fli>\n\u003Cli>Reset hit counts.\u003C\u002Fli>\n\u003Cli>Generate the UMW sitemap manually.\u003C\u002Fli>\n\u003Cli>Generate the sitemap automatically once per day through WP-Cron.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Nothing changes in the way LiteSpeed Cache warms the cache. You simply configure its crawler to use the UMW sitemap instead of a generic SEO sitemap.\u003C\u002Fp>\n\u003Ch3>Requirements\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>LiteSpeed Cache for WordPress must be installed.\u003C\u002Fli>\n\u003Cli>PHP version 8.1 or higher.\u003C\u002Fli>\n\u003Cli>LiteSpeed Enterprise or OpenLiteSpeed web server.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Compatibility exclusions\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>UMW Capture cannot be activated on Quic.cloud or o2switch hosting.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>These are hard technical exclusions, not configuration issues:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Quic.cloud is not supported\u003C\u002Fstrong> because it does not provide the POST caching capability required by UMW Capture.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>o2switch (France) is not supported\u003C\u002Fstrong> because LiteSpeed operates only as an upstream proxy while the WordPress origin runs on Apache. UMW requires LiteSpeed Enterprise or OpenLiteSpeed at the origin.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>There is no supported workaround for either environment.\u003C\u002Fp>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>This plugin requests the public QUIC.cloud IP range list from https:\u002F\u002Fquic.cloud\u002Fips when it performs its server-side QUIC.cloud IP check. The IP range data is used to identify QUIC.cloud-served responses during LiteSpeed Cache validation.\u003C\u002Fp>\n\u003Cp>The request does not send visitor data, page content, credentials, cookies, WordPress options, or database data. As with any HTTPS request, QUIC.cloud receives the server IP address. The default WordPress HTTP user agent may also include the site URL and WordPress version.\u003C\u002Fp>\n\u003Cp>QUIC.cloud Terms of Use:\u003Cbr \u002F>\nhttps:\u002F\u002Fwww.quic.cloud\u002Fterms-of-use\u002F\u003C\u002Fp>\n\u003Cp>QUIC.cloud Privacy Policy:\u003Cbr \u002F>\nhttps:\u002F\u002Fwww.quic.cloud\u002Fprivacy-policy\u002F\u003C\u002Fp>\n","A demand-driven sitemap for LiteSpeed Cache warmup. Record the URLs visitors actually use and warm only what people need.",0,83,"2026-07-11T07:53:00.000Z","7.1","6.2","8.1",[18,19,20,21,22],"cache","crawler","litespeed","sitemap","warmup","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Furls-most-wanted-for-litespeed-lscache.1.0.0.zip",100,null,"2026-07-22T17:31:50.256Z","no_bundle",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":25,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},1,30,94,"2026-08-29T14:07:27.671Z",[36,55,76,97,116],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":25,"num_ratings":46,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":50,"tags":51,"homepage":53,"download_link":54,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"boring-cache-warmup-lite","Boring Cache Warmup Lite","0.4.7","chriskubisch","https:\u002F\u002Fprofiles.wordpress.org\u002Fchriskubisch\u002F","\u003Cp>Boring Cache Warmup Lite is a lightweight, practical WordPress plugin that warms up your cache. It runs from your own site, does not connect to external services, and keeps the job boring, transparent, and privacy-friendly.\u003C\u002Fp>\n\u003Cp>Boring tools, because they simply work.\u003C\u002Fp>\n\u003Cp>The plugin does not use external services, tracking, cloud queues, external APIs, or CDN-hosted assets.\u003C\u002Fp>\n\u003Cp>It is intentionally lightweight: small plugin files, local requests, conservative batches, and no extra frontend baggage.\u003C\u002Fp>\n\u003Cp>Current free version features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Tools submenu page in the WordPress admin.\u003C\u002Fli>\n\u003Cli>Dashboard widget with a direct warmup button.\u003C\u002Fli>\n\u003Cli>Lightweight design with small plugin files and no external runtime dependencies.\u003C\u002Fli>\n\u003Cli>Nonce-protected AJAX calls.\u003C\u002Fli>\n\u003Cli>Published pages, posts, products, and public custom post types.\u003C\u002Fli>\n\u003Cli>Server-friendly default pacing to reduce timeout and overload risk.\u003C\u002Fli>\n\u003Cli>Progress bar and status messages.\u003C\u002Fli>\n\u003Cli>Manual stop button.\u003C\u002Fli>\n\u003Cli>Compact progress by default, with an optional detailed URL log showing status, duration, and HTML payload size.\u003C\u002Fli>\n\u003Cli>Technical post types such as Elementor templates and Astra Advanced Hooks are excluded by default.\u003C\u002Fli>\n\u003C\u002Ful>\n","A lightweight, privacy-friendly WordPress cache warmup tool. No external services, no drama.",20,245,2,"2026-07-07T18:51:00.000Z","7.0.2","6.1","8.0",[18,19,52,22],"performance","https:\u002F\u002Fboringworks.eu\u002Fboring-cache-warmup\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fboring-cache-warmup-lite.0.4.7.zip",{"slug":56,"name":57,"version":58,"author":59,"author_profile":60,"description":61,"short_description":62,"active_installs":63,"downloaded":64,"rating":11,"num_ratings":11,"last_updated":65,"tested_up_to":66,"requires_at_least":67,"requires_php":68,"tags":69,"homepage":23,"download_link":73,"security_score":74,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":75},"xml-cache","XML Cache","2.0.0","GoSuccess","https:\u002F\u002Fprofiles.wordpress.org\u002Fgosuccess\u002F","\u003Cp>This plugin creates an XML sitemap with all posts, pages, categories, archives and tag pages, regardless of whether they are excluded from search engine indexing or not.\u003C\u002Fp>\n\u003Cp>The advantage over a normal sitemap is that no pages are excluded from the sitemap. You can specify the XML cache sitemap in your cache plugin, such as \u003Ca href=\"https:\u002F\u002Fde.wordpress.org\u002Fplugins\u002Flitespeed-cache\u002F\" rel=\"nofollow ugc\">LiteSpeed Cache\u003C\u002Fa>, to fully warm up your website cache.\u003C\u002Fp>\n","Generates an XML sitemap for cache plugins.",10,2090,"2025-08-28T06:08:00.000Z","6.8.5","6.0","8.2",[18,70,71,21,72],"litespeed-cache","pagespeed","xml","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fxml-cache.2.0.0.zip",92,"2026-03-15T15:16:48.613Z",{"slug":77,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":84,"downloaded":85,"rating":25,"num_ratings":86,"last_updated":87,"tested_up_to":88,"requires_at_least":23,"requires_php":23,"tags":89,"homepage":94,"download_link":95,"security_score":33,"vuln_count":46,"unpatched_count":11,"last_vuln_date":96,"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",[90,91,20,92,93],"automatic-purge","cache-purge","nginx","web-performance","https:\u002F\u002Fmerlot.digital","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftnc-toolbox.2.1.4.zip","2025-11-29 00:00:00",{"slug":98,"name":99,"version":100,"author":101,"author_profile":102,"description":103,"short_description":104,"active_installs":105,"downloaded":106,"rating":25,"num_ratings":46,"last_updated":107,"tested_up_to":108,"requires_at_least":109,"requires_php":110,"tags":111,"homepage":113,"download_link":114,"security_score":115,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"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,9514,"2021-12-21T21:00:00.000Z","5.8.13","3.0","7.4",[18,20,92,112],"purge","https:\u002F\u002Fwpinfo.net","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-purge-helper.0.1.4.zip",85,{"slug":117,"name":118,"version":119,"author":120,"author_profile":121,"description":122,"short_description":123,"active_installs":105,"downloaded":124,"rating":125,"num_ratings":126,"last_updated":127,"tested_up_to":128,"requires_at_least":129,"requires_php":23,"tags":130,"homepage":133,"download_link":134,"security_score":74,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"warm-cache","Warm Cache","4.1.1","ramon fincken","https:\u002F\u002Fprofiles.wordpress.org\u002Framon-fincken\u002F","\u003Cp>Crawls your website-pages based on any XML sitemap. If you have a caching plugin this will keep your cache warm.\u003Cbr \u002F>\nSpeeds up your site.\u003Cbr \u002F>\nCompatible with following elements: \u003C sitemap > \u003C url >\u003Cbr \u002F>\nAll urls in your sitemap will be visited by the plugin to keep the cache up to date.\u003Cbr \u002F>\nWill show average page load times and pages visited.\u003C\u002Fp>\n\u003Cp>Needs google XML sitemap to read the generated XML file.\u003Cbr \u002F>\nNeeds a cronjob (wget or curl) to call the plugin. You need to setup the cronjob yourself! (Or ask your sysadmin to help you).\u003Cbr \u002F>\n* Coding by: \u003Ca href=\"https:\u002F\u002Fwww.mijnpress.nl\" rel=\"nofollow ugc\">MijnPress.nl\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fmastodon.social\u002F@ramonfincken\" rel=\"nofollow ugc\">Mastodon profile\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Framon-fincken\u002F\" rel=\"nofollow ugc\">More plugins\u003C\u002Fa>\u003Cbr \u002F>\n* Crawl script idea by \u003Ca href=\"http:\u002F\u002Fblogs.tech-recipes.com\u002Fjohnny\u002F2006\u002F09\u002F17\u002Fhandling-the-digg-effect-with-wordpress-caching\u002F\" rel=\"nofollow ugc\">http:\u002F\u002Fblogs.tech-recipes.com\u002Fjohnny\u002F2006\u002F09\u002F17\u002Fhandling-the-digg-effect-with-wordpress-caching\u002F\u003C\u002Fa>\u003C\u002Fp>\n","Crawls your website-pages based on google XML sitemap. If you have a caching plugin this will keep your cache warm. Speeds up your site.",30032,86,19,"2024-12-02T15:16:00.000Z","6.7.5","3.5",[18,131,21,132,72],"keep","warm","https:\u002F\u002Fwww.autowarmcache.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwarm-cache.4.1.1.zip",{"error":136,"url":137,"statusCode":138,"statusMessage":139,"message":139},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Furls-most-wanted-for-litespeed-lscache\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":31,"versions":141},[142],{"version":6,"download_url":24,"svn_tag_url":143,"released_at":26,"has_diff":144,"diff_files_changed":145,"diff_lines":26,"trac_diff_url":26,"vulnerabilities":146,"is_current":136},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Furls-most-wanted-for-litespeed-lscache\u002Ftags\u002F1.0.0\u002F",false,[],[]]