WordPress 6.9 strips out the old Internet Explorer compatibility code. If you run an older custom theme, here is what tends to break and how to audit and modernize the CSS and JavaScript behind it.
A vague “Bug fixes” changelog leaves your team guessing after an update. Clear changelogs with dated, categorized entries cut support headaches and protect your reputation.
A client deployed WordPress 6.9 RC1 straight to a live WooCommerce store and it broke. The fix is not a rollback, it is a real testing plan: a dedicated environment and conditional code keyed to the WordPress version.
A look at what the WordPress 6.9 release candidate phase changes for developers, from the string freeze to which tickets still qualify and the double sign-off needed to backport a fix.
A real case from a client site: how the WordPress 6.9 heading block CSS specificity fix changed padding on custom feature boxes, and why a proper fix beats a quick override.
The Interactivity API: This is the big one. For years, if you wanted modern, app-like experiences on your site—like a search filter that updates results…
Why I stopped building one-off REST endpoints for a client AI integration and used the WordPress 6.9 Abilities API instead, with the code to register a single ability.
A run through the small WordPress 6.9 changes that actually help developers, from a multisite fix for the News widget to term ID taxonomy templates and a new plugin requirements hook.
WordPress 6.9 ships a Notes feature that keeps editorial feedback inside the block editor instead of scattered across Docs, Asana, and Slack. A look at how it works under the hood and where it still falls short.
A WooCommerce migration left European customers’ accented characters showing as garbled symbols. WordPress 6.9 replaces the old guesswork functions with validation, and here’s how to use them.