SleekView for WP All Import: imports & history as tables
WP All Import logs every run to the pmxi_imports, pmxi_history, and pmxi_posts tables. SleekView reads them directly so import audits, per-run counts, and post-to-feed provenance live in one workspace without writing SQL.
♾️ Lifetime License available
Import history as a workspace, not an opaque log
WP All Import operates on a fork-and-poll cycle: each scheduled or manual run inserts a row into pmxi_imports, accumulates per-batch counts in pmxi_history, and registers every created or updated post in pmxi_posts. The default plugin UI surfaces those tables as one log per import — fine for a single feed, painful when an agency has thirty active imports running on staggered cron schedules.
SleekView treats the pmxi_ family as a flat workspace. A view over pmxi_imports joined to pmxi_history shows created, updated, skipped, and deleted counts for every run as columns, sortable across imports. A second view joins pmxi_posts back to the parent import so any product or CPT row carries its source feed and last touched timestamp.
That two-view setup answers the questions WP All Import customers actually ask in tickets: which import created this orphan product, why are skipped counts climbing on the vendor catalog, and which scheduled imports haven't run since the last cron change. None of those need SQL or per-feed drilling once the views exist.
Workflow
Audit every WP All Import run from one screen
Map the pmxi_ tables
Pivot run counts inline
Join post provenance
Save role-scoped views
Sample columns
A typical import history view
wp_pmxi_imports + wp_pmxi_history + wp_pmxi_posts
| Import | Run | Created | Updated | Skipped | Status |
|---|---|---|---|---|---|
| Products feed | Apr 24 03:00 | 12 | 1,204 | 0 | OK |
| Stock levels | Apr 24 02:00 | 0 | 3,408 | 12 | OK |
| Vendor catalog | Apr 23 23:00 | 204 | 0 | 8 | Partial |
| Legacy CSV | Apr 23 11:00 | 0 | 0 | 0 | Failed |
Comparison
Default WP All Import admin vs SleekView
Default WP All Import admin
- Run history is hidden behind per-import pages
- Cross-import comparison needs jumping between screens
- Filtering by status or run age isn't a saved view
- Per-post provenance (which import created post X) is hard to surface
- Bulk-rerun or pause imports go one at a time
SleekView
-
Read
pmxi_importsandpmxi_historydirectly - List every run with created/updated/skipped/deleted counts
- Filter by status, scheduled flag, and run age
-
Join
pmxi_poststo surface per-post import provenance - Save views per ops or data-quality role
Features
What SleekView gives you for WP All Import
Run history at a glance
Every run across every import in one sortable list with created, updated, skipped, and deleted counts inline. Spot vendor-feed drift before support tickets land.
Post provenance
Join wp_pmxi_posts so any product or CPT row carries its source import and last-touched timestamp. Orphan-record investigations stop being archaeology.
Status filters
Filter to failed or partial runs across every import to triage data-quality issues without leaving WP admin or paging through per-feed screens.
Audience
Who uses SleekView for WP All Import
Data ops
Daily audit covering every scheduled import with created, updated, and skipped counts in one ranked view. Catches drift before it hits the storefront.
Data quality
Investigate skipped or deleted records across the vendor catalog before they become support tickets, with per-run history filterable by status and age.
Support
Per-post provenance during customer chats — instantly know which feed last touched a SKU and when, without opening the WP All Import UI at all.
The bigger picture
Why import history needs to be a workspace
WP All Import is rarely deployed as a single feed. Most production sites run a vendor catalog import, a stock-levels feed, a price feed, and a few legacy CSVs scheduled across the day. The plugin's own UI is built around editing one import at a time, so a missed run on the stock feed and a partial run on the vendor catalog don't show up together unless someone opens both screens.
That is exactly when data drift becomes a customer support ticket. Reading pmxi_imports and pmxi_history directly turns the question from "which import did this come from" into a sortable column. Skipped counts climbing on the vendor catalog stop hiding behind per-import pagination.
Stale scheduled imports that haven't run since cron got rewritten surface in a single filter. The pmxi_posts table makes orphan-record investigations a one-click filter on source import and last-run timestamp. That visibility shifts WP All Import from a tool ops teams hope is working to one they can audit before the morning standup.
Questions
Common questions about SleekView for WP All Import
Yes. Pro adds extra columns for scheduling and cron handling but the underlying tables remain the pmxi_ family — pmxi_imports, pmxi_history, pmxi_posts, pmxi_images, and pmxi_templates. SleekView reads both Free and Pro from the same view configuration without any switch needed.
Yes. SleekView calls WP All Import's run-import API on row actions where supported, so the same hooks that fire on a manual run continue to fire — including image-pipeline and post-process steps. The action is gated by capability, so only authorized roles see it.
Yes. The pmxi_images table tracks every image attempted by the importer with its source URL, attachment ID, and any error. SleekView exposes that as a separate joinable view so image-pipeline failures are filterable alongside the parent import run.
Yes. The scheduled flag stored on each pmxi_imports row is exposed as a filterable column, so you can isolate cron-driven runs from manual ones. That makes diagnosing missed cron events much faster than scrolling per-import screens.
Yes. SleekView paginates and indexes server-side, so even sites with hundreds of thousands of pmxi_history rows render quickly. The pmxi_ tables are already indexed by import_id and run timestamp, which the views take advantage of.
Yes. Views are gated by WP capability so different roles see different column sets — a support view might omit raw error payloads while data ops sees everything. Each role can also save its own filtered presets.
Build a SleekView page over wp_posts joined with pmxi_posts. Each post row carries the import_id of whichever feed last created or updated it, plus the timestamp. Filter by post ID or SKU to pinpoint the source feed instantly.
Yes. Add a computed column on the runs view comparing the current skipped count to the rolling average for that import. Sort descending to surface anomalies first. That is the single most useful audit pattern for vendor-catalog drift.
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