WordPress 5.3

WordPress 5.3 expanded the block editor with new block types and layout controls, including a Group block, improved columns, and more control over image sizing and galleries. It introduced a more robust image-upload pipeline that detects very large images and can generate a scaled copy for use on the site, while preserving the original upload. The release also added a Site Health screen to surface configuration and performance checks, introduced an admin email verification prompt, improved date/time handling, and added support for PHP 7.4. It also changed the default bundled theme to Twenty Twenty and included accessibility, privacy, media, REST API, and developer-facing updates. 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.3 has reached end of life and no longer receives maintenance or security fixes through its own release line. Running it leaves known and newly discovered WordPress core vulnerabilities unpatched, and compatible versions of themes, plugins, PHP, database software, browsers, and hosting tooling become harder to maintain over time. The image-handling, block-editor, and administrative changes in this release may also create upgrade dependencies: a site that has remained on 5.3 can be several major core generations behind, making a direct move more likely to expose deprecated code, editor compatibility issues, old jQuery assumptions, outdated custom themes, and plugins that are no longer maintained. For WooCommerce stores, the exposure includes checkout, account, order-management, and payment integrations, because an unsupported WordPress core can constrain which WooCommerce and payment-plugin versions can be safely used.

Treat the move as a tested upgrade project rather than applying core updates directly to production. Inventory the current WordPress core, PHP version, active and inactive plugins, theme and child-theme code, must-use plugins, custom integrations, scheduled tasks, REST API consumers, payment gateways, caching layers, and hosting requirements. Create a full backup and restore-tested staging copy, then update PHP and WordPress along a compatibility-tested path to a currently supported WordPress release. Update or replace plugins and themes that do not support the target environment, and remediate custom code for deprecated functions, modern PHP compatibility, block-editor behavior, and changed JavaScript dependencies. Test public pages, login and editorial workflows, media uploads and image sizes, forms, search, caching, emails, integrations, backups, and error logs. For a WooCommerce site, additionally test product management, carts, checkout, taxes, shipping, customer accounts, order processing, webhooks, subscriptions if used, and every payment method with the gateway provider’s supported versions. Schedule a rollback plan, deploy during a controlled window, monitor application and payment errors after launch, and keep core, plugins, themes, and the supported PHP runtime on a regular update cadence.