SleekView for Toolset Types: custom post type & field tables
Toolset Types stores custom post types as native WP posts and fields under the wpcf- prefix, plus its own relationships table. SleekView turns each Toolset content model into a working admin table with fields, taxonomies, and related items as columns.
♾️ Lifetime License available
Manage your Toolset content models without bouncing between post lists
Toolset Types stores custom post types as native WordPress posts and field values as postmeta keyed with the wpcf- prefix. Many-to-many and parent-child relationships live in a dedicated relationships table that Toolset queries through its own API. The default Toolset admin lists rely on WordPress's standard columns, so even after you've defined a property type with bedrooms, price, location, and an agent relationship, none of that surfaces in the post list without a Toolset Views listing or custom column code.
SleekView reads Toolset's registered types and gives each one its own table with the fields, taxonomies, and related items as proper columns. A real estate listings view shows beds, price, location, and agent relationship in one row. Inline edits to text, number, select, and relationship fields go through Toolset's own field update handlers, so any custom field logic and Toolset Views queries stay in sync. Sorting and filtering work correctly on numeric and date fields because SleekView reads the underlying meta value type from Toolset's registry.
The integration is admin-only and coexists with Toolset Views. Views remains the front-end display layer; SleekView is for managing data inside the admin without opening each post. Even though the public Toolset Types plugin was discontinued, sites still running it (or the wider Toolset suite) keep their data in the same wpcf- meta and relationships table, which means SleekView continues to work as long as the data layer is in place.
Workflow
From wpcf- meta to working content-model tables
Pick a Toolset type
Build the columns
Filter on field types
Edit through Toolset
Sample columns
A typical Toolset Types properties view
WordPress posts/postmeta and Toolset relationship tables
| Listing | Beds | Price | Location | Agent | Status |
|---|---|---|---|---|---|
| Riverside loft | 2 | €420,000 | Berlin | Lena Park | Active |
| Suburban family home | 4 | €780,000 | Munich | Sam Ortiz | Pending |
| Lake cabin | 3 | €295,000 | Konstanz | — | Withdrawn |
| Studio apartment | 1 | €185,000 | Berlin | Lena Park | Active |
Comparison
Default Toolset admin vs SleekView
Default Toolset admin
- Custom post type lists rely on WordPress's default columns
- Toolset fields don't show as columns out of the box
- Relationship data is invisible on the post list
- Bulk editing of custom fields needs Views or custom code
- No combined view across related post types
SleekView
- One table per Toolset post type with its custom fields
- Show related posts inline (parent, child, many-to-many)
- Sort and filter by any custom field, including numeric and date types
- Inline edit text, number, select, and relationship fields
- Save views per role for editors, sales, or operations teams
Features
What SleekView gives you for Toolset Types
Custom types as proper tables
Each Toolset content model gets its own table with the columns you'd actually want, not just the WordPress defaults of title, author, and date.
Relationships in the same row
Display parent, child, and many-to-many connections inline so you can see which agent owns a listing or which event a session belongs to without opening the post.
Inline edit Toolset fields
Update prices, statuses, and selections in bulk without diving into each post. Changes save back through Toolset's own field handlers so existing hooks still fire.
Audience
Who uses SleekView for Toolset Types
Real estate sites
Review listings with price, beds, location, and agent in one row instead of opening each post. Reassign an agent or change a status inline when the deal moves.
Directory site builders
Manage members, businesses, or events without custom column code. Toolset relationships between businesses and categories surface inline as filterable columns.
WordPress developers
Stop building one-off admin screens for clients with rich content models. SleekView reads Toolset's registry directly, so the admin table tracks the model as it evolves.
The bigger picture
Why Toolset content models need a working admin table
Toolset's appeal has always been that it lets non-developers build serious content models inside WordPress without writing PHP. Custom post types, custom fields, custom taxonomies, and relationships all come from the same UI, and the data lives in standard WordPress tables with a small set of conventions on top. The catch is that the front-end story (Toolset Views) is more polished than the admin story.
The post list screens that ship with WordPress show titles and dates; everything that makes a listing a listing — beds, price, location, agent — sits invisible in postmeta until someone builds a Views listing or writes column code. For real estate sites, directories, and event-driven content, that means editors spend their time opening individual posts to verify a price or reassign an agent. SleekView restores the missing admin layer.
The same Toolset data, the same wpcf- meta, the same relationships table, but now as a sortable, filterable, inline-editable table. Views still owns the front end; SleekView owns the back end where the work actually happens.
Questions
Common questions about SleekView for Toolset Types
Yes. Even though the public Toolset Types plugin was discontinued, sites running it (or the wider Toolset suite) still store data in standard WordPress meta with the wpcf- prefix that SleekView reads. The relationships table, custom field registry, and post type registrations remain in place, so SleekView builds tables against the same data layer the rest of Toolset uses.
Yes. SleekView resolves parent, child, and many-to-many relationships and shows the related post titles inline. A many-to-many relationship can render as a comma-separated list of related titles or as a count, depending on how dense the relationship gets, and inline edits update both sides through Toolset's relationship API.
Yes. SleekView uses Toolset's field update functions where available so any custom field hooks still fire. Numeric and currency fields run through Toolset's value casting, select fields validate against the registered options, and relationship updates call the same API Toolset uses internally, which keeps Views queries and other Toolset features consistent.
Yes, alongside Views. SleekView is for managing data inside the admin; Views remains the front-end display layer. Edits made through SleekView are immediately visible to existing Views queries because both are reading and writing the same wpcf- meta and relationships data, and there is no separate sync layer to drift out of date.
Yes. Numeric, date, and currency fields sort correctly because SleekView reads the underlying meta value type from Toolset's registry rather than treating everything as a string. A sort by price descending returns 1,200,000 above 800,000 above 95,000, instead of the alphabetical ordering you'd get from a default WP_Query meta sort.
Yes. SleekView is read-only by default and only writes through Toolset's own update functions when you make an inline edit. There is no schema migration, no extra database table, and no background job that touches Toolset data. Deactivating SleekView returns the admin to whatever it looked like before, with all wpcf- meta and relationships untouched.
Toolset custom taxonomies are registered as native WordPress taxonomies, so SleekView reads them through the taxonomy API. Term assignments show as inline columns on the post table, and a separate taxonomy view shows term meta and term counts as columns. Filtering posts to a specific term combination is a stacked filter rather than a separate page.
Yes. SleekView paginates against the same indexes WordPress and Toolset already use, and only loads the columns you've added to the visible view. Heavy relationship columns load on demand, which keeps the initial query lean even on directory sites with tens of thousands of records and dense many-to-many relationships.
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