WordPress 5.7

WordPress 5.7 refined the block editor rather than introducing the later full-site-editing features. It added drag-and-drop block placement, a simpler way to change block sizes, improved reusable-block handling, more block variations in the inserter, and a streamlined editor interface. Core also added native lazy loading for iframe content, a Robots API for controlling robots meta directives, improvements intended to help sites move from HTTP to HTTPS, and changes for theme and plugin developers, including new hooks and APIs. It did not include the block-based widget screen, block themes, or the Site Editor that arrived in later WordPress cycles. 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.

This WordPress cycle has reached end of life, so it should not be treated as a maintained platform for production use. Remaining on it increases exposure to vulnerabilities fixed in later core releases and can leave a site dependent on unpatched combinations of core, plugins, themes, PHP, and server libraries. Compatibility becomes a practical operational risk as current plugin and theme releases raise their minimum WordPress or PHP requirements, while older extensions may conflict with newer hosting environments or payment, caching, security, and browser behavior. For WooCommerce stores, that risk includes checkout, account, tax, shipping, payment-gateway, and order-management integrations, because the store relies on WordPress core as well as WooCommerce and its extensions. Delaying the upgrade also tends to make the eventual migration larger: more core changes accumulate, outdated custom code is harder to test, and recovery options are weaker if a failed update or security incident occurs.

Plan an upgrade to a currently maintained WordPress release rather than moving only to the next historical branch. First, inventory the active theme, child theme, custom plugins, must-use plugins, WooCommerce extensions, payment and shipping integrations, PHP version, database version, cron jobs, caches, and external services. Create a complete backup and a production-like staging copy, then update or replace extensions that do not support the target WordPress and PHP versions. Test critical journeys on staging, including login, editing, media uploads, forms, search, redirects, scheduled tasks, API integrations, and, for WooCommerce sites, catalog browsing, cart updates, checkout, payment authorization, transactional email, refunds, stock changes, and webhooks. Review custom code for deprecated WordPress, jQuery, PHP, and WooCommerce behavior, apply updates in a controlled order, and keep a tested rollback path. After deployment, monitor error logs, Site Health, performance, scheduled events, payment callbacks, and conversion-critical flows, then establish a routine for applying future core, plugin, theme, and PHP updates before they become another accumulated migration.