I got a call from a client this morning. He’d just read the news about WordPress 6.9 dropping soon and had the usual questions: “Do we need to update right away? Is this going to break our custom checkout? What’s the deal with all these new features?” It’s the same conversation every few months, and honestly, I get it. The official posts, like the one on the WordPress Developer Blog, are useful, but they’re a firehose. It’s hard to tell what’s a big deal and what’s just noise.
Most of it is noise if you’re a business owner. But for us developers, a few things in this release are actually worth paying attention to. These are the practical updates that will either make our lives easier or fix a problem we’ve all fought with before.
The WordPress 6.9 features that actually matter
First up, the new WP_Block_Processor class. It sounds boring, but it’s a big deal for performance. I had a site a while back, a huge publication with thousands of posts, and running certain checks on the post content was a nightmare. The server would time out just parsing the blocks to find one little thing. This new processor is lazy-loaded, so it doesn’t pull the entire block tree into memory at once. It’s a much smarter way to walk through post content, and for high-traffic sites it’s a real performance win.
Then there’s experimental support for PHP-only blocks. I’m a senior dev, and I can write JavaScript just fine. But not everyone on my team is a React wizard, and not every project needs a full build process for a simple block. Registering a block purely in PHP lowers the barrier to entry and makes WordPress development more approachable. It reminds me of the old days of meta boxes and shortcodes, done right.
I’m also glad some features, like the improved Template Management, got pushed to WordPress 7.0. My younger self would have been annoyed. I once built a feature for a client on an experimental API that was scheduled for release, and halfway through the project it got delayed. Total mess. Lesson learned: don’t build on shaky ground. Better they take the time to get it right than ship something buggy.
A practical fix for theme developers
Here’s a small one that fixes a common frustration. You can now control which aspect ratio options the Gallery block offers, straight from your theme.json file. No more clients picking weird, off-brand image sizes; you lock it down to the ones that fit your design. Simple and clean.
{
"settings":{
"blocks" {
"core/gallery":{
"dimensions":{
"defaultAspectRatios":false,
"aspectRatios": [
{
"name": "Square - 1:1",
"slug": "square",
"ratio": "1"
},
{
"name": "Wide - 16:9",
"slug": "16-9",
"ratio": "16/9"
}
]
}
}
}
}So, what’s the point?
When a new WordPress version lands, you don’t need to panic or rebuild your site. The trick is knowing which updates are foundational and which are just nice-to-haves. For 6.9, the main takeaways:
- Performance is getting serious attention: The Block Processor is a sign of mature, under-the-hood improvements.
- Development is becoming more accessible: PHP-only blocks are a practical nod to the large community of PHP-first developers.
- Stability over shiny new toys: Pushing features to 7.0 is a good thing. It means the core team is focused on not breaking your site.
My advice to the client was simple: wait a week for the inevitable 6.9.1 bug-fix release, then update. No need to be a guinea pig on day one.
This stuff gets complicated fast. If you’re tired of debugging someone else’s mess and just want your site to work, drop my team a line. We’ve probably seen it before.
