Blog with latest news and updates
-
Simple History 5.24.0 brings user card popovers, a redesigned dashboard widget, detailed menu change logging, copy-as-image sharing, and a new Site Health Logger. This is one of the bigger releases in a while — focused on making the activity log faster to scan and faster to load, and more detailed where it matters. User card
-
Simple History shows a quick-view dropdown in the WordPress admin bar, letting logged-in users see recent activity without leaving the page. Since the admin bar loads on every frontend page, keeping this bundle small matters. We discovered that a single import — import { HStack } from ‘@wordpress/components’ — was pulling in wp-components (787 KB)
-
This is the first plugin release we seen being forcibly updated by WordPress, since we released our update of Simple History that included Detection of forced plugin updates. This time it was WooCommerce that was auto-updated from 10.5.2 to 10.5.3 on one of our websites. And it was a security update that was forced to
-
We recently gave Claude Code their own account on this website. Giving an LLM access to your website can sure be scary. But also… very useful! While we do like to create our blog posts manually there are many things that an LLM can do more efficiently than a human. In our case we let
-
Simple History 5.23.1 is a bug fix release that addresses crashes that could occur during plugin updates. When updating from versions 5.21–5.23, some users experienced a fatal “Class not found” error. This happened because some PHP classes were moved between versions, and the old class names were still referenced during the update process. This release
-
We are happy to be able to introduce Alerts in Simple History. Alerts are real-time notifications that tell you when something important happens on your WordPress site, delivered straight to Email, Slack, Discord, or Telegram. Alerts: Know What Happened Before It Becomes a Problem With alerts there is no need to constantly check the log
-
Simple History 5.23.0 brings better visibility into WordPress security updates, more granular failed login tracking, Notes statistics, and a batch of performance improvements that make the plugin faster on large sites. Detection of forced plugin updates WordPress sometimes pushes forced security updates for plugins — patches so critical they’re applied automatically, whether you opted in
-
Here is a little sneak peek of a new premium feature that we are working on: Alerts! The alerts feature will let you forward events to popular destinations like Email, Telegram, Slack and Discord. So first, what do we mean by “Alerts”? In Simple History alerts are selective, rule-based notifications that are triggered when specific
-
A week ago, on a local test website on mine, WooCommerce suddenly got updated. Now this was a bit strange since I do not have auto-update enabled for WooCommerce and I did not perform an update. This is how it looked in the Simple History log. Just like a regular plugin update. I had not
-
Did you know that according to the WordPress.org plugin guidelines, a plugin is not allowed to track a user without their consent. That’s a good rule that sometimes plugin authors break. Sometimes by accident, sometimes deliberately. So you can understand that this debug message in Simple History with the Debug & Monitor add-on installed caught
