WordPress 5.2

WordPress 5.2 added Site Health, which reports configuration and maintenance issues such as outdated PHP, missing recommended PHP extensions, HTTPS status, scheduled-event problems, and inactive plugins or themes. It also introduced PHP fatal-error protection: when a plugin or theme causes a fatal error, WordPress can send a recovery link that lets an administrator enter Recovery Mode and disable or repair the failing component. The block editor included updated Gutenberg functionality, and WordPress 5.2 raised the minimum supported PHP requirement to PHP 5.6.20. WooCommerce is a plugin that runs on WordPress, so a WooCommerce store is a WordPress site and its WordPress version matters to it just as much as its WooCommerce version does.

WordPress 5.2 has reached end of life. Remaining on it means core vulnerabilities and compatibility defects found after its support window are not corrected in that branch. Its PHP baseline is itself obsolete, which can leave a site dependent on unsupported server runtimes or make a later PHP upgrade break older themes, plugins, and custom code. The age of the bundled block editor and WordPress APIs also increases the chance that current plugins, themes, WooCommerce extensions, payment integrations, and hosting tooling will not support the installation. Recovery Mode can help regain access after a fatal error, but it is not a substitute for maintained core or compatible dependencies.

Inventory the WordPress core version, active and inactive plugins, theme and child theme, WooCommerce and extensions, PHP version, custom code, scheduled tasks, and external integrations. Take a tested backup of both files and database, then clone the site to a staging environment that matches production. Update WordPress through supported intermediate steps if required by the site’s plugin and PHP constraints, then move to a currently supported WordPress release and a PHP version supported by that release. Update or replace abandoned plugins and themes, and test login, publishing, media uploads, forms, caching, email, search, scheduled jobs, API integrations, and error logs. For WooCommerce sites, additionally test the customer journey, cart, checkout, payment and shipping callbacks, tax calculations, order emails, stock handling, refunds, and admin order workflows. Deploy with a rollback plan, monitor logs and transactions after release, and keep core, PHP, plugins, and themes on maintained versions thereafter.