WordPress 6.3

WordPress 6.3 expanded the block-based Site Editor so block-theme users could manage navigation, styles, pages, templates and patterns from a more unified editing experience. It added the Command Palette for keyboard-driven editor actions, introduced improved pattern management including synced patterns, and added or enhanced blocks and editor controls such as footnotes, details, image aspect-ratio settings and better link controls. The release also included performance work, accessibility improvements, developer-facing block and editor API changes, and compatibility updates across core. These changes mainly affected the block editor and block themes; classic-theme sites could use many editor improvements without adopting the Site Editor.

This cycle has reached end of life, so remaining on it leaves the site on a WordPress line for which the vendor has ended support. Newly discovered issues in this line will not receive fixes there, increasing security, reliability and compliance risk over time. Plugin, theme, hosting and PHP-version compatibility also tends to move toward currently supported WordPress releases, making future upgrades more difficult if the site accumulates outdated extensions, customizations or database assumptions. Editor-heavy sites have additional risk because templates, synced patterns, navigation and custom blocks can depend on behaviors that later WordPress releases refine or change. 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; an unsupported WordPress core can therefore affect store administration, checkout-related extensions, payment integrations and operational support even when WooCommerce itself is updated.

Plan an upgrade to a currently supported WordPress release, preferably the current stable release after validating compatibility. First inventory the active theme, child theme, plugins, must-use plugins, custom blocks, custom code, hosting PHP version, caching layers and external integrations. Create a tested backup and a production-like staging environment, then update WordPress, plugins and themes there and resolve compatibility notices before changing production. Test login and roles, the editor, templates, navigation, patterns, media uploads, forms, search, scheduled tasks, caching and any custom API integrations. For WooCommerce sites, additionally test product management, cart, checkout, taxes, shipping, payment gateways, transactional email, webhooks, subscriptions or bookings, and order administration with representative data. Review custom code for deprecated WordPress, PHP and block-editor APIs, replace abandoned extensions, document a rollback procedure, and monitor logs and key user journeys after deployment.