SleekView for StackPath: CDN purge & edge rule tables
StackPath stores its zone ID, API credentials, and purge history inside the WordPress options table. SleekView reads that scattered configuration and the purge log entries so you can audit zones, see recent purges, and spot stale edge rules without leaving WP Admin.
♾️ Lifetime License available
Read your StackPath setup as data, not a settings screen
The StackPath WordPress plugin is a thin integration: its real job is to ship purge requests to the StackPath edge and store zone IDs, API keys, and last-purge timestamps in wp_options under keys like stackpath_settings and stackpath_purge_log. The default admin shows a single settings tab with a manual purge button. There is no list of recent purges, no per-URL purge history, and no breakdown of which posts triggered automatic purges on update.
SleekView reads the StackPath options entries and any custom log table the plugin maintains, then pivots them into rows. Each row can be a purge event with the URL or post ID, the trigger (post update, manual, cache rule), the response code from the API, and the timestamp. Sort by response code to find failed purges, filter to the last 24 hours, or group by post type to see which templates trigger the most edge invalidations.
SleekView never sends purge requests itself. Inline actions invoke StackPath's own purge function, so retries route through the official API and the plugin's hooks fire as expected. Saved views like Failed purges or Purges this hour can be scoped per role, useful for letting a developer triage edge issues without giving them the StackPath API token.
Workflow
From StackPath options to a working purge audit
Pick the source
wp_options entries for stackpath_settings and stackpath_purge_log, plus any custom log table the plugin version uses. Fields are decoded into filterable columns.
Compose columns
Scope per role
Act inline
stackpath_purge_log just like a manual purge would, and the plugin's hooks fire.
Sample columns
A typical StackPath purge audit view
wp_options (stackpath_settings, stackpath_purge_log) + wp_postmeta
| URL | Trigger | Response | Post type | User | Time |
|---|---|---|---|---|---|
| /pricing/ | post update | 200 | page | alex@studio.co | 12m ago |
| /blog/scaling-guide/ | manual | 200 | post | ria@design.io | 1h ago |
| /shop/widget/ | post update | 429 | product | system | 3h ago |
| /account/ | manual | 401 | page | tom@hello.dev | Yesterday |
Comparison
Default StackPath admin vs SleekView
Default StackPath admin
- Settings tab shows a single purge button with no recent history
- No per-URL log of which posts triggered an automatic purge
-
API failures from
stackpath_purge_logonly surface as a generic notice - No way to filter purges to the last hour or to a specific post type
- Junior staff need the full API token to see any purge activity
SleekView
-
Read
stackpath_purge_logas one row per purge event - Filter by API response code to find failed purges only
- Group by post type to see which templates churn the edge
- Sort by timestamp to see purges in the last hour at a glance
- Save a Failed purges view and scope it to the developer role
Features
What SleekView gives you for StackPath
Per-purge visibility
Read each purge as a row with URL, trigger, response code, and user. Stop guessing whether a stale page is the cache or the origin and answer the question in one filter.
Filter failed purges only
Combine response code and time filters to build a punch list of edge invalidations that did not complete. Retry inline through StackPath's own API.
Scoped triage access
Saved views are assigned per role, so a developer can read purge history without ever seeing the StackPath API token stored in wp_options.
Audience
Who uses SleekView for StackPath
Performance engineers
Audit which post types trigger the most purges and tune the rules. The grouped view of stackpath_purge_log by post type makes the offenders obvious.
Agency support
Answer client questions about why a page is stale by checking the purge response. The filtered view of last-hour activity makes triage a single query.
Developers after a deploy
Confirm that every URL in the release notes was purged. Filter by URL pattern, sort by response code, and retry any 4xx or 5xx response through StackPath's own function.
The bigger picture
Why a CDN integration plugin needs a queryable log
StackPath's edge does the heavy lifting, and the WordPress plugin's job is mostly to ship purge requests at the right moments. That arrangement works fine when everything succeeds, but the operational gap shows up the moment a purge fails or a stale page makes it to a stakeholder. The default admin shows a single button and a status notice, which is enough to confirm the integration is wired up and nothing more.
SleekView reframes the same data as a list. Purges become rows. Response codes become a column.
Triggers and timestamps become filters. Failed purges sort to the top, repeat offenders show as clusters by post type, and support can answer cache questions without root access to the server. The plugin still owns the API client and the credentials; SleekView just lets the team responsible for edge performance read the log.
Questions
Common questions about SleekView for StackPath
No. SleekView reads from whatever the StackPath plugin writes to wp_options and any purge log table on activation. Any active StackPath account works, including the lower-tier plans, because the plugin stores its purge events locally before shipping them to the edge.
Yes. SleekView exposes StackPath's own purge function as an inline row action. The call goes through the plugin's API client, so retries are logged in stackpath_purge_log exactly as the manual purge button would log them.
No. Reads are paginated against the wp_options autoload index and the purge log table's primary key. The view never loads more rows than the visible page, and the edge purge pipeline is untouched.
Yes. Response codes stored in stackpath_purge_log become a filterable column. A saved view of non-200 responses acts as a punch list for the developer responsible for the edge configuration.
Yes. Saved views and column sets are assigned per role with row-level permission checks before the query runs. A developer role can read purge history without exposure to the API token stored in stackpath_settings.
Yes. The StackPath plugin stores settings and logs per subsite when run network-wide, and SleekView respects that scope. Each subsite shows only its own purge events, which matches how the plugin itself behaves on multisite.
Yes. Any saved view exports to CSV from the table header with the active filters, sort order, and visible columns honored. This is useful for handing an incident report to support or archiving a release-day audit.
SleekView falls back to reading the rolling stackpath_purge_log array stored in wp_options. The shape is decoded automatically, so older versions of the plugin work without configuration as long as the option key exists.
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 Pdf Product Vouchers
- Tradegecko Wp
- Woocommerce Product Vendors
- Woocommerce Bulk Stock Management
- Mailchimp For Woocommerce
- Edd Software Licenses
- Edd Convertkit
- Woocommerce Deposits
- Woocommerce Stock Sync
- Woocommerce Inventory Pro
- Edd Software Bundles
- Woocommerce Favorites
- Gumroad Wp
- Woocommerce Additional Variation Images
- Woocommerce Composite Products