One Click Demo Import is one of the few demo-import plugins that already keeps a real log: each run writes a timestamped file to wp-content/uploads/ocdi-logs/ containing the pack identifier, started/finished timestamps, and any warnings the importer raised. The inserted content goes into wp_posts, wp_postmeta, wp_terms, and wp_term_relationships through the standard WP importer pipeline.

The default UI surfaces the logs as a folder listing on the OCDI settings page, with a download link per file. Reading them means opening each file individually, which works for one site but breaks down across an agency managing dozens.

SleekView parses the ocdi-logs directory as a flat workspace. Each log file becomes a row with pack name, started timestamp, duration, warning count, and outcome. A second view joins wp_posts by post-date window so the inserted demo content is filterable alongside the run that created it. Agency staff stop opening individual log files and start reading the demo history as a table.

OCDI is one of the few demo-import plugins that gets logging right at the file level: every run leaves a timestamped artefact with pack, duration, and warnings. The plugin's UI does not exploit that data. Logs surface as a folder listing with a download link, which is fine for one site and impossible to reason about across an agency.

Reading the ocdi-logs directory as a workspace turns a pile of files into a queryable history. Pack regressions surface as sortable duration outliers. Warning patterns across a customer's projects become a chip filter rather than an afternoon of opening files.

Failed runs cluster by error message because the message is a column. Joining wp_posts by post-date window adds content provenance, so editors can confirm which run inserted a placeholder testimonial that survived launch. That is the difference between a log file the plugin keeps and a logbook the team actually reads.