SleekView for WP User Frontend: front-end posts & transactions as tables
WP User Frontend publishes front-end submissions as WordPress posts and tracks paid posts in wpuf_transaction. SleekView joins wp_posts with the transaction table, pivots wp_postmeta custom fields, and gives moderators one workspace for both content and payments.
♾️ Lifetime License available
Submissions and transactions in one filterable workspace
WP User Frontend uses two main data stores. Front-end submissions land in wp_posts with the form's custom fields written to wp_postmeta, just like normal posts. Paid submissions and subscription payments are recorded in the plugin's own table, wpuf_transaction, with status, amount, gateway, and the related post ID. Two tables, two admin screens, and a workflow that needs both.
SleekView reads wp_posts filtered by WP User Frontend form metadata, joins wp_postmeta for the plugin's keys (and any ACF or custom field the form captures), and left-joins wpuf_transaction on the post ID so paid posts show their transaction status and amount as columns. wp_users joins on author for submitter email and role, completing the row.
Moderators can approve pending front-end posts, edit custom fields, change taxonomies, and reconcile paid submissions against transactions, all from one filterable table. Edits route through wp_update_post and update_post_meta so registered WP User Frontend hooks (publish, expiration, subscription) keep firing.
Workflow
From split screens to one front-end workspace
Filter wp_posts
wp_posts filtered by the WP User Frontend form-source meta key. The base view now shows only front-end submissions across all forms.
Pivot the meta
wp_postmeta key from the plugin or ACF as a column. Per-form custom fields appear immediately because the pivot runs at query time.
Join wpuf_transaction
Approve and reconcile
wp_update_post; reconcile transactions inline. Standard WordPress hooks and the plugin's update functions fire on every change.
Sample columns
A typical WP User Frontend submissions view
wpuf_transaction so paid submissions show their payment status and amount inline.
wp_posts (filtered by WP User Frontend form) + wp_postmeta + wp_wpuf_transaction + wp_users
| Title | Author | Submitted | Status | Payment | Amount |
|---|---|---|---|---|---|
| Vintage typewriter for sale | alex@studio.co | Apr 24 | Pending | Pending | $15.00 |
| Featured listing: Riso prints | ria@design.io | Apr 24 | Published | Paid | $29.00 |
| Wanted: studio space | tom@hello.dev | Apr 23 | Published | Free | — |
| Spam listing body | guest@nope.io | Apr 23 | Rejected | Failed | $15.00 |
Comparison
Default WP User Frontend admin vs SleekView
Default WP User Frontend admin
-
Front-end submissions and
wpuf_transactionrecords live on separate screens -
Custom field values from
wp_postmetaonly show inside the per-post edit screen - Bulk-approving pending submissions across forms is limited and tied to standard Posts UI
- Filtering by payment status alongside post status is not a first-class workflow
- Per-form moderation queues with form-specific custom fields require manual filtering
SleekView
- Posts joined with wpuf_transaction so paid submissions show payment status inline
-
Pivot
wp_postmetaform fields into typed columns automatically - Filter by form, post status, payment status, and pivoted fields together
- Inline approve, reject, edit fields, or reconcile transactions across many rows
- Save filtered views per moderator role (editorial, payments, subscriptions)
Features
What SleekView gives you for WP User Frontend
Posts joined with payments
Left-join wpuf_transaction onto front-end posts so paid submissions show transaction status, gateway, and amount in one row. Reconciliation is a filter, not a CSV export.
Pivot form fields
Per-form custom fields from wp_postmeta pivot into named columns. Each form's fields become first-class columns when you filter to that form.
Bulk approve and reconcile
Move submissions between statuses; mark transactions reconciled; edit fields across many rows. WordPress core APIs and the plugin's update functions route every change with hooks intact.
Audience
Who uses SleekView for WP User Frontend
Editorial moderation
Pending front-end posts cross-form with author email, form name, and payment status visible. Approve clean submissions in bulk; bounce spam without leaving the table.
Payments reconciliation
wpuf_transaction joined to posts by date and gateway. Reconcile paid listings against gateway payouts inline; export the filtered set to CSV for the bookkeeper.
Subscription management
Subscriber-pack purchases (post-credit allocations) listed with author and remaining-credits meta as columns. Spot expiring subscriptions and follow up before they lapse.
The bigger picture
Why content and payments belong in one view
WP User Frontend is two products glued together: a front-end content tool that creates real WordPress posts, and a payments tool that tracks transactions when those posts are paid placements. Architecturally the separation is correct (posts outlive any single transaction, transactions need their own audit trail), but operationally a moderator almost always needs both. A listing waiting for review is also waiting for its payment to clear.
A failed transaction means a published listing might need to come back down. A subscription pack that expired means a contributor's free posts should stop publishing. The default admin makes the operator do that join by hand.
SleekView reads both sources and puts them on one row. The composition does not change anything about how the plugin stores data; it changes whether the operator can see the question. Editorial moderation, finance reconciliation, and subscription oversight all share the same underlying tables, so they share the same SleekView.
Different saved views, same source, no per-team migration.
Questions
Common questions about SleekView for WP User Frontend
Many of the most useful views work with the free version: front-end posts, custom fields, basic moderation. Payment and subscription views require Pro because that is when wpuf_transaction is actively used. SleekView reads what is there, so the feature set expands with your WP User Frontend tier without configuration on the SleekView side.
Yes. Custom field values are stored in wp_postmeta and SleekView edits them via update_post_meta, so all standard filters and actions run. Any registered WP User Frontend or ACF hooks fire on the edit as if it had happened in the per-post screen.
The plugin writes a form-source meta key to wp_postmeta on each submission. SleekView filters on that key for a strict WP User Frontend view, or adds it as a column for a mixed view that includes admin-authored posts alongside front-end ones.
SleekView left-joins wpuf_transaction on the post ID with the most recent transaction per post surfaced as columns. Left-join means free posts stay visible with payment columns blank, so a moderation view of all pending submissions still shows payment context where it exists.
Yes. Filter wpuf_transaction by gateway and date range, sort by amount, and tick off rows as they match the gateway's payout report. The reconciled state can be a custom meta column on the transaction row, edited inline as you confirm each match.
Yes. Add the form-source meta key as a column or filter, then either focus on one form or leave it open for a cross-form view. Shared custom fields become useful cross-form columns; per-form-specific fields appear when you filter to that form.
Yes for any meta WP User Frontend writes to wp_postmeta or to its own tables. Subscription pack data, post credits, and expiration timestamps surface as filterable, sortable columns alongside the post and transaction data.
Yes. Save views and scope them per WordPress role or capability. Editorial sees the post queue, finance sees the payments-joined view, subscription managers see the subscription-pack and credits view. All views read the same source data; only the lens changes.
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