SleekView Charts for Toolset Types
Read directly from postmeta with the wpcf- prefix and the Toolset relationships table, then chart listings by status, agents by load, and price ranges without building a Views template.
♾️ Lifetime License available
Toolset stores the data, charts give the admin a real summary
Toolset Types registers custom post types as native posts and stores field values in postmeta under the wpcf- prefix, with parent, child, and many-to-many relationships in a dedicated Toolset relationships table. Out of the box the admin lists rely on WordPress defaults and Toolset Views handles richer presentation, but Views is a front-end tool, and using it for admin reporting always feels like a workaround.
SleekView Charts reads the Toolset registry directly and pivots wpcf- meta keys into chart sources. A Number card pins the count of active listings. A Pie shows distribution by status. A Bar ranks agents by listing load using the relationships table. An Area card plots new listings over time using post_date so seasonal pipeline shows as a trendline.
The integration is admin-only and coexists with the wider Toolset suite. JetSmartFilters, Toolset Views, and any front-end listing template keep working because SleekView reads the same data layer, not a parallel copy. Saved chart views per role mean sales, ops, and admin each get the cards that match their workflow.
Workflow
How SleekView Charts reads Toolset Types data
Pick a Toolset type
Map wpcf- keys to chart cards
Filter on Toolset values
Save per role
Sample dashboard
Charts you can build from Toolset Types data
Active listings
Count
Listings by status
Count
group by wpcf-status
Listings per agent
Count
group by agent_relationship
New listings per day
Count
group by post_date
Comparison
Default Toolset reporting vs SleekView Charts
Default Toolset admin
- Toolset has no admin chart view, only paginated post lists
- Building a usable summary often means a Toolset Views listing
- Relationship-driven counts (listings per agent) need custom queries
- Numeric and date wpcf- fields don't aggregate in the admin
- Cross-type dashboards require stitching multiple Views together
SleekView Charts
- Number cards for live counts of records by wpcf- field
- Pie or Donut cards for status and select-field distributions
- Bar cards ranking related posts using the Toolset relationships table
- Area or Line cards for new records over time by post_date
- Same filters as the SleekView table apply to every chart card
Features
What SleekView Charts gives you for Toolset Types
wpcf- meta as chart sources
Every Toolset custom field becomes a chart group-by candidate. The chart editor reads the Toolset registry, so adding a field surfaces it in the picker on the next open.
Relationships in chart cards
The Toolset relationships table powers Bar cards that count related posts per parent. Agents per office, listings per agent, sessions per event all become single-card summaries.
Type-aware aggregations
Numeric, date, and currency wpcf- fields aggregate correctly because SleekView reads the underlying meta type from Toolset's registry, not the raw string in postmeta.
Audience
Who builds Toolset Types charts dashboards with SleekView
Real estate sites
Active vs sold listings, average price by region, and a per-agent leaderboard, all on one dashboard instead of one Views listing per slice.
Directory site operators
Members by category, businesses by city, and event volume over time, charted directly from Toolset relationships without a separate analytics plugin.
WordPress developers
Audit content-model coverage during migrations, chart populated-field counts per type, and hand clients a dashboard that tracks the schema as it evolves.
The bigger picture
Why Toolset Types sites need a chart layer
Toolset's appeal has always been that it lets non-developers build serious content models inside WordPress: custom post types, wpcf- fields, taxonomies, and a real relationships table. The trade-off, especially on Toolset-heavy sites, is that the admin and reporting story for those models is light by default. Views was designed for the front end, and using it for admin dashboards is awkward: it renders through the theme, doesn't aggregate cleanly across record sets, and needs a developer touch every time the model changes.
Teams running real estate sites, directories, or event platforms end up either building separate dashboard pages with Views widgets or accepting that the admin is for editing one record at a time. SleekView Charts fills the missing summary layer. The same wpcf- meta, the same relationships table, the same registry, now exposed as Number, Pie, Bar, and Area cards that refresh as records change.
Views still owns the front end; SleekView owns the back-end reporting surface where the team actually triages the model.
Questions
Common questions about SleekView Charts for Toolset Types
Yes. Even though the public Toolset Types plugin was discontinued, sites running it (or the wider Toolset suite) still keep data in standard postmeta with the wpcf- prefix and the dedicated relationships table. SleekView Charts reads the same layer the rest of Toolset reads, so the chart dashboard stays in sync as long as the data is there.
Yes. Parent, child, and many-to-many relationships from the Toolset relationships table power Bar cards that count related posts per anchor. Agents per office, listings per agent, sessions per event all become single chart cards without a manual SQL join.
Yes. SleekView reads the underlying meta type from Toolset's registry, so price fields sum as numbers (not strings), date fields group by day or month correctly, and currency fields preserve their formatting at render time. The alphabetic ordering you get from a raw meta sort is replaced with type-aware aggregation.
Yes. Views remains the front-end display layer for visitors. SleekView Charts adds the admin reporting layer that Views was never really designed for. Both can coexist on the same model because they read and write the same wpcf- meta and relationships data with no sync layer in between.
Toolset custom taxonomies are registered as native WordPress taxonomies, so term assignments show up as chart group-by candidates the same way native categories do. A Pie card grouped by term gives a working content-by-category dashboard without custom code.
Yes. Chart queries hit the same indexes WordPress and Toolset already use, and the chart layer only reads the columns the active cards reference. Heavy relationship cards load on demand, so even directory sites with tens of thousands of records and dense many-to-many relationships stay responsive.
Yes. Each saved chart view is gated by WordPress capability, so a sales dashboard, an ops dashboard, and an admin dashboard can live alongside each other with role-appropriate cards. The underlying Toolset data is the same; the chart selection is per role.
Yes. SleekView Charts is read-only at the chart layer and only writes through Toolset's own update functions on inline edits in the SleekView table. There is no schema migration, no extra Toolset table, and no background job that touches the relationships table. Deactivating SleekView returns the admin to its prior state with all wpcf- meta untouched.
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