[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f8Vcr2NZVCj6jBh6fMDi0lQO1uJVY6041FTBqnix62Vc":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":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":38,"analysis":135,"fingerprints":201},"uncache-script","Uncache Script","1.2.0","todiadiyatmo","https:\u002F\u002Fprofiles.wordpress.org\u002Ftodiadiatmo\u002F","\u003Cp>Uncache Script is a small plugin to uncache all your style & script after you editing them. So they don’t keep any cache in your WordPress site 🙂\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features :\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Uncache all your script and style\u003C\u002Fli>\n\u003Cli>Dead simple to use, just one-click\u003C\u002Fli>\n\u003Cli>Zero configuration\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Plugin Demo\u003C\u002Fstrong>\u003Cbr \u002F>\nYou can try the plugin on this url: http:\u002F\u002Fcoba.tonjoostudio.com\u003C\u002Fp>\n\u003Cul>\n\u003Cli>username: coba\u003C\u002Fli>\n\u003Cli>password: 123456\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>*If you have any questions, comment, customization request or suggestion please contact us via our \u003Ca href=\"https:\u002F\u002Fforum.tonjoostudio.com\u002Fthread-category\u002Funcache-script\u002F\" title=\"Tonjoo Forum\" rel=\"friend nofollow ugc\">Tonjoo Forum\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Find more detail and guide please visit \u003Ca href=\"https:\u002F\u002Ftonjoostudio.com\u002Faddons\u002Funcache-script\u002F?utm_source=wp_org&utm_medium=link&utm_campaign=uc\" title=\"visit Tonjoo plugin website\" rel=\"friend nofollow ugc\">Uncache Script Manual Page\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Or you can find our best plugins at \u003Ca href=\"https:\u002F\u002Ftonjoostudio.com\u002F\" title=\"Tonjoo Studio\" rel=\"friend nofollow ugc\">Tonjoo Studio\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>We can also modify your WordPress plugins according to your needs. Visit us: \u003Ca href=\"https:\u002F\u002Ftonjoo.com\" title=\"Visit Tonjoo Dev Website\" rel=\"friend nofollow ugc\">Tonjoo WordPress Developer\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Usage Instruction\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Install the plugin.\u003C\u002Fli>\n\u003Cli>In the Admin Panel, Go to Setting -> Uncache Script.\u003C\u002Fli>\n\u003Cli>Click Uncache Script to uncache\u003C\u002Fli>\n\u003C\u002Fol>\n","Force your scripts and style to uncache",300,6501,0,"2015-08-20T08:45:00.000Z","4.3.34","3.0.3","",[19,20,21,22,23],"cache","caching","page-cache","wp-cache","wp-super-cache","http:\u002F\u002Fwww.tonjoo.com\u002Funcache-script\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Funcache-script.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":34,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},"todiadiatmo",4,7350,87,956,70,"2026-04-03T19:56:33.716Z",[39,60,78,98,118],{"slug":23,"name":40,"version":16,"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":51,"requires_php":52,"tags":53,"homepage":55,"download_link":56,"security_score":57,"vuln_count":58,"unpatched_count":13,"last_vuln_date":59,"fetched_at":28},"WP Super Cache","Automattic","https:\u002F\u002Fprofiles.wordpress.org\u002Fautomattic\u002F","\u003Cp>This plugin generates static html files from your dynamic WordPress blog.  After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts.\u003C\u002Fp>\n\u003Cp>The static html files will be served to the vast majority of your users:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Users who are not logged in.\u003C\u002Fli>\n\u003Cli>Users who have not left a comment on your blog.\u003C\u002Fli>\n\u003Cli>Or users who have not viewed a password protected post.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>99% of your visitors will be served static html files. One cached file can be served thousands of times. Other visitors will be served custom cached files tailored to their visit. If they are logged in, or have left comments those details will be displayed and cached for them.\u003C\u002Fp>\n\u003Cp>The plugin serves cached files in 3 ways (ranked by speed):\u003C\u002Fp>\n\u003Col>\n\u003Cli>Expert. The fastest method is by using Apache mod_rewrite (or whatever similar module your web server supports) to serve “supercached” static html files. This completely bypasses PHP and is extremely quick. If your server is hit by a deluge of traffic it is more likely to cope as the requests are “lighter”. This does require the Apache mod_rewrite module (which is probably installed if you have custom permalinks) and a modification of your .htaccess file which is risky and may take down your site if modified incorrectly.\u003C\u002Fli>\n\u003Cli>Simple. Supercached static files can be served by PHP and this is the recommended way of using the plugin. The plugin will serve a “supercached” file if it exists and it’s almost as fast as the mod_rewrite method. It’s easier to configure as the .htaccess file doesn’t need to be changed. You still need a custom permalink. You can keep portions of your page dynamic in this caching mode.\u003C\u002Fli>\n\u003Cli>WP-Cache caching. This is mainly used to cache pages for known users, URLs with parameters and feeds. Known users are logged in users, visitors who leave comments or those who should be shown custom per-user data. It’s the most flexible caching method and slightly slower. WP-Cache caching will also cache visits by unknown users if supercaching is disabled. You can have dynamic parts to your page in this mode too. This mode is always enabled but you can disable caching for known users, URLs with parameters, or feeds separately. Set the constant “DISABLE_SUPERCACHE” to 1 in your wp-config.php if you want to only use WP-Cache caching.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>If you’re not comfortable with editing PHP files then use simple mode. It’s easy to set up and very fast.\u003C\u002Fp>\n\u003Ch3>Recommended Settings\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Simple caching.\u003C\u002Fli>\n\u003Cli>Compress pages.\u003C\u002Fli>\n\u003Cli>Don’t cache pages for known users.\u003C\u002Fli>\n\u003Cli>Cache rebuild.\u003C\u002Fli>\n\u003Cli>CDN support.\u003C\u002Fli>\n\u003Cli>Extra homepage checks.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Garbage collection is the act of cleaning up cache files that are out of date and stale. There’s no correct value for the expiry time but a good starting point is 1800 seconds.\u003C\u002Fp>\n\u003Cp>Consider deleting the contents of the “Rejected User Agents” text box and allow search engines to cache files for you.\u003C\u002Fp>\n\u003Cp>Preload as many posts as you can and enable “Preload Mode”. Garbage collection of old cached files will be disabled. If you don’t care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren’t recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. Afterwards a garbage collection of all old files is performed to clean out stale cache files.\u003Cbr \u002F>\nEven with preload mode enabled cached files will still be deleted when posts are modified or comments made.\u003C\u002Fp>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Active development of this plugin is handled \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FAutomattic\u002Fwp-super-cache\" rel=\"nofollow ugc\">on GitHub\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Translation of the plugin into different languages is on the \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fwp-super-cache\" rel=\"nofollow ugc\">translation page\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Documentation\u003C\u002Fh3>\n\u003Cp>If you need more information than the following, you can have a look at \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FAutomattic\u002Fwp-super-cache\u002Fwiki\" rel=\"nofollow ugc\">the wiki\u003C\u002Fa> or the \u003Ca href=\"https:\u002F\u002Fodd.blog\u002Fwp-super-cache-developers\u002F\" rel=\"nofollow ugc\">Developer documentation\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Preloading\u003C\u002Fh4>\n\u003Cp>You can generate cached files for the posts, categories and tags of your site by preloading. Preloading will visit each page of your site generating a cached page as it goes along, just like any other visitor to the site. Due to the sequential nature of this function, it can take some time to preload a complete site if there are many posts.\u003Cbr \u002F>\nTo make preloading more effective it can be useful to disable garbage collection so that older cache files are not deleted. This is done by enabling “Preload Mode” in the settings. Be aware however, that pages will go out of date eventually but that updates by submitting comments or editing posts will clear portions of the cache.\u003C\u002Fp>\n\u003Ch4>Garbage Collection\u003C\u002Fh4>\n\u003Cp>Your cache directory fills up over time, which takes up space on your server. If space is limited or billed by capacity, or if you worry that the cached pages of your site will go stale then garbage collection has to be done. Garbage collection happens on a regular basis and deletes old files in the cache directory. On the advanced settings page you can specify:\u003Cbr \u002F>\n1. Cache timeout. How long cache files are considered fresh for. After this time they are stale and can be deleted.\u003Cbr \u002F>\n2. Scheduler. Setup how often garbage collection should be done.\u003Cbr \u002F>\n3. Notification emails. You can be informed on garbage collection job progress.\u003Cbr \u002F>\nThere’s no right or wrong settings for garbage collection. It depends on your own site.\u003Cbr \u002F>\nIf your site gets regular updates, or comments then set the timeout to 1800 seconds, and set the timer to 600 seconds.\u003Cbr \u002F>\nIf your site is mostly static you can disable garbage collection by entering 0 as the timeout, or use a really large timeout value.\u003C\u002Fp>\n\u003Cp>The cache directory, usually wp-content\u002Fcache\u002F is only for temporary files. Do not ever put important files or symlinks to important files or directories in that directory. They will be deleted if the plugin has write access to them.\u003C\u002Fp>\n\u003Ch4>CDN\u003C\u002Fh4>\n\u003Cp>A Content Delivery Network (CDN) is usually a network of computers situated around the world that will serve the content of your website faster by using servers close to you. Static files like images, Javascript and CSS files can be served through these networks to speed up how fast your site loads. You can also create a “poor man’s CDN” by using a sub domain of your domain to serve static files too.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fossdl-cdn-off-linker\u002F\" rel=\"ugc\">OSSDL CDN off-linker\u003C\u002Fa> has been integrated into WP Super Cache to provide basic CDN support. It works by rewriting the URLs of files (excluding .php files) in wp-content and wp-includes on your server so they point at a different hostname. Many CDNs support \u003Ca href=\"https:\u002F\u002Fwww.google.com\u002Fsearch?hl=en&q=%22origin+pull%22\" rel=\"nofollow ugc\">origin pull\u003C\u002Fa>. This means the CDN will download the file automatically from your server when it’s first requested, and will continue to serve it for a configurable length of time before downloading it again from your server.\u003C\u002Fp>\n\u003Cp>Configure this on the “CDN” tab of the plugin settings page. This is an advanced technique and requires a basic understanding of how your webserver or CDNs work. Please be sure to clear the file cache after you configure the CDN.\u003C\u002Fp>\n\u003Ch4>REST API\u003C\u002Fh4>\n\u003Cp>There are now REST API endpoints for accessing the settings of this plugin. You’ll need to be authenticated as an admin user with permission to view the settings page to use it. This has not been documented yet but you can find all the code that deals with this in the “rest” directory.\u003C\u002Fp>\n\u003Ch4>Custom Caching\u003C\u002Fh4>\n\u003Cp>It is now possible to hook into the caching process using the add_cacheaction() function.\u003C\u002Fp>\n\u003Cp>Three hooks are available:\u003C\u002Fp>\n\u003Col>\n\u003Cli>‘wp_cache_get_cookies_values’ – modify the key used by WP Cache.\u003C\u002Fli>\n\u003Cli>‘add_cacheaction’ – runs in phase2. Allows a plugin to add WordPress hooks.\u003C\u002Fli>\n\u003Cli>‘cache_admin_page’ – runs in the admin page. Use it to modify that page, perhaps by adding new configuration options.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>There is one regular WordPress filter too. Use the “do_createsupercache” filter\u003Cbr \u002F>\nto customize the checks made before caching. The filter accepts one parameter.\u003Cbr \u002F>\nThe output of WP-Cache’s wp_cache_get_cookies_values() function.\u003C\u002Fp>\n\u003Cp>WP Super Cache has its own plugin system. This code is loaded when WP Super Cache loads and can be used to change how caching is done. This is before most of WordPress loads so some functionality will not be available. Plugins can be located anywhere that PHP can load them. Add your own plugin either:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>by putting your plugin in the wp-content\u002Fplugins\u002Fwp-super-cache-plugins directory, or\u003C\u002Fli>\n\u003Cli>by calling wpsc_add_plugin( $name ) where $name is the full filename and path to the plugin. You only need to call that function once to add it. Use wpsc_delete_plugin( $name ) to remove it from the list of loaded plugins.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The cookies WP Super Cache uses to identify “known users” can be modified now by adding the names of those cookies to a list in the plugin configuration. Use wpsc_add_cookie( $name ) to add a new cookie, and wpsc_delete_cookie( $name ) to remove it. The cookie names also modify the mod_rewrite rules used by the plugin but I recommend using Simple mode caching to avoid complications with updating the .htaccess file.\u003Cbr \u002F>\nThe cookie name and value are used to differenciate users so you can have one cookie, but different values for each type of user on your site for example. They’ll be served different cache files.\u003C\u002Fp>\n\u003Cp>See \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FAutomattic\u002Fwp-super-cache\u002Fblob\u002F4cda5c0f2218e40e118232b5bf22d227fb3206b7\u002Fplugins\u002Fsearchengine.php\" rel=\"nofollow ugc\">plugins\u002Fsearchengine.php\u003C\u002Fa> as an example I use for my \u003Ca href=\"https:\u002F\u002Fodd.blog\u002Fno-adverts-for-friends\u002F\" rel=\"nofollow ugc\">No Adverts for Friends\u003C\u002Fa> plugin.\u003C\u002Fp>\n\u003Ch3>Troubleshooting\u003C\u002Fh3>\n\u003Cp>If things don’t work when you installed the plugin here are a few things to check:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Is wp-content writable by the web server?\u003C\u002Fli>\n\u003Cli>Is there a wp-content\u002Fwp-cache-config.php ? If not, copy the file wp-super-cache\u002Fwp-cache-config-sample.php to wp-content\u002Fwp-cache-config.php and make sure WPCACHEHOME points at the right place.\u003C\u002Fli>\n\u003Cli>Is there a wp-content\u002Fadvanced-cache.php ? If not, then you must copy wp-super-cache\u002Fadvanced-cache.php into wp-content\u002F. You must edit the file and change the path so it points at the wp-super-cache folder.\u003C\u002Fli>\n\u003Cli>If pages are not cached at all, remove wp-content\u002Fadvanced-cache.php and recreate it, following the advice above.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Make sure the following line is in wp-config.php and it is ABOVE the “require_once(ABSPATH.’wp-settings.php’);” line:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WP_CACHE', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>Try the Settings->WP Super Cache page again and enable cache.\u003C\u002Fli>\n\u003Cli>Look in wp-content\u002Fcache\u002Fsupercache\u002F. Are there directories and files there?\u003C\u002Fli>\n\u003Cli>Anything in your php error_log?\u003C\u002Fli>\n\u003Cli>If your browser keeps asking you to save the file after the super cache is installed you must disable Super Cache compression. Go to the Settings->WP Super Cache page and disable it there.\u003C\u002Fli>\n\u003Cli>The plugin does not work very well when PHP’s safe mode is active. This must be disabled by your administrator.\u003C\u002Fli>\n\u003Cli>If pages are randomly super cached and sometimes not, your blog can probably be viewed with and without the “www” prefix on the URL. You should choose one way and install the \u003Ca href=\"http:\u002F\u002Ftxfx.net\u002Fcode\u002Fwordpress\u002Fenforce-www-preference\u002F\" rel=\"nofollow ugc\">Enforce www preference\u003C\u002Fa> plugin if you are using an old WordPress install. The latest versions redirect themselves (you should always be running the latest version of WordPress anyway!)\u003C\u002Fli>\n\u003Cli>Private Server users at Dreamhost should edit wp-content\u002Fwp-cache-config.php and set the cache dir to “\u002Ftmp\u002F” if they are getting errors about increasing CPU usage. See this \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002F145895?replies=42\" rel=\"ugc\">discussion\u003C\u002Fa> for more.\u003C\u002Fli>\n\u003Cli>File locking errors such as “failed to acquire key 0x152b: Permission denied in…” or “Page not cached by WP Super Cache. Could not get mutex lock.” are a sign that you may have to use file locking. Edit wp-content\u002Fwp-cache-config.php and uncomment “$use_flock = true” or set $sem_id to a different value. You can also disable file locking from the Admin screen as a last resort.\u003C\u002Fli>\n\u003Cli>Make sure cache\u002Fwp_cache_mutex.lock is writable by the web server if using coarse file locking.\u003C\u002Fli>\n\u003Cli>The cache folder cannot be put on an NFS or Samba or NAS share. It has to be on a local disk. File locking and deleting expired files will not work properly unless the cache folder is on the local machine.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Garbage collection of old cache files won’t work if WordPress can’t find wp-cron.php. If your hostname resolves to 127.0.0.1 it could be preventing the garbage collection from working. Check your access_logs for wp-cron.php entries. Do they return a 404 (file not found) or 200 code? If it’s 404 or you don’t see wp-cron.php anywhere WordPress may be looking for that script in the wrong place. You should speak to your server administator to correct this or edit \u002Fetc\u002Fhosts on Unix servers and remove the following line. Your hostname must resolve to the external IP address other servers on the network\u002FInternet use. See http:\u002F\u002Fyoast.com\u002Fwp-cron-issues\u002F for more. A line like “127.0.0.1 localhost localhost.localdomain” is ok.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>127.0.0.1 example.com\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>If old pages are being served to your visitors via the supercache, you may be missing Apache modules (or their equivalents if you don’t use Apache). 3 modules are required: mod_mime, mod_headers and mod_expires. The last two are especially important for making sure browsers load new versions of existing pages on your site.\u003C\u002Fli>\n\u003Cli>The error message, “WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content\u002Fadvanced-cache.php must be fixed!” appears at the end of every page. Open the file wp-content\u002Fadvanced-cache.php in your favourite editor. Is the path to wp-cache-phase1.php correct? This file will normally be in wp-content\u002Fplugins\u002Fwp-super-cache\u002F. If it is not correct the caching engine will not load.\u003C\u002Fli>\n\u003Cli>Caching doesn’t work. The timestamp on my blog keeps changing when I reload. Check that the path in your .htaccess rules matches where the supercache directory is. You may have to hardcode it. Try disabling supercache mode.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If supercache cache files are generated but not served, check the permissions on all your wp-content\u002Fcache\u002Fsupercache folders (and each of wp-content cache and supercache folders) and wp-content\u002Fcache\u002F.htaccess. If your PHP runs as a different user to Apache and permissions are strict Apache may not be able to read the PHP generated cache files. To fix you must add the following line to your wp-config.php (Add it above the WP_CACHE define.) Then clear your cache.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>umask( 0022 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If you see garbage in your browser after enabling compression in the plugin, compression may already be enabled in your web server. In Apache you must disable mod_deflate, or in PHP zlib compression may be enabled. You can disable that in three ways. If you have root access, edit your php.ini and find the zlib.output_compression setting and make sure it’s “Off” or add this line to your .htaccess:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>php_flag zlib.output_compression off\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If that doesn’t work, add this line to your wp-config.php:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>ini_set('zlib.output_compression', 0);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>The “white screen of death” or a blank page  when you visit your site is almost always caused by a PHP error but \u003Ca href=\"http:\u002F\u002Fwww.johnberns.com\u002F2010\u002F03\u002F19\u002Fwp-super-cache-blank-page-problem-fixed\u002F\" rel=\"nofollow ugc\">it may also be caused by APC\u003C\u002Fa>. Disable that PHP extension if you have trouble and replace with eAccelerator or Xcache.\u003C\u002Fli>\n\u003Cli>After uninstalling, your permalinks may break if you remove the WordPress mod_rewrite rules too. Regenerate those rules by visiting the Settings->Permalink page and saving that form again.\u003C\u002Fli>\n\u003Cli>If your blog refuses to load make sure your wp-config.php is correct. Are you missing an opening or closing PHP tag?\u003C\u002Fli>\n\u003Cli>Your front  …\u003C\u002Fli>\n\u003C\u002Fol>\n","A very fast caching engine for WordPress that produces static html files.",1000000,62208732,86,1341,"2025-11-11T16:21:00.000Z","6.9.4","6.7","7.2",[19,20,54,22,23],"performance","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-super-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-super-cache.3.0.3.zip",95,12,"2022-10-03 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":13,"num_ratings":13,"last_updated":70,"tested_up_to":71,"requires_at_least":72,"requires_php":17,"tags":73,"homepage":75,"download_link":76,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":77},"wpmk-cache","WPMK Cache","1.0.1","WPMK","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpmkorg\u002F","\u003Cp>WPMK Cache easiest and fastest WordPress Cache plugin. it is light-weight plugin you need to just install and active its simple option and it will work for you. it will help you in \u003Ca href=\"https:\u002F\u002Fwww.seoanalyzeronline.com\u002F\" rel=\"nofollow ugc\">SEO\u003C\u002Fa>.\u003C\u002Fp>\n","The easiest, fastest, most light-weight WordPress Cache plugin available.",10,1211,"2022-06-19T14:48:00.000Z","6.0.11","3.3",[19,20,74,22,23],"w3tc","http:\u002F\u002Fwww.wpmk.org\u002Fplugins\u002Fwpmk-cache","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwpmk-cache.zip","2026-03-15T14:54:45.397Z",{"slug":79,"name":80,"version":81,"author":82,"author_profile":83,"description":84,"short_description":85,"active_installs":86,"downloaded":87,"rating":88,"num_ratings":89,"last_updated":90,"tested_up_to":50,"requires_at_least":91,"requires_php":92,"tags":93,"homepage":17,"download_link":95,"security_score":57,"vuln_count":96,"unpatched_count":13,"last_vuln_date":97,"fetched_at":28},"breeze","Breeze Cache","2.4.1","Cloudways","https:\u002F\u002Fprofiles.wordpress.org\u002Fcloudways\u002F","\u003Cp>Breeze is a free, simple (yet powerful) and user-friendly caching plugin developed by the Cloudways team. It offers various options to optimize WordPress site performance at various levels. It works equally great with WordPress, WordPress with WooCommerce and WordPress Multisite.\u003C\u002Fp>\n\u003Cp>Breeze excels in the following areas:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Performance:\u003C\u002Fstrong> Breeze improves website speed and resource optimization. Other features include file level cache system, database cleanup, minification, support for Varnish cache and simplified CDN integration options.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Convenience:\u003C\u002Fstrong> Breeze is easy to install and configure directly from WordPress. Configuring Breeze is easy and most of the default options work well right out of the box. The recommended settings should work on all your WordPress websites seamlessly.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Simplicity:\u003C\u002Fstrong> Breeze is designed to be simple for all users. Just install and activate the plugin and you’ll see the results instantaneously.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>What makes Breeze Cache Plugin awesome is that it comes with builtin support for Varnish. If Varnish is not installed on your servers, Breeze will utilize its internal cache mechanism to boost up your WordPress site performance.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>FEATURES\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Seamless integration with Varnish Cache for efficient content delivery. No manual adjustments needed – all settings come pre-configured for your convenience.\u003C\u002Fli>\n\u003Cli>Optimize performance using Cloudflare’s caching capabilities. No specific Breeze configurations are needed – it works out of the box.\u003C\u002Fli>\n\u003Cli>Effortlessly integrate your preferred Content Delivery Network (CDN) for global content distribution with Breeze instead of using the the CDN providers’ plugins.\u003C\u002Fli>\n\u003Cli>Trim WordPress database bloat effortlessly. Breeze’s Database Options optimize and declutter your database, boosting performance by removing unneeded data like post revisions and trashed content.\u003C\u002Fli>\n\u003Cli>Take command over caching exclusions. With Breeze, you have the power to prevent specific URLs, JS files, and CSS files from being cached.\u003C\u002Fli>\n\u003Cli>Achieve smaller page sizes and faster load times through HTML, CSS, and JavaScript minification, including inline CSS and JavaScript minification.\u003C\u002Fli>\n\u003Cli>Load images when they’re visible, not all at once, for faster webpage performance by implementing lazy loading for images.\u003C\u002Fli>\n\u003Cli>Load JS files with deferred loading, enhancing overall performance.\u003C\u002Fli>\n\u003Cli>Supercharge your site’s speed with Breeze’s advanced preloading features: load fonts early, quicken link clicks, and enhance DNS requests for a seamless user experience.\u003C\u002Fli>\n\u003Cli>Master real-time interactions with Breeze’s Heartbeat API management. Fine-tune notifications, sales data, autosaves, and more to optimize WordPress website performance by adjusting API call frequencies.\u003C\u002Fli>\n\u003Cli>Effortlessly manage Breeze settings using Import\u002FExport. Download your configurations as a .json file for backup, or effortlessly import existing settings to quickly fine-tune your optimization.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Support:\u003C\u002Fstrong> We love to provide support! Post your questions on the WordPress.org support forums, or if you are a Cloudways Customer you may ask questions on the \u003Ca href=\"https:\u002F\u002Fcommunity.cloudways.com\u002F\" rel=\"nofollow ugc\">Cloudways Community Forum\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Requirements\u003C\u002Fh3>\n\u003Cp>PHP 7.4, PHP 8 recommended for better performance, WordPress 6.0+\u003C\u002Fp>\n","Breeze is a caching plugin developed by Cloudways. Breeze uses advance caching systems to improve site loading times exponentially.",400000,13597399,72,125,"2026-03-03T09:14:00.000Z","6.0","7.4",[19,20,94,54,22],"cdn","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbreeze.2.4.1.zip",8,"2026-02-18 15:43:14",{"slug":99,"name":100,"version":101,"author":102,"author_profile":103,"description":104,"short_description":105,"active_installs":106,"downloaded":107,"rating":108,"num_ratings":109,"last_updated":110,"tested_up_to":50,"requires_at_least":111,"requires_php":17,"tags":112,"homepage":115,"download_link":116,"security_score":117,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"wp-super-cache-clear-cache-menu","Clear All Cache for WP Super Cache","2.4","apasionados","https:\u002F\u002Fprofiles.wordpress.org\u002Fapasionados\u002F","\u003Cp>The plugin clears completely the cache from WP Super Cache, directly from the admin menu.\u003C\u002Fp>\n\u003Cp>We created this plugin, in order to be able to clear the cache completely  from the admin menu and not having to navigate to CONTENTS tab in WP Super Cache Settings.\u003C\u002Fp>\n\u003Cp>In some configuration WP Super Cache shows a menu entry to empty the cache in the menu, but it only empties the cache from the current page. See: \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fplugin-wp-super-cache-menu-delete-cache-doesnt-work-but-on-contents-page-it-does\" rel=\"ugc\">The “Delete Cache” button on the admin menu only deletes the cache for the current page.\u003C\u002Fa>\u003Cbr \u002F>\nNevertheless in the majority of the sites that have WP Super Cache installed it doesn’t display this menu entry.\u003C\u002Fp>\n\u003Cp>Please note that this menu option is only visible for WordPress ADMINISTRATORS.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>This is an add-on to WP SUPER CACHE:\u003C\u002Fstrong>\u003Cbr \u002F>\n  Please keep in mind that this plugin is an add-on to the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-super-cache\u002F\" rel=\"ugc\">WP SUPER CACHE\u003C\u002Fa> plugin. You need to install and activate WP SUPER CACHE so that this add-on works.\u003C\u002Fp>\n\u003Cp>If you are having trouble with this plugin, feel free to use the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fwp-super-cache-clear-cache-menu\" rel=\"ugc\">Clear All Cache for WP Super Cache Support\u003C\u002Fa>. If you are having problems with the WP SUPER CACHE plugin, you should ask for support at \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fwp-super-cache\" rel=\"ugc\">WP Super Cache Support\u003C\u002Fa>.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>What can I do with this plugin?\u003C\u002Fh4>\n\u003Cp>The plugin clears completely the cache from WP Super Cache, directly from the admin menu.\u003C\u002Fp>\n\u003Ch4>Clear All Cache for WP Super Cache Plugin in your Language!\u003C\u002Fh4>\n\u003Cp>This first release is avaliable in English and Spanish. In the languages folder we have included the necessarry files to translate this plugin.\u003C\u002Fp>\n\u003Cp>If you would like the plugin in your language and you’re good at translating, please drop us a line at \u003Ca href=\"http:\u002F\u002Fapasionados.es\u002Fcontacto\u002Findex.php?desde=wordpress-org-wp-super-cache-clear-cache-menu-home\" rel=\"nofollow ugc\">Contact us\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Further Reading\u003C\u002Fh4>\n\u003Cp>You can access the description of the plugin in Spanish at: \u003Ca href=\"http:\u002F\u002Fapasionados.es\u002Fblog\u002Fvaciar-cache-wp-super-cache-plugin-wordpress-1933\u002F\" rel=\"nofollow ugc\">Clear All Cache for WP Super Cache Plugin en castellano\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Contact\u003C\u002Fh3>\n\u003Cp>For further information please send us an \u003Ca href=\"http:\u002F\u002Fapasionados.es\u002Fcontacto\u002Findex.php?desde=wordpress-org-wp-super-cache-clear-cache-menu-contact\" rel=\"nofollow ugc\">email\u003C\u002Fa>.\u003C\u002Fp>\n","Clear all cache for WP Super Cache adds a menu entry to the admin menu to clear the cache completely .",7000,279587,62,11,"2026-02-01T14:44:00.000Z","3.0.1",[19,20,113,114,54],"empty-cache","emtpy-wp-super-cache","https:\u002F\u002Fapasionados.es\u002Fblog\u002Fvaciar-cache-wp-super-cache-plugin-wordpress-1933\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-super-cache-clear-cache-menu.2.4.zip",100,{"slug":119,"name":120,"version":121,"author":122,"author_profile":123,"description":124,"short_description":125,"active_installs":126,"downloaded":127,"rating":47,"num_ratings":58,"last_updated":128,"tested_up_to":129,"requires_at_least":130,"requires_php":17,"tags":131,"homepage":133,"download_link":134,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"db-cache-reloaded-fix","DB Cache Reloaded Fix","2.3","Ivan Kristianto","https:\u002F\u002Fprofiles.wordpress.org\u002Fivankristianto\u002F","\u003Cp>This plugin caches every database query with given lifetime. It is much faster than other html caching plugins and uses less disk space for caching. Now compatible with WordPress 3.1.\u003C\u002Fp>\n\u003Cp>This plugin is based on \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fdb-cache-reloaded\u002F\" rel=\"ugc\">DB Cache Reloaded\u003C\u002Fa> by sirzooro. I patch it so it have WordPress 3.4 compatibility.\u003C\u002Fp>\n\u003Cp>I think you’ve heard of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fwp-cache\u002F\" rel=\"ugc\">WP-Cache\u003C\u002Fa> or \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fwp-super-cache\u002F\" rel=\"ugc\">WP Super Cache\u003C\u002Fa>, they are both top plugins for WordPress, which make your site faster and responsive. Forget about them – with DB Cache Reloaded your site will work much faster and will use less disk space for cached files. Your visitors will always get actual information in sidebars and server CPU loads will be as low as possible.\u003C\u002Fp>\n\u003Cp>This plugin is a fork of a \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fdb-cache\u002F\" rel=\"ugc\">DB Cache\u003C\u002Fa> plugin. Because his author did not updated its plugin to WordPress 2.8, I finally (after almost three months since release of WP 2.8) took his plugin and updated it so now it works with newest WordPress version. Additionally I fixed few bugs, cleaned up the code and make it more secure.\u003C\u002Fp>\n\u003Cp>This plugin was tested with WordPress 2.8 and never. It may work with earlier versions too – I have not tested. If you perform such tests, let me know of the results.\u003C\u002Fp>\n\u003Cp>If you are using WordPress 2.9, please use DB Cache Reloaded version 2.0 or never – versions 1.x are not compatible with WordPress 2.9.\u003C\u002Fp>\n\u003Cp>If you are using WordPress 3.0, please use DB Cache Reloaded version 2.1 or never – earlier versions are not compatible with WordPress 3.0.\u003C\u002Fp>\n\u003Cp>For Web Developer:\u003C\u002Fp>\n\u003Cp>If you are a web developer fork me on [Github] (https:\u002F\u002Fgithub.com\u002Fivankristianto\u002FDB-Cache-Reloaded-Fix)\u003C\u002Fp>\n\u003Cp>Available translations:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>English\u003C\u002Fli>\n\u003Cli>French (fr_FR) – thanks \u003Ca href=\"http:\u002F\u002Fwww.inmotionhosting.com\u002F\" rel=\"nofollow ugc\">InMotion Hosting\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Polish (pl_PL)\u003C\u002Fli>\n\u003Cli>Italian (it_IT) – thanks \u003Ca href=\"http:\u002F\u002Fwww.iacchi.org\u002F\" rel=\"nofollow ugc\">Iacopo\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Portuguese Brazilian (pt_BR) – thanks Calebe Aires\u003C\u002Fli>\n\u003Cli>Belorussian (be_BY) – thanks FatCow\u003C\u002Fli>\n\u003Cli>Spanish (es_ES) – thanks Dasumo\u003C\u002Fli>\n\u003Cli>Dutch (nl_NL) – thanks Rene\u003C\u002Fli>\n\u003Cli>Turkish (tr_TR) – thanks wolkanca\u003C\u002Fli>\n\u003Cli>Japanese (jp) – thanks wokamoto\u003C\u002Fli>\n\u003Cli>German (de_DE) – thanks \u003Ca href=\"http:\u002F\u002Fgreatsolution.de\u002F\" rel=\"nofollow ugc\">Carsten Tauber\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Chinese (zh_CN and zh_TW) – thanks \u003Ca href=\"http:\u002F\u002Fneverweep.com\" rel=\"nofollow ugc\">企鹅君\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fdb-cache-reloaded-fix\u002Fchangelog\u002F\" rel=\"ugc\">Changelog\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Fgoo.gl\u002FUzwSf\" rel=\"nofollow ugc\">Blog Post\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Other interesting stuff:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Check out the my other WordPress plugins or web development \u003Ca href=\"http:\u002F\u002Fgoo.gl\u002FOHQNc\" rel=\"nofollow ugc\">My Portfolio\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Want to optimize your WordPress blog? Check out the \u003Ca href=\"http:\u002F\u002Fgoo.gl\u002FQedtH\" rel=\"nofollow ugc\">WordPress Optimization Article\u003C\u002Fa> Guide!\u003C\u002Fli>\n\u003C\u002Ful>\n","The fastest cache engine for WordPress, that produces cache of database queries with easy configuration. Compatible with WordPress 3.4",2000,229802,"2017-11-28T08:10:00.000Z","3.4.2","3.0",[19,20,132,54,22],"db-cache","http:\u002F\u002Fwww.ivankristianto.com\u002Fweb-development\u002Fprogramming\u002Fdb-cache-reloaded-fix-for-wordpress-3-1\u002F1784\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdb-cache-reloaded-fix.zip",{"attackSurface":136,"codeSignals":173,"taintFlows":194,"riskAssessment":195,"analyzedAt":200},{"hooks":137,"ajaxHandlers":169,"restRoutes":170,"shortcodes":171,"cronEvents":172,"entryPointCount":13,"unprotectedCount":13},[138,144,148,154,157,162,164,165],{"type":139,"name":140,"callback":141,"file":142,"line":143},"action","admin_menu","scu_create_theme_options_page","theme-options.php",5,{"type":139,"name":145,"callback":146,"file":142,"line":147},"admin_init","scu_register_and_build_fields",6,{"type":149,"name":150,"callback":151,"priority":68,"file":152,"line":153},"filter","script_loader_src","tonjoo_scu_script","uncache-script.php",17,{"type":149,"name":155,"callback":151,"priority":68,"file":152,"line":156},"style_loader_src",18,{"type":139,"name":158,"callback":159,"priority":160,"file":152,"line":161},"admin_bar_menu","make_parent_node",999,80,{"type":139,"name":140,"callback":141,"file":163,"line":143},"us-theme-options.php",{"type":139,"name":145,"callback":146,"file":163,"line":147},{"type":139,"name":166,"callback":167,"file":163,"line":168},"admin_enqueue_scripts","us_script",7,[],[],[],[],{"dangerousFunctions":174,"sqlUsage":175,"outputEscaping":177,"fileOperations":13,"externalRequests":13,"nonceChecks":192,"capabilityChecks":192,"bundledLibraries":193},[],{"prepared":13,"raw":13,"locations":176},[],{"escaped":13,"rawEcho":147,"locations":178},[179,182,184,186,188,190],{"file":142,"line":180,"context":181},49,"raw output",{"file":142,"line":183,"context":181},51,{"file":163,"line":185,"context":181},56,{"file":163,"line":187,"context":181},58,{"file":163,"line":189,"context":181},189,{"file":163,"line":191,"context":181},194,3,[],[],{"summary":196,"deductions":197},"The 'uncache-script' plugin v1.2.0 presents a mixed security picture.  On the positive side, the plugin has a remarkably small attack surface, with no identified AJAX handlers, REST API routes, shortcodes, or cron events. Furthermore, all SQL queries utilize prepared statements, and there are no recorded vulnerabilities or CVEs, indicating a history of stable and likely secure code. The presence of nonce and capability checks on its limited entry points is also a good security practice.\n\nHowever, a significant concern arises from the code analysis revealing that 100% of its six identified output operations are not properly escaped. This is a critical weakness that could allow for Cross-Site Scripting (XSS) vulnerabilities if user-supplied data, or data that could be manipulated by an attacker, is reflected directly in the output.  While the absence of complex taint flows and dangerous functions is reassuring, the lack of output escaping creates a direct and exploitable avenue for malicious code injection.\n\nIn conclusion, the plugin's strengths lie in its minimal attack surface and adherence to secure database practices. The primary weakness is the universal failure to escape output, which introduces a tangible XSS risk. Until this output escaping issue is addressed, the plugin should be considered to have a moderate security risk due to potential XSS exploits.",[198],{"reason":199,"points":96},"Outputs not properly escaped","2026-03-16T20:07:38.004Z",{"wat":202,"direct":210},{"assetPaths":203,"generatorPatterns":206,"scriptPaths":207,"versionParams":208},[204,205],"\u002Fwp-content\u002Fplugins\u002Funcache-script\u002Fassets\u002Fus-admin.css","\u002Fwp-content\u002Fplugins\u002Funcache-script\u002Fassets\u002Fuikit.js",[],[205],[209],"scu_version",{"cssClasses":211,"htmlComments":215,"htmlAttributes":216,"restEndpoints":218,"jsGlobals":219,"shortcodeOutput":221},[212,213,214],"us-option-wrapper","us-theme-options-wrap","widefat-us",[],[217],"id=\"updateUncache\"",[],[220],"jQuery",[]]