SleekView for WP Content Importer: content runs & created posts as tables
WP Content Importer stores per-run summaries in wp_options (under wpci_run_log) and stamps source provenance into wp_postmeta. SleekView reads both directly so content audits and rerun decisions stop being log-scrolling exercises.
♾️ Lifetime License available
Content imports with provenance built in
WP Content Importer is designed for one-shot bulk loads: WordPress eXtended RSS files, theme demo bundles, content packs. The plugin records each run as a serialized array in the wpci_run_log option and stamps each created post with _wpci_source_run and _wpci_source_file in wp_postmeta. The default admin shows runs as a chronological log without sort or filter.
SleekView parses wpci_run_log into a flat workspace. Each historical run becomes a row with file name, created count, updated count, skipped count, and the user who triggered it. Sorting by created count descending surfaces the heaviest demo imports first. Filtering by file extension separates WXR uploads from JSON content packs.
A second view joins _wpci_source_run back to wp_posts, so any imported page or post carries the run that created it. Removing demo content from a production site becomes a one-filter operation, not a manual hunt by post title.
Workflow
Audit every content run from one screen
Parse the run log
wpci_run_log option and projects each historical run as a row. Filename, counts, and uploader become typed sortable columns.
Surface counts inline
Join post provenance
_wpci_source_run back to wp_posts so each imported post exposes its source run and file. Cleanup becomes a one-filter operation.
Save cleanup presets
wp_posts by known demo run IDs. Re-run them before launch to safely remove starter content without title-by-title hunting.
Sample columns
A typical content runs view
wp_options (wpci_run_log) + wp_postmeta (_wpci_source_*)
| File | Run | Created | Updated | Skipped | Status |
|---|---|---|---|---|---|
| demo-content.xml | Apr 24 | 212 | 0 | 0 | OK |
| starter-pack.json | Apr 23 | 48 | 0 | 0 | OK |
| blog-archive.xml | Apr 22 | 1,408 | 12 | 4 | Partial |
| old-theme.json | Apr 18 | 0 | 0 | 0 | Failed |
Comparison
Default WP Content Importer admin vs SleekView
Default WP Content Importer admin
-
Run log lives in a single
wp_optionsblob, not a sortable list - Per-run counts hidden inside serialized PHP
-
Per-post provenance via
_wpci_source_runis buried in meta - Removing demo content means hunting by title, not filtering
- No way to compare two runs side by side in the plugin UI
SleekView
-
Parses
wpci_run_loginto a flat sortable view - Surfaces created, updated, and skipped counts per run
-
Joins
_wpci_source_runmeta back towp_postsfor provenance - Filters by file extension, uploader, or created-count threshold
- Saves cleanup presets for safely removing demo or test content
Features
What SleekView gives you for WP Content Importer
Serialized log unpacked
SleekView parses the wpci_run_log option into a flat table: filename, counts, uploader, and timestamp as first-class columns instead of PHP-serialized strings.
Per-post provenance
Join _wpci_source_run back to wp_posts so every imported page carries the run ID and source file that produced it. Demo cleanup becomes a single filter.
Safe demo removal
Filter to posts whose _wpci_source_file matches a known demo bundle. Review, then bulk-trash in one step without scanning post titles.
Audience
Who uses SleekView for WP Content Importer
Theme builders
Validate that the demo content bundle created the expected post counts on every customer install, filterable by run timestamp and source file.
Site builders
Remove a starter-content bundle before launch by filtering on _wpci_source_run. No more title-by-title hunting on go-live day.
Data quality
Spot imports that overwrote existing content unexpectedly by comparing updated counts against created counts in the run log.
The bigger picture
Why content imports need provenance
Content imports look harmless until launch day. A site builder runs a starter-content bundle while building, the client adds genuine pages on top, and at go-live no one is sure which posts are demo and which are real. The default plugin admin treats each run as a one-shot event without a stable mapping back to the posts it created.
The data exists already: every imported post carries _wpci_source_run in wp_postmeta, every historical run lives in the wpci_run_log option. Reading both together turns the launch-day question "is this real content" into a one-filter operation. Theme authors gain a way to validate that every customer install created the expected post counts.
Site builders gain a way to wipe starter content safely. Data quality teams gain a way to spot the overwrite that no one noticed when an updated content pack landed. The plugin keeps owning import logic.
SleekView owns the audit and cleanup layer the plugin's UI never exposed.
Questions
Common questions about SleekView for WP Content Importer
SleekView deserializes wpci_run_log server-side and projects each historical run as a row. The view re-reads the option on each page load so new runs appear without manual refresh of the schema.
Yes, where the plugin exposes a run-by-id endpoint. SleekView triggers that endpoint on a row action so the same import pipeline runs again with the original file path. The action is capability-gated.
Yes. WXR runs and JSON content-pack runs both write to the same wpci_run_log option. SleekView surfaces a file_type column derived from the extension so each format is filterable.
Yes. Each imported post carries _wpci_source_run in wp_postmeta. Filter that column on the WP Content Importer workspace to map a single post back to its source run and file.
Yes. Per-site option logs live under wpci_run_log in each blog's options table (e.g. wp_2_options). Point SleekView at the relevant prefix and the same view configuration applies.
Yes. Views are capability-gated. Theme builders see customer-install runs; site builders see only their own. Each role saves filtered presets.
Filter wp_posts joined on _wpci_source_run to the run ID of the bad import. Review the affected posts, then bulk-trash them in one operation. The provenance stamp guarantees no manual content is caught up.
Yes. The file_path entry inside each run log row is surfaced as a column so the original upload location stays auditable, even after the upload has been moved out of wp-content/uploads.
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 checkoutBrowse more
- Woocommerce Mix And Match
- Yith Woocommerce Quick View
- Wpc Buy Now Button
- Edd Amazon S3
- Woocommerce Customer Order Csv Export
- Woocommerce Google Product Feed
- Woocommerce Pre Order Pro
- Woocommerce Quaderno
- Woocommerce Shipping Ups
- Paypal Payments
- Woocommerce Dhl Express
- Woo Direct Checkout
- Ti Woocommerce Wishlist
- Woocommerce Sage Accounting
- Woocommerce Color Swatches
- Ultimatemember Social
- Woocommerce Memberships
- Armember
- Paid Member Subscriptions
- Wp Community
- Userpro Pro
- Ultimate Membership Pro
- Premium Content Block
- Wpadverts
- Content Restriction By Userrole
- Simple Membership
- Paid Memberships Pro Addons
- Magic Members Pro
- Memberium Infusionsoft
- Ultimatemember Real Time Notifications