[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2YJ0BoxWXGagY0C7VVdUWF6ifoq8uRzwtt0HPyLerT0":3,"$fGuBvbdC8C875WYO4T-8k5lfQjuubFDELDAONKKKJqic":353,"$f8zX6BvudGZ65PW6nbl8tInfNhB6HXe4dvsf7rEJ0Iuo":357},{"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":21,"download_link":22,"security_score":23,"vuln_count":11,"unpatched_count":11,"last_vuln_date":24,"fetched_at":25,"discovery_status":26,"vulnerabilities":27,"developer":28,"crawl_stats":24,"alternatives":35,"analysis":140,"fingerprints":312},"cache-file-management-for-wp-super-cache","Cache file management for wp super cache","1.3","For Games","https:\u002F\u002Fprofiles.wordpress.org\u002Fsockscap64\u002F","\u003Cp>This is a simple plugin to help the users to manage cache files of wp super cache.\u003C\u002Fp>\n\u003Cp>Due to the cache management in WPSC is too weak. Sometimes, We need to delete one or multiple cache pages or even a category cache of wp suer cache, so we have to delete it via SSH.\u003C\u002Fp>\n\u003Cp>This plugin will show all caches of WPSC, and you could delete one or multiple cache files or folders.\u003C\u002Fp>\n\u003Cp>WP Super cache(WPSC) is my favorite cache plugin, so I developed this plugin to help myself manage cache files, and hope it will help someone else has the same needs.\u003C\u002Fp>\n\u003Cp>This plugin is based on WP super cache, you should install WPSC first, or this plugin do nothing.\u003C\u002Fp>\n\u003Cp>This plugin does not have any options to set.\u003C\u002Fp>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cp>This plugin is based on Tiny File Manager. Source code here https:\u002F\u002Fgithub.com\u002Fprasathmani\u002Ftinyfilemanager\u003C\u002Fp>\n","A simple tool to help the users to manage cache files of wp super cache.",0,1259,"2019-02-02T08:23:00.000Z","5.0.25","3.9","5.2.4",[18,19,20],"cache-files","cache-files-management","wp-super-cache","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcache-file-management-for-wp-super-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-file-management-for-wp-super-cache.zip",85,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"slug":29,"display_name":7,"profile_url":8,"plugin_count":30,"total_installs":31,"avg_security_score":23,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},"sockscap64",4,70,30,84,"2026-05-20T03:01:20.117Z",[36,61,82,99,118],{"slug":20,"name":37,"version":38,"author":39,"author_profile":40,"description":41,"short_description":42,"active_installs":43,"downloaded":44,"rating":45,"num_ratings":46,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":50,"tags":51,"homepage":56,"download_link":57,"security_score":58,"vuln_count":59,"unpatched_count":11,"last_vuln_date":60,"fetched_at":25},"WP Super Cache","3.1.0","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, loaded before most of WordPress. Add your own plugin either by putting it in the wp-content\u002Fplugins\u002Fwp-super-cache-plugins directory, or by calling wpsc_add_plugin( $name ) with the full path to the plugin.\u003C\u002Fp>\n\u003Cp>The cookies used to identify “known users” can be modified with wpsc_add_cookie( $name ) and wpsc_delete_cookie( $name ). 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.\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>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>Garbage collection of old cache files won’t work if WordPress can’t find wp-cron.php. Check your access_logs for wp-cron.php entries and that your hostname resolves to the external IP address other servers on the network\u002FInternet use.\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>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 page is ok but posts and pages give a 404? Go to Settings->permalinks and click “Save” once you’ve selected a custom permalink structure. You may need to manually update your .htaccess file.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If certain characters do not appear correctly on your website your server may not be configured correctly. You need to tell visitors what character set is used. Go to Settings->Reading and copy the ‘Encoding for pages and feeds’ value. Edit the .htaccess file with all your Supercache and WordPress rewrite rules and add this at the top, replacing CHARSET with the copied value. (for example, ‘UTF-8’)\u003C\u002Fp>\n\u003Cpre>\u003Ccode>AddDefaultCharset CHARSET\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>The error message, “WP Super Cache is installed but broken. The constant WPCACHEHOME must be set in the file wp-config.php and point at the WP Super Cache plugin directory.” appears at the end of every page. You can delete wp-content\u002Fadvanced-cache.php and reload the plugin settings page or edit wp-config.php and look for WPCACHEHOME and make sure it points at the wp-super-cache folder. This will normally be wp-content\u002Fplugins\u002Fwp-super-cache\u002F but you’ll likely need the full path to that file (so it’s easier to let the settings page fix it). If it is not correct the caching engine will not load.\u003C\u002Fli>\n\u003Cli>If your server is running into trouble because of the number of semaphores used by the plugin it’s because your users are using file locking which is not recommended (but is needed by a small number of users). You can globally disable file locking by defining the constant WPSC_DISABLE_LOCKING, or defining the constant WPSC_REMOVE_SEMAPHORE so that sem_remove() is called after every page is cached but that seems to cause problems for other processes requesting the same semaphore. Best to disable it.\u003C\u002Fli>\n\u003Cli>Set the variable $htaccess_path in wp-config.php or wp-cache-config.php to the path of your global .htaccess if the plugin is looking for that file in the wrong directory. This might happen if you have WordPress installed in an unusual way.\u003C\u002Fli>\n\u003C\u002Fol>\n","A very fast caching engine for WordPress that produces static html files.",1000000,62825761,86,1341,"2026-04-14T15:49:00.000Z","6.9.4","6.8","7.4",[52,53,54,55,20],"cache","caching","performance","wp-cache","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-super-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-super-cache.3.1.0.zip",95,12,"2022-10-03 00:00:00",{"slug":62,"name":63,"version":64,"author":65,"author_profile":66,"description":67,"short_description":68,"active_installs":69,"downloaded":70,"rating":71,"num_ratings":72,"last_updated":73,"tested_up_to":48,"requires_at_least":74,"requires_php":75,"tags":76,"homepage":79,"download_link":80,"security_score":81,"vuln_count":11,"unpatched_count":11,"last_vuln_date":24,"fetched_at":25},"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,280837,62,11,"2026-02-01T14:44:00.000Z","3.0.1","",[52,53,77,78,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":83,"name":84,"version":85,"author":86,"author_profile":87,"description":88,"short_description":89,"active_installs":90,"downloaded":91,"rating":11,"num_ratings":11,"last_updated":92,"tested_up_to":93,"requires_at_least":94,"requires_php":75,"tags":95,"homepage":97,"download_link":98,"security_score":23,"vuln_count":11,"unpatched_count":11,"last_vuln_date":24,"fetched_at":25},"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,6578,"2015-08-20T08:45:00.000Z","4.3.34","3.0.3",[52,53,96,55,20],"page-cache","http:\u002F\u002Fwww.tonjoo.com\u002Funcache-script\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Funcache-script.zip",{"slug":100,"name":101,"version":102,"author":103,"author_profile":104,"description":105,"short_description":106,"active_installs":107,"downloaded":108,"rating":45,"num_ratings":30,"last_updated":109,"tested_up_to":110,"requires_at_least":111,"requires_php":75,"tags":112,"homepage":116,"download_link":117,"security_score":23,"vuln_count":11,"unpatched_count":11,"last_vuln_date":24,"fetched_at":25},"country-caching-extension-for-wp-super-cache","Country Caching For WP Super Cache","0.8.0","wrigs1","https:\u002F\u002Fprofiles.wordpress.org\u002Fwrigs1\u002F","\u003Cp>DUE TO PERSONAL CIRCUMSTANCES I AM NO LONGER ABLE TO DEVELOP OR SUPPORT THIS PLUGIN. IF YOU ARE INTERESTED IN ADOPTING THIS PLUGIN SEE https:\u002F\u002Fdeveloper.wordpress.org\u002Fplugins\u002Fwordpress-org\u002Ftake-over-an-existing-plugin\u002F\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Bonus\u003C\u002Fstrong> also makes Cookie Notice work correctly with WPSC (whether using country\u002FEU geolocation or not).\u003C\u002Fp>\n\u003Cp>Allows WP Super Cache to display the correct page\u002Fwidget content for a visitor’s country when you are using geo-location; solves problems like these reported on  \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fplugin-wp-super-cache-super-cache-with-geo-targeting\" rel=\"ugc\">WordPress.Org\u003C\u002Fa> and  \u003Ca href=\"http:\u002F\u002Fstackoverflow.com\u002Fquestions\u002F21308405\u002Fgeolocation-in-wordpress\" rel=\"nofollow ugc\">StackOverflow\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>A similar extension is available \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcountry-caching-extension\u002F\" rel=\"ugc\">for Comet Cache\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>This plugin builds an extension script that enables Super Cache to create separate snapshots (cache) for each page based on country location.\u003C\u002Fp>\n\u003Cp>Separate snapshots can be restricted to specific countries.  E.g. if you are based in the US but customize some content for Canadian or Mexican visitors, you can restrict separate caching to CA & MX visitors; and all other visitors will see the same cached (“US”) content.\u003C\u002Fp>\n\u003Cp>You can also specify a single snapshot for a group of countries e.g. all European Union countries.\u003C\u002Fp>\n\u003Cp>It works on both normal WordPress and Multisite (see FAQ) installations.\u003C\u002Fp>\n\u003Cp>More info in \u003Ca href=\"http:\u002F\u002Fwptest.means.us.com\u002Fgeolocation-and-wp-super-cache-caching-by-page-visitor-country-instead-of-just-page\u002F\" rel=\"nofollow ugc\">the user guide\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Identification of visitor country for caching\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Via Cloudflare or Maxmind (when the plugin is first enabled it uploads GeoLite2 data created by MaxMind, available from http:\u002F\u002Fwww.maxmind.com ). Cloudflare works with any PHP version, but Maxmind Geolite2 requires PHP 5.4 or later. \u003Cem>It is also possible to connect a different GeoLocation sytem of your choice (see documentation).\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>If you use Cloudflare and have “switched on” their GeoLocation option ( see \u003Ca href=\"https:\u002F\u002Fsupport.cloudflare.com\u002Fhc\u002Fen-us\u002Farticles\u002F200168236-What-does-CloudFlare-IP-Geolocation-do-\" rel=\"nofollow ugc\">Cloudflare’s  instructions\u003C\u002Fa> ) then it will be used to identify visitor country.  If not, then the Maxmind Country Database will be used.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Updating\u003C\u002Fstrong> (If not using Cloudflare for country) The installed Maxmind Country\u002FIP data file will lose accuracy over time.  To automate a monthly update of this file, install and enable the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcategory-country-aware\u002F\" rel=\"ugc\">Category Country Aware (CCA) plugin\u003C\u002Fa> (Country Caching and the Cataegory Country Aware (CCA) plugins use the same Maxmind data file in the same folder and the CCA plugin includes code for its update). The CCA plugin has many other features and functionality you may find useful. Alternatively you can manually update (FAQ below).\u003C\u002Fp>\n\u003Ch3>ADVICE\u003C\u002Fh3>\n\u003Cp>I don’t recommend you use ANY Caching plugin UNLESS you know how to use an FTP program (e.g. Filezilla). Caching plugins can cause “white screen” problems for some users. WP Super Cache is no different; when I checked the first page of its support forum it included 4 \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fsite-broken-after-activate-wp-super-cache\" rel=\"ugc\">posts like  this\u003C\u002Fa>. Sometimes the only solution is to manually delete files using FTP or OS command line. When deactivated\u002Fdeleted via Dashboard->Plugins; the Country Caching plugin deletes its files, but in “white screen” situations you may have to resort to “manual” deletion – see FAQ for instructions.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This program is free software licensed under the terms of the \u003Ca href=\"http:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fold-licenses\u002Fgpl-2.0.html\" rel=\"nofollow ugc\">GNU General Public License version 2\u003C\u002Fa> as published by the Free Software Foundation.\u003C\u002Fp>\n\u003Cp>In particular please note the following:\u003C\u002Fp>\n\u003Cp>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\u003C\u002Fp>\n","Extends WP Super Cache to cache by page\u002Fvisitor country instead of just page. Solves \"wrong country content\" Geo-Location issues.",200,6930,"2021-03-24T11:06:00.000Z","4.9.29","3.3",[53,113,114,115,20],"country","geoip","super-cache","http:\u002F\u002Fmeans.us.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcountry-caching-extension-for-wp-super-cache.zip",{"slug":119,"name":120,"version":121,"author":122,"author_profile":123,"description":124,"short_description":125,"active_installs":81,"downloaded":126,"rating":127,"num_ratings":128,"last_updated":129,"tested_up_to":130,"requires_at_least":131,"requires_php":132,"tags":133,"homepage":75,"download_link":138,"security_score":139,"vuln_count":11,"unpatched_count":11,"last_vuln_date":24,"fetched_at":25},"cache-purger-for-bunnycdn","Cache Purger for BunnyCDN","2.0","amanda f","https:\u002F\u002Fprofiles.wordpress.org\u002Fsayatentang\u002F","\u003Cp>Cache Purger for BunnyCDN is a powerful and flexible plugin that automatically purges BunnyCDN cache whenever you publish or update posts\u002Fpages in WordPress. This ensures that your visitors always get the most up-to-date content.\u003C\u002Fp>\n\u003Cp>In version 2.0, the plugin now supports cache purging for additional popular caching plugins including LiteSpeed Cache, WP Fastest Cache, WP-Optimize, Cache Enabler, Breeze, and Hummingbird – alongside the previously supported WP Rocket, WP Super Cache, and W3 Total Cache.\u003C\u002Fp>\n\u003Cp>Developed to address persistent caching issues when using BunnyCDN and Bunny DNS Accelerator, this plugin ensures both your local and CDN caches stay in sync for optimal performance and content freshness.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key Features:\u003C\u002Fstrong>\u003Cbr \u002F>\n– Automatically purges BunnyCDN cache for individual URLs whenever content is published or updated.\u003Cbr \u002F>\n– Integrates with major WordPress caching plugins:\u003Cbr \u002F>\n  – WP Rocket\u003Cbr \u002F>\n  – WP Super Cache\u003Cbr \u002F>\n  – W3 Total Cache\u003Cbr \u002F>\n  – LiteSpeed Cache\u003Cbr \u002F>\n  – WP Fastest Cache\u003Cbr \u002F>\n  – WP-Optimize\u003Cbr \u002F>\n  – Cache Enabler\u003Cbr \u002F>\n  – Breeze\u003Cbr \u002F>\n  – Hummingbird Cache\u003Cbr \u002F>\n– Logs all purge requests and responses for easy monitoring.\u003Cbr \u002F>\n– Supports wildcard purging for broad cache invalidation.\u003Cbr \u002F>\n– Asynchronous cache purging via WP-Cron for optimized performance.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Why Use Cache Purger for BunnyCDN?\u003C\u002Fstrong>\u003Cbr \u002F>\nThis plugin is ideal for sites using BunnyCDN to accelerate global content delivery. By purging both CDN and local caches when content updates, your users always receive the freshest possible version of your site.\u003C\u002Fp>\n\u003Ch3>External Services\u003C\u002Fh3>\n\u003Cp>This plugin connects to an external API to manage cache purging for updated pages, ensuring that users always see the latest content. Each time a page is updated, the plugin sends the page URL to the Bunny.net API at https:\u002F\u002Fapi.bunny.net\u002Fpurge to clear the cache.\u003C\u002Fp>\n\u003Cp>For more information, please refer to Bunny.net’s \u003Ca href=\"https:\u002F\u002Fbunny.net\u002Ftos\u002F\" rel=\"nofollow ugc\">Terms of Use\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fbunny.net\u002Fprivacy\u002F\" rel=\"nofollow ugc\">Privacy Policy\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This plugin is licensed under the GPLv2 or later. For more information, see https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html.\u003C\u002Fp>\n","Automatically purge BunnyCDN cache on post\u002Fpage updates. Integrates with top WordPress caching plugins for seamless cache clearing.",1799,74,3,"2025-05-09T06:11:00.000Z","6.7.5","5.0","7.2",[134,135,136,20,137],"bunnycdn","cache-purging","litespeed","wp-rocket","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-purger-for-bunnycdn.2.0.zip",92,{"attackSurface":141,"codeSignals":157,"taintFlows":250,"riskAssessment":300,"analyzedAt":311},{"hooks":142,"ajaxHandlers":153,"restRoutes":154,"shortcodes":155,"cronEvents":156,"entryPointCount":11,"unprotectedCount":11},[143,149],{"type":144,"name":145,"callback":146,"priority":11,"file":147,"line":148},"action","init","load_localisation","includes\u002Fcache-file-management-for-wp-super-cache.php",124,{"type":144,"name":150,"callback":151,"file":147,"line":152},"admin_menu","add_admin_menu",126,[],[],[],[],{"dangerousFunctions":158,"sqlUsage":164,"outputEscaping":166,"fileOperations":30,"externalRequests":11,"nonceChecks":248,"capabilityChecks":128,"bundledLibraries":249},[159],{"fn":160,"file":161,"line":162,"context":163},"shell_exec","includes\u002Fcfm-lib-tfm.php",351,"$mime = shell_exec('file -bi ' . $file);",{"prepared":11,"raw":11,"locations":165},[],{"escaped":30,"rawEcho":167,"locations":168},45,[169,172,173,175,177,179,180,182,184,186,188,190,192,193,194,196,198,200,202,204,205,207,208,210,212,213,214,215,217,219,221,223,224,226,228,229,230,232,234,236,238,240,242,244,246],{"file":147,"line":170,"context":171},256,"raw output",{"file":147,"line":170,"context":171},{"file":147,"line":174,"context":171},258,{"file":147,"line":176,"context":171},259,{"file":147,"line":178,"context":171},261,{"file":147,"line":178,"context":171},{"file":147,"line":181,"context":171},263,{"file":147,"line":183,"context":171},278,{"file":147,"line":185,"context":171},279,{"file":147,"line":187,"context":171},280,{"file":147,"line":189,"context":171},281,{"file":147,"line":191,"context":171},298,{"file":147,"line":90,"context":171},{"file":147,"line":90,"context":171},{"file":147,"line":195,"context":171},309,{"file":147,"line":197,"context":171},311,{"file":147,"line":199,"context":171},320,{"file":147,"line":201,"context":171},383,{"file":147,"line":203,"context":171},416,{"file":147,"line":203,"context":171},{"file":147,"line":206,"context":171},435,{"file":147,"line":206,"context":171},{"file":147,"line":209,"context":171},436,{"file":147,"line":211,"context":171},440,{"file":147,"line":211,"context":171},{"file":147,"line":211,"context":171},{"file":147,"line":211,"context":171},{"file":147,"line":216,"context":171},444,{"file":147,"line":218,"context":171},445,{"file":147,"line":220,"context":171},448,{"file":147,"line":222,"context":171},472,{"file":147,"line":222,"context":171},{"file":147,"line":225,"context":171},473,{"file":147,"line":227,"context":171},477,{"file":147,"line":227,"context":171},{"file":147,"line":227,"context":171},{"file":147,"line":231,"context":171},480,{"file":147,"line":233,"context":171},481,{"file":147,"line":235,"context":171},482,{"file":147,"line":237,"context":171},486,{"file":147,"line":239,"context":171},488,{"file":147,"line":241,"context":171},511,{"file":147,"line":243,"context":171},512,{"file":147,"line":245,"context":171},549,{"file":147,"line":247,"context":171},578,1,[],[251,279],{"entryPoint":252,"graph":253,"unsanitizedCount":277,"severity":278},"view_file (includes\u002Fcache-file-management-for-wp-super-cache.php:208)",{"nodes":254,"edges":273},[255,260,266,269],{"id":256,"type":257,"label":258,"file":147,"line":259},"n0","source","$_GET",216,{"id":261,"type":262,"label":263,"file":147,"line":264,"wp_function":265},"n1","sink","file_get_contents() [SSRF\u002FLFI]",250,"file_get_contents",{"id":267,"type":257,"label":268,"file":147,"line":259},"n2","$_GET (x7)",{"id":270,"type":262,"label":271,"file":147,"line":170,"wp_function":272},"n3","echo() [XSS]","echo",[274,276],{"from":256,"to":261,"sanitized":275},false,{"from":267,"to":270,"sanitized":275},8,"medium",{"entryPoint":280,"graph":281,"unsanitizedCount":11,"severity":299},"\u003Ccache-file-management-for-wp-super-cache> (includes\u002Fcache-file-management-for-wp-super-cache.php:0)",{"nodes":282,"edges":294},[283,284,285,287,288,292],{"id":256,"type":257,"label":258,"file":147,"line":259},{"id":261,"type":262,"label":263,"file":147,"line":264,"wp_function":265},{"id":267,"type":257,"label":286,"file":147,"line":259},"$_GET (x12)",{"id":270,"type":262,"label":271,"file":147,"line":170,"wp_function":272},{"id":289,"type":257,"label":290,"file":147,"line":291},"n4","$_POST",185,{"id":293,"type":262,"label":271,"file":147,"line":241,"wp_function":272},"n5",[295,297,298],{"from":256,"to":261,"sanitized":296},true,{"from":267,"to":270,"sanitized":296},{"from":289,"to":293,"sanitized":296},"low",{"summary":301,"deductions":302},"The plugin 'cache-file-management-for-wp-super-cache' version 1.3 presents a mixed security posture. On the positive side, it demonstrates good practices by having zero known CVEs, a zero attack surface for unprotected entry points, and all SQL queries utilize prepared statements. The presence of capability checks and a nonce check further suggests an attempt to secure its functionality. However, the static analysis reveals some significant concerns that temper this positive outlook. The detection of the `shell_exec` function is a critical red flag, as it can be a vector for remote code execution if not handled with extreme caution and robust sanitization. Additionally, the low percentage of properly escaped output (8%) indicates a high probability of cross-site scripting (XSS) vulnerabilities, which could be exploited by attackers to inject malicious scripts into the website.\n\nWhile the taint analysis did not identify critical or high-severity flows, the single flow with an unsanitized path warrants attention. This, combined with the low output escaping rate, suggests a potential for path traversal or other file manipulation vulnerabilities if the unsanitized path interacts with file operations. The absence of a recorded vulnerability history is a strength, suggesting the plugin has historically been maintained securely. However, this doesn't negate the risks identified in the current static analysis. The plugin's strengths lie in its secure handling of database queries and its limited direct attack surface. Its weaknesses are primarily concentrated in the potential for code execution via `shell_exec` and the high likelihood of XSS due to insufficient output escaping.",[303,306,308],{"reason":304,"points":305},"Dangerous function: shell_exec detected",15,{"reason":307,"points":277},"Low output escaping rate (8%)",{"reason":309,"points":310},"Flow with unsanitized path detected",10,"2026-04-16T14:28:42.935Z",{"wat":313,"direct":326},{"assetPaths":314,"generatorPatterns":321,"scriptPaths":322,"versionParams":325},[315,316,317,318,319,320],"\u002Fwp-content\u002Fplugins\u002Fcache-file-management-for-wp-super-cache\u002Fassets\u002Fcss\u002Fjquery.treeview.css","\u002Fwp-content\u002Fplugins\u002Fcache-file-management-for-wp-super-cache\u002Fassets\u002Fjs\u002Fjquery.treeview.js","\u002Fwp-content\u002Fplugins\u002Fcache-file-management-for-wp-super-cache\u002Fassets\u002Fjs\u002Ftinymce.popup.js","\u002Fwp-content\u002Fplugins\u002Fcache-file-management-for-wp-super-cache\u002Fassets\u002Fjs\u002Fjquery.jscrollpane.min.js","\u002Fwp-content\u002Fplugins\u002Fcache-file-management-for-wp-super-cache\u002Fassets\u002Fjs\u002Ftinymce.min.js","\u002Fwp-content\u002Fplugins\u002Fcache-file-management-for-wp-super-cache\u002Fassets\u002Fcss\u002Ftinymce.popup.css",[],[323,324],"\u002Fwp-content\u002Fplugins\u002Fcache-file-management-for-wp-super-cache\u002Fincludes\u002Fcfm-lib-tfm.php","\u002Fwp-content\u002Fplugins\u002Fcache-file-management-for-wp-super-cache\u002Fincludes\u002Fcache-file-management-for-wp-super-cache.php",[],{"cssClasses":327,"htmlComments":341,"htmlAttributes":345,"restEndpoints":349,"jsGlobals":350,"shortcodeOutput":352},[328,329,330,331,332,333,334,335,336,337,338,339,340],"cfm_delete_cache_button","cfm_file_tree","cfm_header","cfm_icon","cfm_item","cfm_lock","cfm_rename","cfm_text","cfm_title","cfm_unlock","cfm_user","cfm_user_icon","cfm_wpsc_cache_dir",[342,343,344],"\u003C!-- Delete file \u002F folder -->","\u003C!-- Mass deleting -->","\u003C!--Tiny File Manager -->",[346,347,348],"data-title","data-type","data-path",[],[351],"tinyfilemanager",[],{"error":296,"url":354,"statusCode":355,"statusMessage":356,"message":356},"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fcache-file-management-for-wp-super-cache\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":11,"versions":358},[]]