Directly from the WPIDE option rows in wp_options, the backup index keys it maintains, and per-user recent-files entries in wp_usermeta. No shadow copy, no separate export. The chart cards run live queries against the same data the editor writes on every save.

Yes. The free editor writes the same option and user-meta entries that any paid tier uses for activity tracking. Every field WPIDE persists is available as a chart group-by or aggregation candidate, so the dashboard works the same on any installation of the plugin.

Yes. A stacked Bar card grouped by directory with user as a secondary series surfaces both pivots at once. Or build two cards side by side, one ranked by user and one ranked by directory, sharing the same view-level date filter for consistent context.

Yes. SleekView only queries the columns and rows the active cards need, so a multi-thousand-entry WPIDE log produces a lean grouped count rather than a full scan. Heavy aggregations are pushed to the database engine and cached at the view level for repeat loads.

Cards reflect whatever is currently in the option rows, so a trimmed log produces a shorter time series rather than missing data. To preserve longer history, snapshot the relevant wp_options rows to a separate table on a schedule and point a second SleekView source at that copy.

Yes. View-level filters for directory prefix, file extension, user, or date range apply to every chart card on the dashboard. One saved configuration drives both the editing table and the reporting view, so investigation and summary stay aligned across the audit.

Charts are read-only summaries by design. To act on an insight, switch to the SleekView table filtered to the same slice (for example, recent edits in wp-content/themes) and open the file in WPIDE from there. Rollback stays inside the plugin's backup browser.

No. The in-browser editor, the search across files, and the backup browser stay exactly where the plugin puts them. SleekView Charts adds a reporting surface on top of the activity log the plugin already writes, so editing remains a single-screen task and the dashboard owns the summarisation.