WordPress 6.9 gives AI integration an actual standard
A client wanted a sparkle button by Friday. What WordPress 6.9 actually shipped matters more: the Abilities API and the MCP adapter, which give AI agents a defined way to talk to a site.
Author: Ahmad Wael
I'm a WordPress and WooCommerce developer with 15+ years of experience building custom e-commerce solutions and plugins. I specialize in PHP development, following WordPress coding standards to deliver clean, maintainable code. Currently, I'm exploring AI and e-commerce by building multi-agent systems and SaaS products that integrate technologies like Google Gemini API with WordPress platforms, approaching every project with a commitment to performance, security, and exceptional user experience.
What the WordPress 7.0 roadmap means for your build
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.
Gutenberg 22.2 puts button hover states in theme.json
Gutenberg 22.2 lets you define button hover and focus states in theme.json instead of a separate stylesheet, and it accepts YouTube or Vimeo embeds as Cover block backgrounds.
What WordPress 6.9 features mean for high-traffic sites
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.
WordPress 6.9 core updates and the bugs RC4 fixed
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.
What the WordPress MCP Adapter 0.3.0 release changes
A wrapper around a few REST endpoints wasn’t enough to keep an AI agent alive through a timeout. Version 0.3.0 of the WordPress MCP Adapter covers what I had to hand-roll: HttpTransport, WP_Error responses, prefixed hooks and one event stream.
How the WordPress plugin review process works now
A client’s plugin kept bouncing back out of the queue, so here is what changed: 60,187 plugins in the directory, 7,670 submissions this year, and 85.3% of first reviews started by an automated scanner rather than a person.
What a moderation fight taught me about incident response
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.
Why custom plugins fail WordPress security standards
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.
The WordPress HTML API in 6.9 replaces your regex hacks
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.