PHP Version Support & Upgrades

Overview #

PHP powers WordPress, and every PHP version has a supported lifespan. When a version reaches End-of-Life (EOL), it stops receiving security patches, a known and exploitable attack surface. This article covers the alerts you may see, what Xponent supports, and how upgrades happen.

The Alerts #

Why It Matters #

• Security: EOL PHP accumulates unpatched vulnerabilities; attackers target old runtimes first
• Compatibility: current plugins (including the Xponent Stack) drop support for old PHP versions
• Performance: newer PHP releases are measurably faster (PHP 8.x is significantly quicker than 7.x)

How Upgrades Happen #

1. We plan it: PHP version changes are applied via the GridPane control panel, never by editing files.
2. We test first: your site is verified on the target PHP version before the switch (plugins, theme, forms, admin).
3. We coordinate: upgrades happen in a low-traffic window; a backup is taken before the change so we can roll back instantly.
4. We verify after: the site is checked post-upgrade and monitored for regressions.

What You Should Do #

Nothing: upgrades are our job. If you see either alert, contact support to schedule the change. Do not change PHP versions yourself in any hosting panel (an uncoordinated change can take the site down).

If you’re planning a migration to Xponent, tell us: the PHP upgrade is included in the migration rather than done twice.

The Xponent Standard #

Xponent-managed sites run PHP 8.3+ as the minimum baseline for the stack, and we target 8.4 as the current standard for new builds and migrations. If your site is below this, it’s flagged for upgrade.

Related Articles #

• Resolving max_input_vars Truncation
• Migrating Your Site to Xponent
• How Xponent Keeps Your Site Updated