SleekView for Powered Cache: page cache & rule tables
Powered Cache writes static page snapshots to disk and keeps rejection rules in its options. SleekView surfaces both as one workspace so cached URLs, excluded patterns, and preload progress live in the same sortable view.
♾️ Lifetime License available
Read your Powered Cache state as a per-URL ledger
Powered Cache writes one file per URL into wp-content/cache/powered-cache/ and stores configuration in the powered_cache_settings option, including rejection patterns, preload settings, and CDN rewrites. Per-environment overrides live in wp-content/pc-config/config-*.php. The default admin shows global toggles and a cache size summary, but never lists every cached URL with its size, age, or whether it was rejected by a pattern in rejected_uri.
SleekView indexes the cache directory and parses powered_cache_settings so the same data becomes flat rows. One row per URL can show its cached file size, last refresh, MIME type, and whether a rejection rule blocked it. Rejection patterns surface as their own table with the match count produced by the front-end filter, and preload progress joins the same workspace with current queue size and estimated completion.
SleekView is read-only against the cache directory and writes only through Powered Cache's option API for inline actions like purging a URL or updating a rejection pattern. The plugin keeps serving static files through its NGINX or Apache rewrites exactly as before. Saved views like Stale cached URLs or Rejected by /checkout/* scope per role so a developer audits cache state without access to the licence or the global toggles.
Workflow
From powered_cache_settings to a working URL ledger
Connect the sources
powered_cache_settings option as sources. URL, cache state, rejection reason, and last refresh decode into filterable columns automatically.
Compose the audit view
Scope per role
Act inline
Sample columns
A typical Powered Cache view
wp_options (powered_cache_settings) + cache directory index
| URL | Cache | Size | Rejected by | Post type | Last refresh |
|---|---|---|---|---|---|
| / | Cached | 22 KB | page | 5m ago | |
| /checkout/ | Skipped | /checkout/* |
page | Never | |
| /blog/launch-notes/ | Stale | 84 KB | post | 11d ago | |
| /account/orders/ | Missing | /account/* |
page | Never |
Comparison
Default Powered Cache admin vs SleekView
Default Powered Cache admin
- Cache size only shows as a single aggregate total
- Rejection patterns sit in a textarea with no match data
- No file-level list of cached URLs with last refresh
- No way to filter to stale URLs after a deploy
- Hard to delegate cache triage without granting plugin settings access
SleekView
- One row per URL with cache state, size, and last refresh
-
Rejection patterns shown with match counts from
rejected_uri - Filter to stale URLs by reading the cache file mtime
- Group by post type or template for systematic audits
- Save shared views like 'Stale URLs since last deploy'
Features
What SleekView gives you for Powered Cache
Per-URL cache visibility
Read the powered-cache directory as a table with URL, size, and last refresh. The cache stops being a single number on a settings screen and becomes a sortable inventory.
Filter to the right rejections
Combine filters across cache state, rejection reason, and last refresh. The view becomes a punch list of URLs that need attention rather than a wall of identical green badges.
Inline purge through the plugin
Trigger Powered Cache's own purge action from a row. Writes go through the plugin's option API so the cache invalidator and the rewrites keep working as before.
Audience
Who uses SleekView for Powered Cache
Performance engineers
Audit every cached URL against its rejection patterns. Sort by mtime to find URLs that never regenerated after a deploy and fix the upstream cause once instead of clearing pages one at a time.
Agency support
Give junior staff a read-only audit of cache size and rejection coverage. They answer client questions about whether checkout is correctly excluded without rights to plugin settings.
Site owners after a release
Filter to URLs whose cache file is older than the latest deploy timestamp. Watch the queue refill as the preload runs and stop trusting the aggregate cache size.
The bigger picture
Why a file-based cache needs a per-URL inventory
Powered Cache earns its reputation by being lean. Activate the plugin, point the rewrites at the cache directory, and most pages serve as static files before WordPress even loads. The catch is the admin shows the cache as a single number.
Total cached size, total skipped URLs, total preload progress. That summary is fine on a five-page brochure site, but the moment a deploy invalidates only some templates or a rejection pattern accidentally matches a checkout variant, the team has no way to read the queue. The default UI gives no list, no filter, and no per-URL refresh timestamp.
SleekView treats Powered Cache's directory and its options as exactly what they are: a list of URLs and a set of patterns. Stale URLs sort to the top, rejection rules show their actual match counts, and developers can purge a row without holding rights to the plugin settings. The cache keeps serving static files; SleekView just lets the operator read the inventory that is already on disk.
Questions
Common questions about SleekView for Powered Cache
Yes. Powered Cache continues to serve static files through its rewrites because SleekView never modifies the cache directory or its routing. The view only reads file mtime, size, and URL mapping from the same data the plugin already maintains.
Yes. The inline purge action invokes Powered Cache's own purge helper. The plugin's invalidation queue, option counters, and any related CDN purges all behave normally because nothing is bypassed.
Yes. The rejected_uri field in powered_cache_settings is read into a dedicated table where every pattern is a row with the match count it produces on the front end. Patterns that never match become candidates for removal during a configuration audit.
No. Directory listings are paginated and cached in transient storage with a short TTL. The front-end cache continues to serve through the plugin's normal rewrites because nothing in SleekView modifies the pipeline.
Yes. SleekView scopes saved views per role and hides fields like the licence option and the global toggles. A developer can read every cached URL and rejection pattern without exposure to settings they are not meant to change.
Yes. Powered Cache stores its cache directory and settings per subsite when run network-wide. SleekView respects that boundary so each subsite shows only its own cache and rejection data.
Yes. Any saved view exports to CSV from the table header with active filters, sort order, and visible columns preserved. A weekly export of stale URLs makes a useful artefact for hosting handoffs.
Yes. Preload runs through Powered Cache's own cron event and writes to the same directory SleekView reads. The view reflects whatever the preload has produced on its last pass, with no separate sync to manage.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkoutBrowse more
- Woocommerce Fast Checkout
- Pretty Links
- Woocommerce Sequential Order Numbers Pro
- Berocket Product Filter
- Woocommerce Product Csv Import
- Woocommerce Clearpay Afterpay
- Yith Woocommerce Checkout Manager
- Payu Money Woocommerce
- Checkout Field Editor
- Woocommerce Shipment Tracking Pro
- Woocommerce Quick Order
- Yith Woocommerce Product Add Ons
- Sprout Invoices
- Edd Convertkit
- Woocommerce Shipping Class Rates