Simple History 4.16.0 released – improved settings logging, ANSI_QUOTES support, RSS feed filtering, and more

We’re excited to announce the release of Simple History 4.16.0! This update brings a host of new features and improvements designed to enhance your WordPress site monitoring experience.

Since this new version contains so much new, we’ve split it up into multiple headlines:

After updating plugins we find it useful to go to the site history view to get at more detailed look at the changes that was made. This version adds a handy shortcut link, next to the other links at the bottom of the page.

Settings pages logging updates

In this version, we’ve made significant updates to how changes on the WordPress settings pages are logged.

Screenshot: Settings name and setting page name with link and on/off text for changes.

Changes made to the options on any settings screens have undergone a major overhaul, making the logs much more user-friendly and informative.

First, with this version, only built-in WordPress options are logged. Previously, other options could “sneak in” when they were added using a filter or similar methods on the same screen.

When the site language is updated, “en_US” is now shown as the language when the option is empty. Previously, it was set to an empty string, which was a bit confusing.

The “Week Starts On” setting now displays the new and previous weekday as human-readable text (e.g., Monday, Tuesday) instead of just a number.

The plugin now logs changes as “Updated setting…” instead of “Updated option…”. Internally, WordPress stores the settings as options, but “setting” is the word used in the WordPress UI. The settings screens are called settings screens, not options screens.

The name of the settings page is included in the main log message for each setting updated, and the text is a link to the settings page in question.

Most settings now include the setting name in a human-readable format and the changes also as human-readable text. This means that instead of “blog_public” was changed to “0”, the log will now display “Discourage search engines from indexing this site” was changed to “On”. This applies to almost all settings, so instead of “blogname”, you will now see “Site Title”, and instead of “blogdescription”, you will see that “Tagline” was changed. Similarly, “admin_email” means that “Administration Email Address” was changed. The list goes on.

These changes applies to all the settings screens that come with WordPress: General, Writing, Reading, Discussion, Media, Permalinks, and Privacy.

Screenshot: Example of settings changes being displayed with settings name in cleartext and the changed values clearly shown too.

Monitor WordPress Auto Update Adjustments

In the latest release of Simple History, we’ve added a new feature that logs changes to the WordPress auto update settings. Now, whenever an admin user modifies the way WordPress handles core updates, it will be recorded in the activity log. Whether you switch from “automatic updates for all new versions of WordPress” to “automatic updates for maintenance and security releases only,” or vice versa, Simple History will capture this important change. This enhancement ensures you have a clear audit trail of all modifications to your site’s update settings, providing greater transparency and control over your WordPress maintenance processes.

Changes to WordPress core auto update settings are now logged. Whether you switch from “automatic updates for all new versions of WordPress” to “automatic updates for maintenance and security releases only,” or vice versa, Simple History will capture this important change.

This enhancement ensures you have a clear audit trail of all modifications to your site’s update settings, providing greater transparency and control over your WordPress maintenance processes.

When a user changes the setting on the “WordPress updates” screen….
…it will now be shown in the log.

Attachment Updates: Now with Full Change History

Attachment modifications are now tracked in more detail. When changes are made to an attachment’s title, alternative text, caption, description, or slug, Simple History provides a comprehensive log entry that clearly displays what fields were changed and what both their new and old values were.

Screenshot: After modifying an uploaded image the log will show what fields have been updated, i.e. in this case title, caption, description, and slug.

Plugin Update Errors: Now Captured in Your Logs

Plugin updates don’t always go smoothly. Sometimes, the WordPress upgrader encounters obstacles – it might fail to delete old files, struggle to move folders, or face other unexpected issues. Previously, these failed updates could slip under the radar, leaving site administrators unaware of potential problems.

With this latest update to Simple History, we’ve addressed this blind spot:

  • Plugin update failures are now logged
  • Error messages provide insight into what went wrong
  • Administrators can quickly identify and address update issues
Example of WordPress plugin updates that fail.
Failed plugin updated as shown in the history event log.
Details about the reason for the plugin fail is added to the event context.

As a WordPress site owner it’s not uncommon to see many failed login attempts. Sometimes this is a sign that a valid user is having issues logging in, but often it can be brute force attacks from botnets. No matter the reason, it’s not fun to have to log filled with to many entries about the same thing.

This version adds a link next to the number of similar events for these messages:

  • For users who has the extended settings add-on the link goes to the settings page for that plugin, where they can configure the number of login attempts to store.
  • For users who does not have the add-on the link goes to the information page for the extended settings add-on.
Screenshot: For users with the extended settings add-on a link to add-on settings is added.
Screenshot: For users without the extended settings add-on a link to more information about the add-on is added.

Debug Page Boost: SQLite Support and More Insights

The debug page has got a few improvements in this version:

  • SQLite Support: View table size and row count for SQLite databases, matching existing MySQL and MariaDB features
  • Database Engine Detection: Quickly identify your database type (MySQL, MariaDB, or SQLite)
  • Drop-ins Visibility: See a list of all drop-ins active on the site
Database size and number of rows for each table is now shown for users of SQLite.

Changelog summary

  1. More Informative Settings Logging
    • Clearer, more user-friendly messages when settings are updated
    • Human-readable display of options like “Week Starts On” and feed content settings
    • Improved logging of WordPress core auto-update preference changes
  2. Supercharged Debug Page
    • Now displays your database engine (MySQL, MariaDB, or SQLite)
    • Shows table size and row count for SQLite databases
    • Lists Drop-ins for better insight into your WordPress setup
  3. Improved Error Handling and Logging
    • Exceptions are now thrown for log query database errors, making debugging easier
    • Plugin update failures are logged with detailed error messages
    • New support for ANSI_QUOTES mode in MySQL/MariaDB
  4. Enhanced RSS Feed Functionality
    • Filter your RSS feeds by log levels (e.g., warnings, notices) for more targeted monitoring
  5. Additional Context for Plugin and Theme Management
    • Update URI plugin header now included in context for installs and updates
    • Streamlined logging for plugin/theme ZIP installations
  6. Attachment Modifications Tracking
    • Now logs changes to title, alternative text, caption, description, and slug for attachments
  7. User-Friendly Interface Improvements
    • Link to Simple History site added below update completion messages
    • Helpful link for managing failed login attempts, integrated with our Extended Settings add-on

For full changelog and past changelogs please see the plugin development tab at wordpress.org.

These updates are designed to provide you with more detailed, actionable information about your WordPress site’s activities. Whether you’re troubleshooting, monitoring for security, or just keeping tabs on site changes, Simple History 4.16.0 has you covered.

As always, we’ve also included various code improvements and bug fixes to ensure Simple History runs smoothly on your site.