WordPress 6.4

WordPress 6.4 expanded the block editor and site-editing tools rather than changing the underlying WordPress application model. It introduced the Twenty Twenty-Four default theme, built around patterns and several ready-made page and section layouts. The release added block hooks, allowing themes and plugins to insert compatible blocks at defined locations without requiring users to place each one manually. It also improved pattern organization and management, added background-image support for the Group block, refined navigation and toolbar behavior, and continued accessibility and editor usability work. Performance work included changes intended to reduce unnecessary loading and improve template, stylesheet, and script handling in common cases. WordPress 6.4 also included the usual broad set of bug fixes, developer API changes, and compatibility adjustments that later themes and plugins may assume are present. 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 6.4 has reached end of life. Remaining on it means the site no longer receives fixes for newly discovered WordPress core security vulnerabilities or defects through that maintenance line. This does not mean every 6.4 site is immediately compromised, but the exposure grows when a disclosed issue affects code present in the installed version and attackers can identify unpatched sites. The operational risk is also cumulative: current plugins, themes, WooCommerce extensions, hosting stacks, PHP versions, and browser expectations are increasingly tested against maintained WordPress releases rather than this older line. A plugin update may retain compatibility, but that should not be assumed from its installation requirements alone. Delaying the move can turn a routine upgrade into a larger project involving deprecated custom code, theme overrides, editor content, payment or shipping integrations, caching, and hosting changes. For stores, compatibility failures can affect checkout, order processing, account functions, tax, shipping, and payment gateways.

Plan an upgrade to a currently maintained WordPress release rather than treating 6.4 as a stable long-term baseline. First, inventory the active theme, child theme, plugins, must-use plugins, WooCommerce extensions, custom code, PHP version, database configuration, web-server rules, cron jobs, caching, backups, and third-party integrations. Make a verified backup that includes both files and the database, and confirm that restoration works in a separate environment. Clone the site to staging, update WordPress core and dependencies there, then test the public site, editor, forms, search, media handling, user roles, scheduled tasks, emails, APIs, and any custom post types or block patterns. On WooCommerce sites, place particular emphasis on product pages, cart and checkout flows, payment capture and refunds, taxes, shipping calculations, transactional email, webhooks, subscriptions, and order administration. Resolve plugin or theme incompatibilities by updating, replacing, or remediating the affected component; do not disable a security-relevant component permanently merely to complete the upgrade. Schedule production deployment with a rollback plan, monitor logs and key transactions afterward, and keep core, themes, plugins, PHP, and WooCommerce on supported versions through an ongoing patch-management process.