Table of Contents

This article explains the different terminologies used by Comet Cache when referring to clearing the cache. Comet Cache stores cache files for your site inside the default cache directory located at wp-content/cache/comet-cache/cache/ and, depending on your configuration, Comet Cache will automatically clear or wipe the cache to ensure that that an up-to-date cache file is always served to visitors.


To "wipe", is to delete ALL files in the cache directory, for all hosts. This includes, but is not limited to, all systematic cc- prefixed files in the main wp-content/cache/comet-cache/cache/cc-* directory; and anything else for that matter. A full wipe of the cache can be performed by network admins on a MS network.

A manual wipe is not necessary (or available) for standard WP installs in the Comet Cache UI; it is only available when Comet Cache is installed on a Multisite Network. That said, a full wipe is automatically performed by Comet Cache on both standard and network installs whenever Comet Cache options are changed, when the plugin is reactivated/upgraded; or when the plugin is deactivated and/or uninstalled. In the case of uninstalling, the entire Comet Cache base directory is removed also; i.e. wp-content/cache/comet-cache.


To "clear", is to delete cache files (in whole, or in part), for the current host; excluding systematic cc- prefixed files in the main wp-content/cache/comet-cache/cache/cc-* directory

There are two types of "clearing" that CC deals with:

  1. Manual Clearing of the entire cache. This will clear all cache-related files (and directories containing them). A manual clearing of the cache will impact the current host only. Please note that host specificity is irrelevant on a standard WP install since there is just one host; i.e. a clearing of the cache will simply clear the cache for your site. On a MS network, host specificity is important. The cache will be cleared for the current host only; i.e. whichever child blog's dashboard you are currently logged into whenever you perform a manual clearing of the cache.

  2. Automatic Cache Clearing deals w/ specific cache files only; i.e. not ALL files, just those that contain specific portions of the site which need to be refreshed for one reason or another. Automatic cache clearing can happen as changes occur on-site or in your dashboard. Comet Cache monitors various components within your WordPress installation, and also provides you with some control over automatic cache clearing behavior (even more control in the Pro version). See: WordPress Dashboard Comet Cache Clearing the Cache for config. options.

Note: Automatic cache clearing deals with files only (not directories). This is for speed/optimization. In short, it is not necessary for Comet Cache to remove directories too; it's just the files that really matter. If you would like to clear the entire cache (including directories), please do a manual clearing of the cache, which does remove directories also.

Multisite Network with Domain Mapping: When domain mapping is being used on a multisite network, the cache for all domains mapped to the blog is also cleared.


To "purge", is to automatically delete any expired cache files for the current host (i.e. old/stale cache files, according to your configured cache expiration time). Purging (aka: garbage collecting) is always automatic; i.e. there is no UI functionality that allows you to purge the cache.

Automatic purging routines in Comet Cache are driven by WP Cron, and they are always based on your Cache Expiration Time. See: WordPress Dashboard Comet Cache Expiration Time.

Note: It's worth mentioning that Comet Cache will never serve an old/stale cache file, even if automatic purging routines get behind, or have been disabled for some reason (e.g. if your web host does not allow WP Cron). The last modification time for each cache file is always checked (in real-time) before it is served to a visitor. Thus, if a cache file expires (either through an automatic purge, or simply because it is too old), it is automatically regenerated on-the-fly.

See also: