WordPress Updates vs. PHP Upgrades: Two Jobs, One Platform

Every WordPress fleet needs two kinds of maintenance. They get confused because both involve “updates,” but they are different jobs with different cadences, different risks, and different revenue models for hosts. Conflate them, and you either break sites with careless updates or wake up to mass breakage the day your infrastructure team retires an EOL PHP version.

Job One: Continuous Update Management

WordPress core, plugins, and themes generate a never-ending stream of security and compatibility releases. Applied carelessly, they break sites. Ignored, they become the number one cause of compromised WordPress installations.

This is the job WP Maintain’s platform runs every day across your portfolio. The Plugin and Theme Manager gives your team centralized visibility and bulk actions with guardrails. Core updates are applied through defined policies with compatibility awareness. Every action is staged, tested, scored by the Update Confidence Score, logged, and reversible.

The cadence is continuous. The unit is per site. The value to your customers is that updates simply happen, safely, without tickets. See the full engine at Core, Plugin, Theme Updates.

Job Two: PHP Lifecycle Upgrades

Underneath every WordPress site is PHP, the runtime your servers execute. PHP versions reach end of life on a published schedule. PHP 8.1 stopped receiving security patches at the end of 2025, and PHP 8.2 reaches end of life this December. Every site still on those versions is on a countdown. After that date, no more security patches exist. Sites left behind are running an unpatched engine, and eventually your infrastructure team is forced to retire the old version, breaking every site that wasn’t ready.

This is not a routine update. It is a migration project: audit the site for code that fails on the new version, resolve outdated plugin and theme code, test on staging, then move the site to a fast, supported runtime.

The cadence is periodic, driven by the PHP end-of-life calendar. The unit is a migration. The value to you as a host is fleet-level risk retirement: no EOL runtimes on your infrastructure, no mass breakage on forced-upgrade day, no security exposure sitting on your servers. See the full offering at PHP Lifecycle.

When Does a Fleet Need PHP Upgrades?

Most well-maintained sites don’t need one today. The sites that do are predictable:

• Sites on a PHP version that has reached, or is approaching, end of life
• Sites blocking your infrastructure team from retiring an old PHP version
• Legacy sites that were never migrated because an old plugin or theme breaks on modern PHP
• Sites underperforming on speed, since modern PHP is dramatically faster
• Sites that can’t install current plugins or themes due to minimum PHP requirements

The PHP Version Monitor identifies exactly which sites these are across your portfolio, before your team goes looking. And for sites that cannot migrate yet, PHP Bridge Support keeps them protected, and billing, until they graduate. If you think this doesn’t apply to your fleet, the data says otherwise — a recent industry study found 70% of WordPress is running on a dead engine.

How They Work Together

Monitoring finds the problem. The service fixes it. The platform keeps it fixed.

The PHP Version Monitor flags every site on an outdated or EOL runtime. PHP Upgrades migrate those sites safely, in batches, with staging and rollback. Continuous update management then keeps core, plugins, and themes current so sites never drift back into legacy territory.

Side by side, the two jobs look like this:

One platform sees both layers. One partner handles both jobs.

Explore Core, Plugin, Theme Updates and PHP Lifecycle, or run your fleet’s numbers on the WP Care ROI Calculator.