WordPress update log: see exactly which update broke your site

Published Updated 4 min read

WordPress 7.1 shipped on 19 August 2026. Within hours, sites running WP Rocket began returning a white screen or the generic critical error page, with the front end, wp-admin, the REST API and WP-CLI all down at once. The cause was a type error in WP Rocket's Cloudflare integration, and the fix, version 3.23.2.2, arrived the following day.

For the people whose sites went dark, the fix was not the hard part. The hard part was the half hour before it, spent working out what had changed. WordPress keeps no update log. Nothing in wp-admin tells you core updated at 01:52 and which plugins auto-updated alongside it, so the first question after any outage gets answered by guesswork.

What follows is what actually broke, what the incident says about leaning on a large plugin, and a small plugin that keeps the record WordPress does not.

What actually broke

WordPress 7.1 changed how it builds the identifier for a hook callback, moving from spl_object_hash(), which returns a long hexadecimal string, to spl_object_id(), which returns a small number. PHP stores a numeric string array key as an integer, so any code that walked the callback list assuming every key was a string started receiving integers instead.

WP Rocket's Cloudflare module did exactly that, calling substr() on each key. The file declares strict_types=1, so PHP raised a TypeError rather than quietly casting the number to a string. The error surfaced in inc/ThirdParty/Plugins/CDN/Cloudflare.php, on a path that runs on every request, which is why entire sites went down instead of one page.

Version 3.23.2.1 and earlier are affected; 3.23.2.2, released on 20 August 2026, fixes it. If a site is still down and wp-admin is unreachable, rename the wp-content/plugins/wp-rocket folder over SFTP, or run wp plugin deactivate wp-rocket, then update and switch it back on.

Six weeks of warning in a public bug report

The bug was filed on WP Rocket's GitHub on 6 July, during the WordPress 7.1 beta, six weeks before release, and the report included the one-line fix. It sat there until production sites started failing, and the release that went out on 20 August was that same one-line change.

That is the complaint doing the rounds: not that a plugin had a bug, which happens to every plugin eventually, but that the beta period did its job. The break was caught, written up and solved by somebody outside the company, in public, with six weeks to spare. WordPress runs a months-long public beta precisely so this class of failure never reaches a live site.

Keep it in proportion. WP Rocket shipped a fix inside a day of the first production report, which is faster than plenty of vendors manage, and the change in core was a legitimate improvement that any plugin reading hook internals was exposed to.

The blast radius of a dependency is its whole surface

The file that crashed is a Cloudflare integration: a module for a service that plenty of WP Rocket users have never switched on. When you install a large plugin you take on all of its code, not the slice you use, and a caching plugin runs on every single request.

Then there is the waiting. When something you did not write breaks, you can disable it and lose the feature, patch it and watch the patch get overwritten by the next update, or wait for the vendor. Here the wait was one day. It is not always one day, and you do not get to choose.

None of this argues against WP Rocket. Page caching, critical CSS and file optimisation are genuinely difficult, and rolling your own is a worse idea than installing a good one. It argues for two smaller things: knowing what is actually running on your site, and being able to say what changed without guessing.

A snapshot of every version, and a row for every change

The plugin adds Tools > Update Log, backed by its own table. It keeps a snapshot of the installed versions of core, every plugin and every theme, compares the live versions against it, and writes a row for each difference: installs, updates, removals, activations and deactivations, with the version before and after.

It checks on the updater hook and again, throttled, on admin page loads, so a change made over SFTP or WP-CLI still produces a row on the next admin visit; the timestamp is when the change was noticed, not when it happened. Rows are attributed to the logged-in user where there was one, and background and cron updates are marked automatic. It records auto-updates; it does not control them.

You can filter by type and date range and export the filtered view to CSV. The table grows with how often you update, not with traffic, and a daily cron prunes anything older than a year by default.

When you should just install Simple History

If what you want is an activity log, install Simple History. It is free, it records updates alongside logins, post edits and option changes, and it has been maintained for years by people who do this properly. For most sites that is the better choice.

The case for building your own is narrow. You want update history and nothing else, on a client site where adding a broad logging plugin is a conversation rather than a click. Or you want the screen shaped to how you work, with your columns and your retention. Small single-purpose plugins like that are the ones worth owning outright rather than renting, and the size a WordPress plugin generator writes in one pass.

One limit to know before you build it: it does not help during an outage. A fatal error that stops WordPress loading stops this plugin too, and nothing gets written. Recover first, by deactivating the suspect plugin over SFTP or WP-CLI, then read the log for what changed in the hours before.

What you get

Included

  • A Tools > Update Log screen listing every core, plugin and theme version change, newest first
  • The version before and the version after on each row, with the date and time in the site's timezone
  • Installs, updates, removals, activations and deactivations, including changes made over SFTP or WP-CLI
  • Attribution to the logged-in user where there was one, and an automatic marker for background updates
  • Filtering by type and date range, plus CSV export of the filtered view

Not included

  • Rolling back an update: this records what changed, it does not restore anything
  • Anything at all during an outage, because a fatal error stops this plugin loading too
  • File integrity checking inside a plugin, which is a different job and a bigger one
  • Logins, post edits, option changes and the rest of what an activity log covers
  • Alerting: there is no email or Slack message when something updates

Simple History does the things on the right. This build covers the part most sites use.

Build it in Steem

The button opens the builder with this guide's prompt filled in, so you can change anything before it runs. Nothing is built, and nothing is charged, until you send it.

Build this pluginAbout 55 credits. The free plan includes enough for one.
Read the prompt (203 words)

Build a WordPress plugin that logs every version change to WordPress core, plugins and themes. On activation, create a custom database table with columns for timestamp, type (core, plugin or theme), item name, item slug or file path, old version, new version, action (installed, updated, removed, activated or deactivated), and the user ID that triggered it. Store a snapshot of the current versions of core, all installed plugins and all installed themes in a single option. Compare the live versions against that snapshot on the upgrader_process_complete hook, and again on admin_init throttled to once every fifteen minutes with a transient, so changes made over SFTP or WP-CLI are caught too. Write a row for every difference found, then update the snapshot. Add an admin page under Tools > Update Log that lists the rows newest first, with columns for date and time in the site timezone, type, name, from version, to version, action, and who triggered it, showing rows with no logged-in user as Automatic. Add a dropdown to filter by type and two date fields to filter by range, and an Export CSV button that exports the currently filtered rows. Add a daily cron event that deletes rows older than 365 days.