WordPress 6.7

WordPress 6.7 advanced the block editor and Site Editor rather than changing WordPress’s basic deployment model. It added the Twenty Twenty-Five default theme, introduced the Zoom Out view for working with page patterns and layout at a higher level, improved data views and block settings, and expanded template and pattern editing. It also added support for HEIC image uploads by converting them to JPEG where the server supports the required image-processing capability, improved media handling and accessibility, and included a range of performance, internationalization, and developer-facing API refinements. For sites using classic themes or the Classic Editor, many editor and full-site-editing changes are less visible, but core, media, security, compatibility, and performance changes still apply. 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.7 has reached end of life. Remaining on this cycle means the site no longer receives ongoing maintenance and security fixes through its original release line. A newly disclosed WordPress core vulnerability, compatibility defect, or regression affecting this line may therefore require an upgrade rather than a backported fix. The practical risk grows as hosting environments move to newer PHP, database, browser, and web-server versions, and as themes and plugins raise their minimum supported WordPress version or stop testing against 6.7. For WooCommerce sites, an outdated WordPress core can constrain WooCommerce upgrades and complicate troubleshooting: payment, tax, shipping, checkout, and extension problems may be caused by an unsupported combination rather than by WooCommerce alone. Delaying the move also increases the size of the eventual change, because plugin, theme, PHP, database, and custom-code updates can accumulate into a larger compatibility project.

Plan an upgrade to a currently supported WordPress release rather than treating 6.7 as a stable long-term baseline. First, inventory the active theme, child theme, plugins, must-use plugins, custom blocks, integrations, scheduled tasks, and server versions. Confirm that the target WordPress version is supported by the hosting stack and that every business-critical plugin and theme explicitly supports it. Create a production-like staging copy, take tested backups of files and the database, and upgrade WordPress, plugins, and themes in a controlled sequence. Test authenticated and public-site behavior, including forms, search, media uploads, caching, redirects, user roles, accessibility-sensitive editor workflows, and error logs. For WooCommerce stores, additionally test product management, cart and checkout, payment authorization and capture, taxes, shipping, transactional email, subscriptions or memberships where used, webhooks, order administration, and any ERP, inventory, or fulfillment integrations. Review custom code for deprecated APIs and PHP compatibility, then deploy with rollback steps and post-deployment monitoring in place. Establish a recurring core, plugin, theme, and server patching process so the site does not remain on another end-of-life WordPress cycle.