PHP Compatibility Index

Your host is upgrading PHP. Autopilot fixes what would break.

PHP 8.2 stops getting security fixes on 31 December 2026. When your host moves you to PHP 8.3, 8.4 or 8.5, old plugin code stops working and the site shows a fatal error. Autopilot finds that code and rewrites it — before the upgrade.

How it works

  1. Scan for free with PHP Upgrade Check: every plugin and theme, the exact file and line.
  2. Fix automatically: Autopilot first copies the whole plugin to a backup, then rewrites only what newer PHP removed or deprecated. Every change still works on older PHP too.
  3. Site check: it loads your home page and your Plugins screen. If either shows an error, the original files go back on their own.
  4. Undo with one click, any time.

What it fixes today

$string{0} offsets · PHP 4 constructors · create_function() · nested ternaries · get_magic_quotes_*() · mktime() without arguments · removed filter flags · implicitly nullable parameters (PHP 8.4) · curl_close(), imagedestroy() and other no-op close calls (PHP 8.5) · long cast names (PHP 8.5) · E_STRICT (PHP 8.4) · methods that old code calls statically.

For code that can't be rewritten safely, optional compatibility shims put back each(), ereg(), split(), the common mysql_* functions (through WordPress' own database layer) and mcrypt with Rijndael-128 (AES), byte-compatible so old encrypted data still decrypts.

Not fixed automatically: other mcrypt ciphers (Rijndael-256, Blowfish) and method signatures that no longer match WordPress core. The free report explains those.

Tested on real plugins

Static analysis finds most problems, not all. Always test on a staging copy before upgrading a live site.

1 site

$49per year

5 sites

$99per year

Agency

$199per year, unlimited sites

Autopilot is in final testing. Scanning with PHP Upgrade Check is free and always will be.