SleekView for Meta Box AIO
Meta Box AIO bundles every Meta Box extension under one licence. SleekView reads each module's storage, custom tables, frontend submissions, relationships, builder definitions, and surfaces them as inline-editable list tables.
♾️ Lifetime License available
AIO bundles a lot of plugins. The list table should cover all of them.
Meta Box AIO is the bundled tier that ships all twenty-plus Meta Box extensions under a single licence: MB Custom Table, MB Frontend Submission, MB Custom Post Type, MB Builder, MB Views, MB Relationships, MB Settings Page, MB User Profile and the rest. The bundle saves licence keys and dependency tracking, but the standard admin still surfaces each module on its own screen. A build that runs the full AIO needs a list-table layer that covers all of them, not just core field groups.
SleekView reads the registered storage of each AIO extension and turns the full set into a coherent table layer. Relationships become rows with source and target columns and the connection name. MB Custom Post Type entries query their post type directly. MB User Profile fields render on a user-scoped view. MB Settings Page becomes a one-row table per registered page. Frontend submissions and custom-table-backed datasets each get their own list with field values inline.
Inline edits go through Meta Box save hooks regardless of which extension owns the data, so module-specific logic continues to fire. The same dataset can be flipped to a kanban or feedback view, useful for workflows that need a board over the row data.
Workflow
Turn the AIO bundle into one table layer
Choose extensions
Compose the column set
Save a bundle view
Edit inline
Sample columns
A typical Meta Box AIO relationship view
postmeta, termmeta, usermeta plus MB Custom Table and MB Relationships
| Source | Connection | Target | Source type | Target type | Created |
|---|---|---|---|---|---|
| Case study: SaaS launch | Features | All Access Pass | post | product | Apr 24 |
| Pricing FAQ | Mentions | Plus plan | post | product | Apr 23 |
| Tutorial: meta boxes | Related | Quickstart guide | post | post | Apr 22 |
| Old changelog entry | Deprecated | — | post | — | 1 year ago |
Comparison
Default AIO admin vs SleekView
Default Meta Box AIO admin
- Each bundled extension lists its own data on its own screen
- MB Relationships pairs do not surface as rows in a list table
- Frontend submissions and custom table rows live on separate admin pages
- Bulk editing across extensions requires custom code
- Builder-defined field groups never surface as columns in core admin
SleekView
- Cross-module list tables for the full AIO bundle
- MB Relationships pairs as rows with source, target and connection
- MB Custom Table datasets queried through the dedicated table
- Inline edits routed through the appropriate Meta Box save path
- Save filtered views per role with capability-based gating
Features
What SleekView gives you for Meta Box AIO
Every AIO extension in one layer
AIO bundles many plugins. SleekView surfaces each one as a table so a developer or ops lead does not have to click through twenty modules to see and edit the underlying data.
Relationships as rows
MB Relationships pairs become first-class rows. Filter by source, target or connection name and bulk-edit links from the same screen as the data they connect.
One source of truth
Every column reads Meta Box's documented storage. No nightly sync, no parallel database, no chance that the table disagrees with the editor.
Audience
Who uses SleekView for Meta Box AIO
WordPress developers
Audit which AIO modules are actually used on a build. Bulk-edit relationships, custom-table rows and submissions without writing one-off admin tooling.
Forms and lead ops
Treat MB Frontend Submission as a real lead surface. Filter entries by form and status and triage them inline from the same list.
Agency leads
Hand over an AIO build with a structured editing UI for every bundled extension. Clients see and edit their own data without bespoke admin pages.
The bigger picture
Why bundling more plugins demands more list tables
Meta Box AIO is a strong proposition for agencies and large builds because every extension comes pre-licensed and pre-integrated. The flip side is that the build's surface area grows quickly. A typical AIO install has custom tables alongside postmeta-backed groups, frontend submissions alongside back-end editors, relationships alongside taxonomies, builder-defined groups alongside hand-coded ones.
The standard Meta Box admin surfaces each module separately and never tries to unify them. SleekView does the unification at the list-table level. It reads the documented storage paths each AIO extension uses, treats them as one dataset family and renders each as a sortable, filterable, inline-editable table.
That changes what the AIO licence is buying: not just more features, but a build that can be browsed and edited as rows.
Questions
Common questions about SleekView for Meta Box AIO
No. SleekView reads the storage paths of whichever AIO extensions are active. The table layer adapts to the bundle's actual configuration, so a build that disables MB Views or MB User Profile still gets coherent views from the modules that remain.
Yes. MB Relationships records pairs in its own table. SleekView surfaces that as a dataset, with source, target and connection name columns, and supports filtering and inline edits like any other view.
The standalone Meta Box view covers core field groups well. The AIO bundle adds extensions that core SleekView still surfaces, but the AIO page documents the full module coverage in one place: relationships, settings pages, custom tables and the rest.
Yes. MB Builder is the visual UI that registers field groups. The registered definitions drive both Meta Box's editor and SleekView's columns, so inline edits run through Meta Box's documented save paths.
Yes, when both share a logical key. Otherwise build separate views and put them side by side on the same page using SleekView's tabbed layout, which keeps each dataset queried natively.
Yes. MB Settings Page registers global option storage. SleekView treats each settings page as a one-row dataset and surfaces every registered option as a column, with inline edit support.
Yes. Each saved view sits behind a WordPress capability check, so forms ops can see the submission table, developers can see the relationship and custom-table views, editorial leads can see content coverage only.
No. Every column runs on the same storage Meta Box uses for the editor: postmeta, termmeta, usermeta, custom tables and registered options. There is no nightly export and no risk of disagreement between table and editor.
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