SleekView for WPGraphQL for ACF
SleekView reads the acf-field-group post type WPGraphQL for ACF augments, then renders show_in_graphql, graphql_field_name, field type and last modified as sortable audit columns inside WP Admin.
♾️ Lifetime License available
Exposure is a checkbox. The audit is the missing surface.
WPGraphQL for ACF adds a show_in_graphql checkbox to every ACF field group, plus a graphql_field_name slug that controls how the group lands on the schema. Per group, it's trivial: tick the box and the fields appear in GraphQL. Across a site with hundreds of groups, the cumulative public schema is the part nobody owns.
SleekView reads the acf-field-group post type directly, parses the group settings JSON stored in post_content and exposes show_in_graphql, graphql_field_name, graphql_type_name and the underlying ACF field types as real columns. A schema owner can filter to show_in_graphql = true, sort by graphql_type_name and see in one screen which types carry the heaviest field load and which groups quietly opened up sensitive data.
WPGraphQL for ACF keeps owning the schema registration. The table view owns the audit surface, so accidental exposures, unused fields and silent drift stop hiding inside per-group settings panels.
Workflow
How SleekView surfaces WPGraphQL for ACF data
Point at the field group posts
Join the field rows
Compose the columns
Save and gate the view
Sample columns
A typical WPGraphQL for ACF exposure audit
wp_posts
| Field group | GraphQL type | Field name | Fields | Exposed | Modified |
|---|---|---|---|---|---|
| Hero section | Page | hero | 5 | Yes | 2026-05-12 |
| Product specs | Product | productSpecs | 12 | Yes | 2026-04-29 |
| Internal editor notes | Post | editorNotes | 3 | Yes | 2026-05-10 |
| Author bio | User | authorBio | 4 | Yes | 2026-02-14 |
| Legacy banner | Page | — | 6 | No | 2024-09-03 |
Comparison
Default ACF + WPGraphQL admin vs SleekView
Default ACF + WPGraphQL admin
- Exposure is one checkbox per group, never an aggregate column
- No site-wide audit of which groups land on which GraphQL types
- Field types live inside each group's edit screen, never as columns
- Newly exposed groups have no review surface before they ship
- Schema reviews start from a spreadsheet someone built by hand
SleekView
- show_in_graphql and graphql_field_name as real, filterable columns
- Filter to exposed = true to scope the table to the public schema
- Sort by graphql_type_name to see exposure per GraphQL type
- Saved views for schema owners, frontend leads and security reviewers
- Same dataset the chart view reads, so table and dashboard stay in sync
Features
What SleekView gives you for WPGraphQL for ACF
Exposure as a real column
show_in_graphql and graphql_field_name move from per-group settings into first-class table columns, so a schema owner sees the public surface without clicking through every group.
Filter the public schema
Stack filters on exposed, graphql_type_name and field_type to pull every relationship field on the User type, or every repeater exposed in the last month, in one query.
Catch accidental exposures
Sort by post_modified descending and filter to exposed = true to see the most recently exposed groups, so an internal-notes group flipped on by mistake surfaces the same day it ships.
Audience
Who uses SleekView for WPGraphQL for ACF
Schema owners
A saved view of every exposed group with its type and field count becomes the working surface for deprecations, renames and gated additions to the public schema.
Frontend leads
Filter to graphql_type_name = Page and a new developer sees the actual coverage map their frontend reads from, instead of poking through the schema explorer.
Security reviewers
A view filtered to exposed = true and sorted by post_modified surfaces newly exposed groups before they reach production, with a CSV export for the compliance log.
The bigger picture
Why a checkbox per group needs a site-level audit
WPGraphQL for ACF makes exposure trivial, which is precisely what makes the cumulative public schema invisible. One checkbox, applied to dozens of groups over months, ends up exposing relationship fields, internal notes and admin metadata that nobody intentionally signed off on. SleekView reads the acf-field-group post type WPGraphQL for ACF already augments and renders show_in_graphql plus graphql_field_name as real columns.
Schema owners filter and sort, security reviewers run the same audit every quarter, frontend leads stop guessing. The plugin keeps owning schema registration. The table view owns the audit surface, so silent drift becomes a one-screen conversation instead of a multi-hour archeology project.
Questions
Common questions about SleekView for WPGraphQL for ACF
From the standard acf-field-group post type and the group settings JSON stored in post_content, which is where show_in_graphql and graphql_field_name live. The acf-field rows for individual fields are read on the same dataset.
Both. ACF and ACF Pro write the same field-group post type, and WPGraphQL for ACF augments it the same way on either edition. SleekView reads the post type directly, so the audit works on any combination.
Yes. graphql_type_name is a sortable column with a filter, so the table can scope to Page, Post, MediaItem, custom post types or ACF Options. Useful for finding which type carries the heaviest field load.
Both. WPGraphQL for ACF v2 (the rewrite) and the older registry both expose the same show_in_graphql flag on the ACF group, so the table reads from the source of truth (the ACF post) and tolerates either version of the bridge plugin.
Yes, when the WPGraphQL query log is on. Join the field exposure table to the query log dataset, filter to graphql_query_count = 0 and the resulting list is the natural starting point for a schema cleanup sprint.
Toggling show_in_graphql inline routes through the standard WordPress update path, the same one ACF and WPGraphQL for ACF listen to. Schema regeneration fires exactly as it does from the field group edit screen.
Yes. Any filtered set exports as CSV with field group, type name, field name, exposure flag, field count and modified date. Schema reviews use the export as their authoritative coverage record.
No. The plugin still owns per-group settings and the schema bridge. SleekView adds a site-wide audit table on top of the data WPGraphQL for ACF already maintains, so exposure decisions stop being one-at-a-time and become measurable.
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