SleekView for Simple History: events & contexts as tables
Simple History stores every event in its own simple_history and simple_history_contexts tables. SleekView turns those tables into a flexible audit grid.
♾️ Lifetime License available
Simple History, with real filters
wp_simple_history with rich context in wp_simple_history_contexts. SleekView pulls them together so the data is finally queryable.
Sample columns
A typical Simple History audit view
wp_simple_history, wp_simple_history_contexts
| When | User | Logger | Level | Message | IP |
|---|---|---|---|---|---|
| Today 11:02 | ada | SimplePostLogger | Info | Updated post Spring Sale | 203.0.113.10 |
| Today 11:14 | ben | SimplePluginLogger | Notice | Activated plugin Yoast SEO | 203.0.113.11 |
| Today 11:30 | — | SimpleUserLogger | Warning | Failed login attempt | 198.51.100.22 |
| Today 11:45 | carol | SimpleOptionsLogger | Notice | Changed permalink structure | 203.0.113.12 |
Comparison
Default Simple History admin vs SleekView
Default Simple History admin
- Simple History's UI is friendly but its filters are fixed to user, logger, and date.
-
The rich context stored in
wp_simple_history_contextsis invisible without code. - Cross-logger views, like all changes by a single user, take repeated searches.
- There is no inline tagging or annotation of events.
- Exports go through dedicated add-ons rather than the default UI.
SleekView
- Joins events with every context key for fully filterable audit rows.
- Inline tag, archive, or comment on events without leaving the grid.
- Filter by logger, level, user, IP, or context value and save reusable views.
- Bulk acknowledge events for incident reviews and clear the queue.
-
Export the visible columns as
CSVfor compliance and reporting.
Features
What SleekView gives you for Simple History
Events and contexts
Combines the events table with its contexts so every audit field is on a single row.
Saved audit views
Pin views like plugin changes, option changes, or failed logins for fast review.
Inline notes
Annotate an event with an internal note that stays attached to the audit row.
Audience
Who uses SleekView for Simple History
Site security leads
Investigate failed logins, role changes, and option edits from one editable list.
Agencies
Hand clients a clear audit grid that filters down to anything their compliance team asks for.
Support teams
Quickly find the change that broke a site by filtering across loggers and contexts.
Questions
Common questions about SleekView for Simple History
Yes. It queries wp_simple_history and joins context keys from wp_simple_history_contexts.
Any context key written by a logger can be promoted to a column and used as a filter or sort.
Custom loggers and their context keys are picked up automatically because SleekView reads the same tables.
Yes. Filtered rows export as CSV with only the columns currently on screen.
SleekView paginates server-side and uses indexes already present, so the grid stays fast even on years of history.
Yes. Capability checks follow Simple History so only authorised users see sensitive events.
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.
...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