Hosts are moving sites off old PHP versions: PHP 8.1 gets no security fixes since the end of 2025, PHP 8.2 loses them at the end of 2026. For a WooCommerce shop the question is always the same \u2014 will the checkout still work after the switch?<\/p>\n\n
PHP Upgrade Check reads the code of your plugins and themes and compares it with what changed in PHP from version 7.0 to 8.5. It runs on the PHP you have today (7.2 or newer) and tells you, before anything is switched, which plugins will stop working on the version you are moving to.<\/p>\n\n
The report<\/strong><\/p>\n\n What it finds<\/strong><\/p>\n\n Code that already copes with both versions \u2014 inside a check of the PHP version, Your server<\/strong><\/p>\n\n How it works<\/strong><\/p>\n\n The plugin reads the PHP files with PHP's own tokenizer. Nothing is executed, included or changed, and no code leaves your server. The scan runs in short steps, so a shop with WooCommerce and dozens of plugins does not hit the server's time limit; you can leave the page and continue later.<\/p>\n\n A scan of the code cannot see everything that happens while the site runs \u2014 for example a When \"Latest PHP releases\" is on (the default), the plugin asks php.net which release is the latest in each PHP branch and until when each branch gets security fixes, so it can tell you whether your PHP is up to date.<\/p>\n\n Switch it off under Tools \u2192 PHP Upgrade Check \u2192 Settings; the plugin then uses the list of releases built into it.<\/p>\n\n\n No. It only reads files. It does not switch PHP, does not edit plugins and does not execute their code.<\/p><\/dd>\n Yes. Since 1.0.1 WooCommerce is a required plugin: WordPress activates PHP Upgrade Check only while WooCommerce is installed and active. The report marks the WooCommerce extensions and shows the PHP version WooCommerce needs.<\/p><\/dd>\n Yes \u2014 that is what it is for. The scan runs on the PHP you have and reports for the version you choose.<\/p><\/dd>\n No tool can promise that by reading code. \"Ready\" means nothing was found that the chosen PHP version breaks. Test the shop after the switch \u2014 the checkout above all \u2014 and keep a backup you can restore.<\/p><\/dd>\n WordPress publishes which PHP versions each release supports; the plugin shows that next to your WordPress version.<\/p><\/dd>\n Encoded files cannot be read. They run only on the PHP versions their encoder and the loader on the server support, so the report tells you to ask the vendor before the switch.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
wp catcode-php-check scan<\/code>, wp catcode-php-check report --target=8.4<\/code>, wp catcode-php-check export report.csv<\/code>.<\/li>\n<\/ul>\n\n\n
$text{0}<\/code>), nested ternaries without parentheses, the (real)<\/code> and (unset)<\/code> casts, =& new<\/code>, classes named after new reserved words (mixed<\/code>, never<\/code>, readonly<\/code>, match<\/code>), a function called match()<\/code> or __autoload()<\/code>.<\/li>\neach()<\/code>, create_function()<\/code>, get_magic_quotes_gpc()<\/code>, money_format()<\/code>, split()<\/code>, the ereg<\/code> family and many more.<\/li>\nmysql_*<\/code> (PHP 7.0), mcrypt_*<\/code> (7.2), xmlrpc_*<\/code> (8.0), imap_*<\/code>, pspell_*<\/code> and oci_*<\/code> (8.4).<\/li>\nimplode()<\/code> with the array first, parse_str()<\/code> without a result, mktime()<\/code> without arguments), and code that silently does something else: old-style constructors that no longer run, is_resource()<\/code> on handles that became objects, define()<\/code> with case-insensitive constants, assert()<\/code> with code in a string, preg_replace()<\/code> with \/e<\/code>.<\/li>\nCountable<\/code>, ArrayAccess<\/code>, Iterator<\/code>, JsonSerializable<\/code> and other PHP interfaces (8.1), utf8_encode()<\/code> (8.2), strftime()<\/code> (8.1), FILTER_SANITIZE_STRING<\/code> (8.1), E_STRICT<\/code> (8.4), CSV functions without the escape argument (8.4), curl_close()<\/code> and imagedestroy()<\/code> (8.5), the backtick operator and non-canonical casts (8.5) and others.<\/li>\nfunction_exists()<\/code>, extension_loaded()<\/code> or defined()<\/code>, or a plugin that ships its own replacement of a removed function \u2014 is shown as \"guarded\" and does not count against the plugin.<\/p>\n\n\n
null<\/code> passed to a PHP function or a property created on the fly. Such cases appear as deprecation notices in the PHP error log after the switch.<\/p>\n\nExternal services<\/h3>\n\n
\n
\n
\n
Does it change anything on my site?<\/h3><\/dt>\n
Does it need WooCommerce?<\/h3><\/dt>\n
My site is on PHP 7.2 \/ 7.4. Can I check it for PHP 8.3?<\/h3><\/dt>\n
Is a plugin marked \"Ready\" guaranteed to work?<\/h3><\/dt>\n
Why is WordPress itself not in the list?<\/h3><\/dt>\n
What about encoded (ionCube) plugins?<\/h3><\/dt>\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n