What the WordPress 6.9 update changes for developers
Notes puts editorial comments on the editor canvas, the Abilities API replaces scattered capability checks for automated workflows, and classic themes finally load block styles on demand.
Notes puts editorial comments on the editor canvas, the Abilities API replaces scattered capability checks for automated workflows, and classic themes finally load block styles on demand.
A Make WordPress Core proposal would allow the PHP short echo tag for single statements. Here is why the old objection stopped applying at PHP 5.4, and how to keep the rule strict in your own phpcs.xml.
The November 2025 core committers check-in set the direction for WordPress 7.0: PHP 7.4 as the minimum, AI models running in the browser instead of on your server, and a reworked WP Admin.
Notes from a slow 80k-post news portal and what WordPress 6.9 changes about it: consistent cache keys for query groups, the new block processor and HTML API, and the Abilities API.
A pre-release WordPress install killed a client’s publish button. The cause was a core bug in hidden async-upload fields, one of several things the 6.9 release candidates cleaned up alongside alternate cron and REST API errors.
A banned member was back in ten minutes on three new accounts, because a dynamic IP beats a firewall rule. What the site actually needed was an incident response protocol: logging, permissions, and a human who owns the ban button.
A client shipped a custom plugin to the WordPress repo and got twenty-four violations back. Most of them came down to one habit: escaping data at the moment you output it instead of trusting the sanitization you did on input.
A regex that injected attributes into product images broke a store’s layout over one misplaced quote. WordPress 6.9 makes serialize_token() public, so the processor rebuilds the markup for you.
Twelve editors on one set of long-form guides, with feedback spread across Slack, email and sticky notes. Block-level notes and the hide and show toggle in 6.9 move that conversation into the editor.
A client’s WordPress.com site outgrew the managed plan after nearly a decade. The XML export timed out and broke thousands of image links, so the move became a SQL migration with a media path filter.