Managing Cache Entries
Managing cache entries needs no configuration and is optional.
Version 1.3.0 adds a new admin interface which you can reach by navigating to System → Full Page Cache Entries. Here you can view, filter and manage all full page cache content. This easy interface gives you real time, granular control over the entire contents of the full page cache and allows you to view individual cached pages, filtering results by the same caching criteria used to create the cache. Version 1.8.0 also adds a cache crawler to this page.
You can also remove individual or multiple cached pages, and see which pages have expired. Cached entries become expired either when the cached content is deleted outside of Magento admin, or when the cache expiration time for Redis, Memcached or APC has been exceeded.
Version 1.5.0 adds the ability to view each cache entry in a new browser window by clicking the View link against each entry, so what you see here is exactly what your customers see. If your admin area is secure, but the frontend is not then the browser may block insecure content when viewing cached pages from admin. This will mean the page will not be displayed correctly. To see the page correctly you need to disable this protection for the page which you can normally do from the address bar area of your browser.
Once generated, by using automatic clearing and warming the cache will keep itself up to date. When there is no cache, whether that's because Evolved Caching has just been installed, or because the cache needed to be cleared for some reason, version 1.8.0 of Evolved Caching adds the Generate Cache button which lets you immediately build up a good basic cache. By using this the crawler will run across all CMS, category (not including filtering) and product pages, so a good percentage of your store a customer visits will be cached right from the outset.
From version 1.9.3 the Refresh Entries button rebuilds the entire cache which is useful if you make a global design change to your store, for instance modifying the footer. Prior to version 1.9.3 this button instead just cleaned up expired cache entries (which it still does).