WordPress 5.8

WordPress 5.8 expanded the block editor beyond post and page content. It introduced the first phase of Full Site Editing for compatible block themes, including a template editor, reusable template parts, global styles controls, and the Query Loop block. It also brought block-based widgets to the Widgets screen and Customizer, added support for WebP image uploads, added duotone effects for images and cover blocks, and removed Internet Explorer 11 support from the administration experience. These changes made theme and widget behavior more dependent on block-editor assets, theme configuration, and JavaScript than in earlier WordPress versions.

WordPress 5.8 has reached end of life, so this branch no longer receives its own maintenance or security fixes. A site that remains on it can retain known WordPress-core vulnerabilities and will increasingly encounter plugins, themes, PHP versions, browsers, and hosting environments that no longer test against or support it. The main migration risk is accumulated compatibility change: older themes may rely on legacy widget behavior, custom editor integrations may assume older block-editor APIs, and plugins may have changed database, PHP, or front-end requirements since 5.8. 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.

Plan an upgrade to a currently supported WordPress release rather than treating 5.8 as a long-term baseline. First inventory the active theme, child theme, plugins, must-use plugins, custom code, integrations, scheduled tasks, and the PHP and database versions supplied by the host. Clone the site to a staging environment, take tested backups of files and the database, then update WordPress, plugins, themes, and PHP in a controlled sequence compatible with the target environment. Test login and role workflows, the block editor, templates and widgets, media uploads, forms, caching, search, outbound integrations, cron jobs, and error logs. For WooCommerce sites, also test product data, checkout, payment and shipping integrations, taxes, transactional email, webhooks, subscriptions or other extensions, and order processing before deploying. Resolve deprecated-code notices and replace abandoned extensions, then monitor logs, performance, and business-critical transactions after production rollout.