WordPress 7.0 pulls View Transitions into core, and ticket #64066 raises preloading eagerness when a proxy cache is detected. Here is what that changes for admin speed, and why blanket prefetching pinned my CPU at 100%.
The 2026 proposal moves WordPress back to three majors a year, roughly one every four months, with one to three minors in between. Freezing a client site at 6.7 is what taught me why that cadence is easier to live with.
WooCommerce 10.4.3 patches guest order data exposure in the Store API, throttles HPOS sync-on-read during heavy jobs, and restores the cart undo link that 10.4.2 broke.
WordPress itself is free to download, but hosting, premium licenses and maintenance are not. Where the money actually goes once a site has to earn its keep.
WordPress may go back to three major releases in 2026, roughly one every four months. What that faster cadence means for staging, testing and custom code.
A deleted product used to take down order history with a fatal error. WooCommerce 10.4.2 adds the null check, along with PHP 8.4 transient validation and support for the renamed WordPress 6.9 Abilities API hooks.
I dismissed WordPress Playground as a browser toy. It now installs almost every popular plugin, runs Composer and Laravel, and spins up a shareable environment per ticket, which has replaced most of my staging work.
Real-time collaboration is targeted at WordPress 7.0 in 2026. Beta feedback says native blocks work fine and legacy post meta does not, so custom fields need registering for the REST API before then.
A client with fifteen editors kept losing work to overwrites, which is exactly what Phase 3 collaboration is meant to solve. Here is what else the 7.0 planning covers: React 19, block validation levels, block bindings and the AI Client API.
The 6.9 update turned a client’s custom blocks into ghosts and I nearly wrote a core override for it. The December dev chat notes had the answer already: hotfix plugins now, official maintenance release in January 2026.