Free pilot

Why WordPress Sites Get Stuck on Legacy PHP

By Ryan7 min read

Why WordPress Sites Get Stuck on Legacy PHP
On this page
  1. 1. Functions that no longer exist
  2. 2. PHP 8 stopped tolerating sloppy code
  3. 3. Abandoned themes and plugins
  4. 4. Expired and nulled licenses
  5. 5. WordPress core itself is too old
  6. 6. Custom code nobody remembers
  7. 7. Business logic locked inside a dead plugin
  8. 8. Server-level dependencies
  9. 9. Nobody owns the upgrade
  10. What it takes to actually move them

Most hosts can switch a site’s PHP version with one click. That was never the hard part. The hard part is what happens to the site after the click.

A WordPress site isn’t one piece of software. It’s WordPress core, a theme, a stack of plugins and often some custom code, each written by different developers at different times against whatever PHP version was current then. When the runtime underneath changes, every one of those pieces has to keep working. If one doesn’t, the site shows a white screen, a fatal error, or a checkout that silently stops.

That’s why so many sites sit on PHP 5.6 or 7.4 for years. Not because nobody noticed, but because every attempt to move them broke something. Here are the core reasons, roughly in order of how often we see them.

1. Functions that no longer exist

Each major PHP release removes things older code depended on. When a site calls a function that no longer exists, PHP doesn’t warn; it stops.

The most common casualties:

  • The original MySQL functions (mysql_query, mysql_connect and the rest) were removed in PHP 7.0. Old themes and plugins that talk to the database directly with them fail instantly.
  • ereg and split, old pattern-matching functions, were removed in PHP 7.0.
  • mcrypt, once common for encryption, was removed from core in PHP 7.2.
  • create_function and each() were removed in PHP 8.0, and both were everywhere in plugins written before 2017.

A site built around any of these can’t simply be switched. The code has to be found and rewritten.

2. PHP 8 stopped tolerating sloppy code

For years, PHP was forgiving. Code that passed the wrong type of value, counted something that wasn’t countable, or did arithmetic on the wrong kind of data got a warning, and the page usually kept loading.

PHP 8.0 turned many of those warnings into fatal errors. Code that ran for a decade without complaint suddenly throws a TypeError and takes the page down with it. PHP 8.1 and 8.2 added more deprecations, including passing null where a string is expected and creating properties on objects on the fly, which are harmless warnings today and errors in a future version.

This is the most frustrating category for site owners, because nothing looks wrong with the code. It worked yesterday. It just relied on behavior PHP no longer allows.

3. Abandoned themes and plugins

The biggest single blocker isn’t PHP itself. It’s code nobody maintains anymore.

A theme bought in 2015 from a marketplace author who has since moved on will never receive a PHP 8 compatibility update. A plugin removed from the directory years ago won’t either. The site owner can’t fix them, the original developer won’t, and the site stays on the last PHP version they worked with.

Premium themes make it worse. Many bundled their own copies of page builders, sliders and form plugins, frozen at the version that shipped with the theme. Those bundled copies can’t be updated separately, and they’re often the first thing to break.

4. Expired and nulled licenses

Premium plugins and themes only update while a license is active. When a license lapses, the site keeps running the old version, and eventually that old version is incompatible with the PHP the host wants to move to.

Nulled copies, pirated versions with licensing removed, are the same problem with no path back. They can’t update at all, and they’re a security risk on their own. A surprising share of legacy sites are held back by nothing more than a license that needs renewing or replacing, which makes this one of the fastest blockers to clear.

5. WordPress core itself is too old

Some sites never updated WordPress core, usually because an earlier update broke something and nobody tried again. Older core versions weren’t built for PHP 8; WordPress added beta support for PHP 8.0 only in version 5.6.

This creates a chain: the site can’t move to current PHP without updating core, it can’t update core without updating the theme and plugins, and it can’t update those without fixing whatever broke last time. Every link has to be worked through in order.

6. Custom code nobody remembers

