Simple History now comes with support for the Duplicate Post plugin.
When a user clones a post or a page you will se this in the history log, with links to both the original post and the new copy. It works for both build in pages and post, and with custom post types.
With over 600.000 active installs the Redirection plugin is a pretty popular WordPress plugin. So when there was a request for supporting it I agreed it would be a good idea to add support for it.
So in the latest version of Simple History there is now support for the plugin Redirection. The following things are logged:
Here’s a screenshot of how it looks in action:
With the latest update of Simple History the log will show the available updates to plugins, themes and WordPress core that are found.
This is a great feature to have if you for example subscribe to the history RSS feed. You no longer need to manually check the updates-page to see if there are any updates.
Here you can see how it looks when an update to WordPress is found and then the update is installed. It’s all there in the history log:
And here’s how it can look in your RSS-reader when you get notified that WordPress has auto-updated:
Before this version (2.7) of Simple History you could see in the log that a user had been created or changed. But you could not see any details.
With this update however, you can now see a lot of details when a user is created or edited: their username, name, email, webpage, and so on. And when a user is edited you can see from what old value to what new value.
There is now a new plugin that extends Simple History with new features and loggers.
It’s called Developer Loggers for Simple History.
At the moment the developer plugin adds:
Now this plugin has 100 5-star reviews.
In the support forum for Simple History some people have raised issues about the Simple History database tables are growing large. (For example this thread and this thread.
The reason for this is that Simple History is really good at logging things. So if your WordPress blog is getting a really big amount of brute force attacks, all those failed login attempts will be logged in Simple History. Nothing wrong with that, that’s the purpose of the plugin. But the number of rows can be huge – like over a million for some sites. And that can be an issue for some low cost hosts where you have a limited amount of storage/disk space.
Here’s what Simple History is doing to keep the database small – and a solution to keep the number of login attempts down to a minimum:
With version 2.5 or Simple History the creation, modification, and deletion of taxonomies are now logged. This includes terms, categories and post tags.
For a long time the stats-section of this plugins page over at wordpress.org have felt like it was “stuck”. Always showing “20.000 active installs”…
Today however, it did finally update – to 30.000 active installs!
Version 2.4 of Simple History brings a wanted addition to the event log: when hovering the time of an event the tooltip now displays both the local time and the GMT time of the event. This change makes it easier for admins in different timezones that work together on a site to understand when each event happened.
The update also brings two new logged things: