✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Forminator: form & poll submissions as tables

Forminator splits forms, polls, and quiz submissions across frmt_form_entry and frmt_form_entry_meta. SleekView reads them all and joins to the form definitions in posts so a single workspace can triage every submission type.

♾️ Lifetime License available

SleekView table view for Forminator

Forms, polls, and quizzes in one cross-type view

Forminator stores submissions in two custom tables: frmt_form_entry holds one row per submission with form_id and date_created, and frmt_form_entry_meta stores each field value as its own row keyed by entry_id and meta_key. The form definitions themselves live in wp_posts as three different CPTs — forminator_forms, forminator_polls, and forminator_quizzes — so reconstructing a single submission means joining three sources for the form name and pivoting many meta rows into one record.

The default Forminator admin handles each form type in isolation. Submissions for one form, votes for one poll, attempts for one quiz — each on its own screen with fixed columns that don't surface the field values inline. Cross-form views, where ops want to see every submission across forms and polls together filtered to the last 24 hours, aren't a built-in screen and require either reports or SQL.

SleekView reads frmt_form_entry and frmt_form_entry_meta directly, joins to the CPT-stored form definition for the form name and type, and pivots the meta rows into named columns at query time. The result is a single cross-type workspace where every submission, vote, and quiz attempt shows up with the field values you care about as proper columns.

Workflow

Submissions across forms, polls, and quizzes

1

Connect the tables

Point SleekView at frmt_form_entry and frmt_form_entry_meta. Add a join to wp_posts on form_id to pull the form title and identify whether each entry belongs to a form, poll, or quiz.
2

Pivot the meta values

Map each meta_key in frmt_form_entry_meta to a column. Long-format field values become named columns so each submission renders as one row with email, message, and any custom field visible inline.
3

Build cross-type views

Create a saved view that combines all three submission types with form-type as a sortable column, then filter to last seven days, unread status, or by specific form ID. Save per role — form admin, poll moderator, quiz instructor.
4

Triage and edit inline

Mark entries read, update statuses, or correct field values directly in the table. Use Forminator's submission API where hook-aware writes are needed; switch to direct DB writes for bulk-cleanup operations.

Sample columns

A typical Forminator submissions view

Cross-type entries across forms, polls, and quizzes with form-name and form-type as columns.
Source: wp_frmt_form_entry + wp_frmt_form_entry_meta + wp_posts (forminator_*)
Entry Form Type Submitted Status
#412 Contact Form Apr 24 Unread
#411 Mood Poll Poll Apr 24 Voted
#410 CSS Quiz Quiz Apr 23 Submitted
#409 Demo Request Form Apr 23 Read

Comparison

Default Forminator admin vs SleekView

Default Forminator admin

  • Submissions are scoped per form/poll/quiz in the default admin
  • Field values in frmt_form_entry_meta aren't surfaced as columns by default
  • Cross-type tables (forms + polls + quizzes) require custom queries
  • Filtering by form-type + date range together isn't a saved view
  • Bulk inline editing isn't first-class

SleekView

  • Cross-type entries from forms, polls, and quizzes
  • Pivot frmt_form_entry_meta into named columns
  • Filter by form-type, form-name, and date range together
  • Inline-edit entry status across submissions
  • Save views per role (form admin, poll moderator, quiz instructor)

Features

What SleekView gives you for Forminator

Pivot meta into columns

frmt_form_entry_meta rows pivot into named columns at query time. Each submission shows up as one readable row with the field values inline rather than spread across many meta rows.

Cross-type filters

Combine form, poll, and quiz submissions in a single view with form-type as a sortable column. Filter by date range, form ID, or status across all submission types at once.

Inline edit and moderate

Update submission status, mark entries read, or correct field values in place. Bulk-resolve poll votes or quiz attempts without opening each entry individually.

Audience

Who uses SleekView for Forminator

Form admins

All form submissions in one cross-form table, filtered to unread plus last 7 days. Status updates flow inline so the daily triage queue empties without clicking each entry.

Poll moderators

Poll-vote tallies grouped by selected option, filterable by date and form ID. Spot brigading or stale polls without leaving the table.

Quiz instructors

Per-quiz score tables sorted by submission date. Find top scores, identify stalled attempts, and export results as CSV directly from the saved view.

The bigger picture

Why cross-form submission views matter

Form-driven sites rarely have one form. A typical Forminator install runs a contact form, a demo-request form, a couple of polls embedded in pages, and maybe a quiz or two for engagement — each generating its own stream of submissions, each with different field shapes, each currently siloed in its own admin screen. The operational reality is the opposite: someone needs to scan everything that came in today, mark the ones that need follow-up, and route the rest.

With submissions in frmt_form_entry and field values in frmt_form_entry_meta, the data already supports a cross-type view; the default admin just doesn't compose one. SleekView's pivot collapses the long-format meta into a flat table joined to the form CPT, so the screen finally matches the workflow. Combine that with a date-range filter and a status column, and triaging the day's submissions becomes one query instead of clicking through every form individually.

For teams running quizzes or polls alongside forms, that consolidation is the difference between hours of admin and a single saved view.

Questions

Common questions about SleekView for Forminator

Not publicly. SleekView confirms entry_id, form_id, date_created, and the relationship to frmt_form_entry_meta via entry_id. Other columns are exposed as they appear on your installation, but column names and types beyond that core set aren't documented in Forminator's public docs as of 2026 — verify against your own database before depending on a specific field.

 

Yes. SleekView writes back to frmt_form_entry_meta with conflict detection so concurrent edits don't silently overwrite each other. Use Forminator's submission APIs where they exist for hook-aware updates; direct DB writes are fine for bulk cleanup that doesn't need to re-fire integrations.

 

Yes. Group entries by the relevant poll option meta_key and aggregate the count to get a live tally view. Combine with a date filter to see vote distribution over the last day, week, or campaign window — useful for moderating polls in-flight.

 

Forminator's own per-form views remain available and unchanged. SleekView complements them by adding a cross-form, cross-type workspace that the per-form views can't provide. Use both: Forminator's view for deep edits inside a single form, SleekView for the triage and bulk operations across forms.

 

Yes. Form definitions live in wp_posts with forminator_forms, forminator_polls, and forminator_quizzes as their post types. Join entries to posts on form_id and use post_type as a filterable column; that becomes the form-type sort and filter.

 

When SleekView uses Forminator's submission API, hooks fire as expected — including any registered after-save filters or notification routing. Direct DB writes skip hooks by design, which is the right choice for bulk data cleanup but the wrong choice for status changes that need to email the submitter.

 

Yes. Any SleekView view exports as CSV or JSON, including cross-type views with pivoted meta. Build a saved view filtered to last week's submissions across all forms and export it; that becomes the weekly report without scripting an export job.

 

File-upload values in Forminator are stored as URLs or attachment IDs in frmt_form_entry_meta. SleekView surfaces the value as a column — render it as a link or thumbnail — and the underlying file in the WordPress media library is unaffected by view-level edits.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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