SleekView for ElementsKit for Elementor
Read _elementor_data, the ElementsKit modules option ek_modules and the header/footer builder CPT, then surface widgets, headers, footers and megamenus as one inline-editable workspace with status, type and author columns.
♾️ Lifetime License available
ElementsKit records, surfaced as rows
ElementsKit ships dozens of widgets plus a free header/footer builder, megamenu engine, layout library and parallax modules. Each used widget appears inside _elementor_data with an ekit- type prefix. The plugin holds module on/off state in ek_modules at the site level, and the header/footer builder maintains its own custom post type for saved headers, footers and megamenus.
The default ElementsKit admin is a tabbed settings screen with module toggles, plus separate screens for the header/footer builder and megamenu manager. It cannot answer "which pages use the Advanced Tab widget", "do we have a header for every site section" or "which megamenus are still active". SleekView reads the same meta, options and CPT records and renders the workspace those screens never quite become.
Inline edits route through standard WordPress CRUD, so ElementsKit's caches invalidate as expected. The Elementor JSON stays untouched, the editor owns layout, the table owns the row-level inventory across widgets, headers, footers and megamenus.
Workflow
How SleekView reads ElementsKit records
Pick the source
wp_posts filtered to _elementor_data for widget-level audits, or the ElementsKit header/footer builder CPT for headers, footers and megamenus. Each source exposes its own filterable columns.
Compose the column set
ekit- slugs actually present plus the active modules from ek_modules.
Save and scope the view
Edit inline and ship
Sample columns
A typical ElementsKit usage view
wp_posts + wp_postmeta (_elementor_data, ekit- widget slugs) + ElementsKit header/footer builder CPT
| Title | Type | Status | Author | Last edited | URL |
|---|---|---|---|---|---|
| Header — global | Header | Published | Den J. | Apr 25, 2026 | n/a |
| Footer — global | Footer | Published | Den J. | Apr 24, 2026 | n/a |
| Mega menu — Products | Megamenu | Draft | Mira S. | Apr 20, 2026 | n/a |
| Features | Page (ekit-advanced-tab) | Published | Lena R. | Apr 18, 2026 | /features |
| Old header | Header | Trashed | Tom B. | Jan 04, 2026 | — |
Comparison
Default ElementsKit admin vs SleekView
Default ElementsKit admin
- Settings screen, header builder and megamenu manager live on separate screens
- No single list spans widgets, headers, footers and megamenus
- Pages embedding a given ElementsKit widget cannot be listed without a search
- Author and last-edited columns are missing from the header builder list
- No shareable audit URL for header coverage or megamenu inventory
SleekView
- Widget pages and header/footer/megamenu CPT records in one queryable table
- Filter by widget slug, template type, module, status, author or last edited
- Inline-edit status, slug and author on ElementsKit records
- Saved views per role (audit, coverage check, editorial pipeline)
- CSV export of any filtered slice for client handovers
Features
What SleekView gives you for ElementsKit for Elementor
Header and megamenu coverage as columns
Template type from the header/footer builder CPT becomes a filterable column. Confirm every site section has a header, footer and megamenu without flipping between screens.
Audit-grade filters
Combine widget slug, template type, status, author and last-edited. Each filter saves as a named view so coverage checks run in seconds, not screen-by-screen scrolls.
Inline metadata edits
Update status, slug or author across ElementsKit records directly in the row. Updates route through standard WordPress CRUD so module caches refresh as expected.
Audience
Who uses SleekView for ElementsKit
Agencies
Per-client ElementsKit audits as one table: widget pages, headers, footers and megamenus side by side, with last-edited and status visible at a glance.
Information architects
Megamenu inventory and header coverage by type surface IA gaps long before users see them, especially on multi-section marketing sites.
Editorial ops
Filter ElementsKit widgets by slug and author to ground editor training in real usage and surface long-tail widgets ready for retirement.
The bigger picture
Why ElementsKit installs deserve a working table
ElementsKit's appeal is breadth: an Elementor widget pack plus a free header/footer builder plus a megamenu engine plus a layout library in one plugin. Breadth is also what makes the default admin hard to read as a coverage map. Three screens, three CPTs and one settings tab tell you what is enabled, but not whether every site section has a header, every header carries a megamenu or every active module is actually pulling weight.
SleekView reads the same meta, options and CPT records as a working table source. Headers, footers, megamenus and widget pages live in one filterable inventory. Coverage checks become a deliverable.
Stale records become a clean-up brief. The plugin keeps owning the editor and the builder, the table owns the row-level audit.
Questions
Common questions about SleekView for ElementsKit for Elementor
Directly from wp_posts and wp_postmeta (including _elementor_data), the ek_modules option for module flags, and the ElementsKit header/footer builder custom post type.
Yes. ElementsKit widgets carry an ekit- type prefix inside _elementor_data. SleekView decodes the JSON and exposes a widget-slug column for filtering, so picking a slug scopes the table to pages embedding that widget.
Yes. The ElementsKit header/footer builder uses a custom post type with a template_type column for header, footer and megamenu. Filter by template_type to confirm coverage across the site, and combine with status to spot drafts ready for promotion or retirement.
No. The _elementor_data JSON stays the editor's responsibility. SleekView edits the metadata around the layout: status, slug, author and any postmeta you choose to surface.
Yes. Updates route through the standard WordPress CRUD path, so ElementsKit's caches invalidate exactly as they would after a save in the editor or header builder.
Yes. ElementsKit widgets live inside the same _elementor_data JSON as Pro and core Elementor widgets. SleekView can list them together or filter to just the ekit- slugs.
Yes. Queries hit indexed columns on wp_posts, postmeta and the ElementsKit CPT. Widget-slug decoding can be cached for sites with thousands of pages.
No. The settings tab, header/footer builder and megamenu manager still own their configuration surfaces. SleekView adds a row-level audit layer on top of the records ElementsKit already writes.
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