SleekView for PublishPress Blocks
SleekView walks post_content, reads the PublishPress Blocks permission map from wp_options and renders block usage, role scope and scheduled visibility as sortable, filterable columns inside WP Admin.
♾️ Lifetime License available
The block library as a real working table
PublishPress Blocks (formerly Advanced Gutenberg) extends the block editor with a roster of additional blocks, role-based permissions, scheduled block visibility and per-block style controls. It is one of the most common ways to make a multi-author site usable across designers, editors and contributors. The trouble is that block usage data lives where it has always lived: parsed out of post_content, scattered across thousands of posts, with no admin column to summarise it.
SleekView walks parse_blocks() on every post and renders one row per post-block pair. Block name, source post, author, post type, scheduled visibility window and permission scope become first-class columns with sort, filter and inline navigation. A design system owner can scope the table to a single block, an admin can pull every block currently restricted from contributors, and an editorial lead can find the posts using a block that is about to be retired.
The plugin keeps owning the editor, the permission map and the per-block settings. The table view owns the audit surface, so block sprawl, permission drift and stale scheduled rules stop hiding inside per-post content.
Workflow
How SleekView surfaces PublishPress Blocks data
Parse blocks from post_content
parse_blocks() on every post and emits one row per post-block pair. Block name, source post and post type come straight from the parsed tree.
Read the permission map
wp_options. SleekView reads the same option so role scope renders as a column alongside the block name.
Filter and sort like a database
advgb/table, scheduled visibility expired or role scope excludes contributor. Sort by post modified to find the posts using a block that needs migrating off.
Save and gate the view
Sample columns
A typical PublishPress Blocks audit view
wp_posts
| Block | Post | Author | Post type | Schedule | Roles allowed |
|---|---|---|---|---|---|
| advgb/table | Pricing comparison | Marco D. | page | — | All |
| advgb/accordion | Help center | Priya S. | page | — | Editor, Author |
| advgb/columns-manager | Spring landing | Lena R. | page | Scheduled | All |
| advgb/icon | Feature highlights | Marco D. | post | Expired | Editor |
| advgb/contact-form | Contact | Priya S. | page | — | Editor, Admin |
Comparison
Default PublishPress Blocks admin vs SleekView
Default PublishPress Blocks admin
- Block usage across posts is invisible, only the library itself is exposed
- Permission map shows as toggles, not as a per-block role scope column
- Scheduled visibility rules live on the block, not as a sortable column
- No site-wide list of posts using a specific block
- Cross-post block reporting requires a custom WP_Query loop
SleekView
- Block name and source post as real columns from parsed content
- Role permission scope rendered next to the block on each row
- Scheduled visibility status (active, scheduled, expired) as a filter
- Inline navigation from any row into the editor for the source post
- Saved views per role: design audit, permission review, schedule cleanup
Features
What SleekView gives you for PublishPress Blocks
Block library as a real surface
Every PublishPress Blocks occurrence becomes a row with the source post, author and post type. Block usage stops being parsed in someone's head and becomes a queryable list.
Permission map as a column
The PublishPress Blocks role permission map is read from wp_options and rendered next to the block on every row. Permission drift after onboarding or offboarding surfaces in one filter.
Scheduled visibility as a status
Active, scheduled and expired visibility windows appear as a filterable column. Expired rules that are still in posts surface before they break a layout.
Audience
Who uses SleekView for PublishPress Blocks
Design system owners
Scope the table to a single block to see every post relying on it, useful before retiring a block or migrating to a new pattern.
Site admins
Filter to role scope excludes contributor to audit which blocks the contributor role can currently insert, and inline-correct any permission that drifted.
Editorial leads
Pull every post using a block that is going away in the next release, ship a cleanup sprint and confirm progress against the same filtered view.
The bigger picture
Why block libraries need a real audit table
PublishPress Blocks gives a multi-author site a real component library, with role-based permissions and scheduled visibility on top of the standard editor. The risk is the one every component library faces: half the blocks dominate every page, a quarter rarely get used, and permission rules drift quietly after every team change. The default admin shows configuration but not consumption.
SleekView walks parse_blocks() across every post and renders block usage, permission scope and scheduled visibility as sortable columns. Design system owners get the honest picture of what the team is reaching for, admins get a permission audit they can scan in five seconds, and editorial leads get a single table to point at when planning the next round of templates.
Questions
Common questions about SleekView for PublishPress Blocks
From parse_blocks() on each post's post_content. SleekView walks the parsed tree and emits one row per post-block pair, including nested inner blocks. The same data WordPress already uses to render the post drives the table.
Yes. The free plugin already registers its blocks and writes its permission map to wp_options, which is exactly the data SleekView reads. Pro features add extra blocks and additional settings, which become extra columns but are not required for the base audit.
Yes. The permission map in wp_options renders as a Roles allowed column on every row. Filter to a specific role to see exactly which blocks are currently enabled for it across the site.
Yes. Reusable blocks live in the wp_block post type and are referenced by id from post_content. SleekView resolves those references so reusable block reuse shows up as rows with the right source post.
Yes. Add a filter for post type and the whole table narrows to that scope. Useful for sites that ship landing pages, blog posts and product pages with different block usage expectations.
Not in practice. SleekView caches parsed block counts per post and refreshes only on post update. The first build of a heavy site walks the corpus once, and incremental updates run in milliseconds after that.
Inline edits route through the standard option update path PublishPress Blocks itself uses. Capability checks and registered hooks continue to fire, so the permission map stays consistent with what the plugin's own settings screen would produce.
Yes. Any filtered view exports to CSV with the block, post, author, post type and permission columns. Design system owners use it for quarterly audits and admins use it to document permission settings before a major user cleanup.
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 checkout