Pomnex Update Check

Updates are the most common reason WordPress sites break. The worst breakages are the silent ones. The site still loads, but the checkout button is gone or the contact form stopped rendering, and you only find out when a customer tells you.

Pomnex Update Check watches the pages that matter to you. Pick up to 5 pages (checkout, contact, login) and tell it what must appear on each one, like “Place order”. After every core, plugin or theme update, manual or automatic, it checks that:

• the page loads without errors
• the important element is still there
• no broken shortcodes or PHP warnings are showing to visitors
• stylesheets and scripts still load
• the page hasn’t become much slower

If something fails, you get an email naming the page, what changed, and which update came right before it.

Update log. Every update is recorded: what changed, from which version to which, who ran it, when, and what the check found.

Private by design. Everything runs on your own site. No account, no external service, no data sent anywhere, including to us.

What it does not do. It doesn’t fix problems, roll back updates or take backups. It doesn’t take screenshots, so it won’t catch small visual changes. It doesn’t click buttons or test that orders and emails go through.

Built by Pomnex, a WordPress maintenance and custom plugin development team. Source code: https://github.com/Pomnex/pomnex-update-check

How the check works

1. For each important page, the plugin keeps a baseline: the last state in which the page worked (HTTP status, size, response time, whether the marker was found, the site’s own stylesheets and scripts, and the shortcodes registered at the time).
2. When an update finishes, it records what changed and schedules a check about a minute later, when the update is done and the site is out of maintenance mode.
3. The check loads each page from the site itself, as a logged-out visitor, and compares it with the baseline.
4. The result is Pass, Warning, Fail or Could not check. On Fail you get an email. Everything is recorded in the update log.

WordPress (6.6 and later) rolls back a plugin auto-update only when it causes a PHP fatal error on the home page. Update Check also looks at your other important pages, manual updates, theme and core updates, and problems that are not fatal errors.

License

GPLv3 or later, with one additional term under GPLv3 section 7(b): the original author attribution (“Developed by Pomnex”) must be preserved in the source code headers and on the plugin’s About screen. See the LICENSE file.