WordPress 6.8

WordPress 6.8 added user-facing design and editing capabilities on top of the preceding release, including image backgrounds for Group blocks, section-level styling through block style variations, an improved Style Book, and a Query Total block for showing the number of results in a query. It also introduced speculative loading support, allowing compatible sites to prefetch or prerender likely navigation targets to improve perceived navigation speed. Core password hashing moved to bcrypt for newly created or updated password hashes, replacing the older default hashing approach while retaining compatibility with existing hashes. The cycle also included performance, accessibility, and editor refinements. 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.8 has reached end of life. Remaining on it means the site will not receive fixes delivered for later WordPress releases through this cycle, including security corrections, reliability fixes, and compatibility changes. The practical exposure grows as hosting environments, browsers, plugins, themes, and WooCommerce extensions target supported WordPress versions and stop testing against 6.8. An outdated core version can also complicate incident response: a plugin or theme issue may be difficult to distinguish from a core compatibility problem, and vendors may require reproduction on a supported WordPress release before investigating. For stores, this risk affects checkout, account, payment, shipping, tax, and administrative workflows as well as the public site.

Plan an upgrade to a currently supported WordPress release rather than treating 6.8 as a long-term baseline. First inventory the active theme, child theme, plugins, must-use plugins, custom code, WooCommerce extensions, payment gateways, integrations, and server-side dependencies. Confirm their stated WordPress and PHP compatibility, and identify abandoned components that need replacement or remediation. Take tested backups of files and the database, clone production into a staging environment, and upgrade WordPress, plugins, and themes in a controlled sequence. Test the site’s templates, block-editor workflows, forms, search, caching, scheduled tasks, media handling, user login and password reset, APIs, and any custom integrations. For WooCommerce, test product management, carts, checkout, taxes, shipping, payment capture and refunds, transactional email, customer accounts, subscriptions or bookings where used, and webhooks. Review error logs and performance after deployment, keep a rollback plan, and apply ongoing core, plugin, and theme updates through a defined maintenance process.