Many business sites carry custom code: functions added to a theme’s functions.php, a small plugin a freelancer wrote, a parent theme edited directly instead of through a child theme.

That code was written once, for the PHP of its day, and never touched again. It’s rarely documented, and the person who wrote it is usually long gone. Worse, when someone edited a parent theme’s files directly, updating the theme wipes those changes out, so the owner learns not to update anything at all.

7. Business logic locked inside a dead plugin

This is the hardest case. A membership site, a booking system, a directory or a custom e-commerce flow is built on a plugin that holds the site’s core function, and that plugin is abandoned.

It can’t be swapped for an alternative without migrating data and rebuilding workflows. It can’t be left alone, because it breaks on current PHP. It has to be refactored, or the site has to be rebuilt around something maintained. These are the sites that sit on extended support the longest, because every option costs real engineering time.

8. Server-level dependencies

Some sites depend on things outside WordPress entirely. Plugins encoded with ionCube require a loader that matches both the PHP version and the version the file was encoded for; if the vendor is gone, the file can’t be re-encoded or read. Others rely on PHP extensions that newer versions no longer ship.

These can’t be fixed from inside the site. They need to be replaced.

9. Nobody owns the upgrade

Underneath all of the technical reasons is a structural one. The site owner doesn’t know what PHP is, can’t see which version they’re on, and has no way to know whether the switch will break their contact form. The host can flip the version but doesn’t own the site’s code. The original developer is gone.

So the site sits. Not because the problem is unsolvable, but because it belongs to nobody. Extended support keeps it safe while it sits, which is useful, but it doesn’t make anyone responsible for moving it.

What it takes to actually move them

Every blocker above has a known fix. What differs is the effort.

BlockerWhat breaksHow it’s fixedTypical effort
Expired or nulled licensePlugin or theme can’t update to a compatible versionRenew or replace the license, then updateQuick
Outdated utility pluginCaching, SEO, slider or form plugin throws errorsSwap for a maintained alternativeQuick
Deprecation warningsLogs fill with notices; sometimes layout breaksPatch the affected callsQuick
Removed functionsFatal errors on loadRewrite the calls using current equivalentsModerate
Abandoned themeTheme fails on PHP 8Patch through a child theme, preserving the designModerate
Outdated WordPress coreCore can’t run on current PHPUpdate core, then work through theme and plugins in orderModerate
Undocumented custom codeUnknown breakage in functions or custom pluginsAudit, test on staging, rewrite what failsModerate to heavy
Business logic in a dead pluginCore site function stops workingRefactor the plugin or migrate to a maintained oneHeavy
Encoded files or missing extensionsFiles can’t load on the new versionReplace the dependencyHeavy, or rebuild

The pattern that matters: most legacy sites aren’t held back by the hard cases. They’re held back by one or two quick ones that nobody was assigned to fix. The heavy cases are real, but they’re usually a minority of any fleet, and they’re the ones where a rebuild often costs less than a patch.

The way through is the same every time. Audit the site against the target PHP version before touching production. Clone it to staging, switch the version, and see exactly what breaks. Sort the fleet by effort. Fix the quick ones first, patch the moderate ones, and quote the heavy ones as refactors or rebuilds. Then upgrade with rollback standing by.

That’s what PHP Lifecycle in WP Maintain is built to do across a whole fleet: flag every site on an end-of-life version, sort each one by what will break and why, and track every upgrade through to done. And it’s why we include the upgrade itself for hosting partners on WP Maintain+, because the reason sites stay stuck was never the click. It was that nobody was there to fix what the click broke.

See the Legacy PHP Fleet Program or request your fleet audit.

Stop Fighting Fires. Start Preventing Them.

WP Maintain enables proactive monitoring and maintenance that reduces tickets, escalations, and downtime across your hosting platform.

  • Safe updates with instant rollback
  • Fewer WordPress-related tickets
  • White-label Proof-of-Care reports
  • Reduce tech support costs
  • Legacy PHP protection and upgrades
  • Improve customer retention
  • Visual regression testing on staging
  • Higher-tier premium upsells