Both the free and the Pro versions of Comet Cache write cache files to the same directory and store options under the same key, and SleekView reads that directory and those options directly. The kanban renders the same way regardless of which version you run on the WordPress site.

Yes. The drag handler calls the Comet Cache clear helper for that URL, which deletes the matching cache file from the directory on disk. The next visitor request to that URL forces Comet Cache to regenerate the static cache from a live PHP page render.

Yes. Comet Cache honors the TTL setting from its options page, which automatically expires files past the configured age. SleekView surfaces the stale lane so you can spot URLs that crossed the TTL boundary, but the cache directory still self-prunes without intervention.

Yes. SleekView views are configuration only, so you can build one board filtered to blog URLs and another to WooCommerce URLs from the same Comet Cache dataset. Each developer picks a default board, and admins pin shared boards into the sidebar for the whole team.

SleekView reads the exclude rules on every page load, so a URL that newly matches an exclude pattern shows up in the excluded lane automatically. The cached and uncached lanes shrink accordingly, and no kanban reconfiguration is needed for the exclude rule change to take effect.

Each cached card opens a side panel showing the response headers that produced the cache file, the variant flag for logged-in or mobile users, the cache file size, and the file age. Developers can inspect a URL without leaving the kanban to dig in the server cache directory.

Yes. SleekView respects WordPress capabilities, so you can require a senior developer capability before a card lands in the uncached lane for production-tagged URL patterns. Juniors purge staging URLs freely, but only seniors purge production URLs from the kanban.

SleekView reads and writes the existing Comet Cache directory and option rows without adding shadow tables for cache state. View configuration sits in its own small options row, so uninstalling SleekView leaves every cache file and exclude rule exactly where Comet Cache wrote it.