WordPress 7.0 features are landing in rapid succession, and while the “shiny new tools” are getting the headlines, the technical plumbing underneath is where the real war is being fought. Between the move to Beta 3 and the massive security sweep in 6.9.2, if you haven’t updated your staging environments yet, you’re already behind the curve.
I’ve spent the last 14 years watching release cycles, and 7.0 feels like one of those foundational shifts—similar to when Gutenberg first dropped. However, before we dig into the cool stuff, let’s talk about the fires you need to put out today. Specifically, the WordPress 6.9.2 security release.
The 6.9.2 “Emergency” Patch
If you haven’t seen the advisory, go check it now. It patches ten vulnerabilities including a nasty blind SSRF and a PoP-chain weakness in the HTML API. These aren’t just “theoretical” risks; they’re the kind of holes that lead to full site takeovers if you’re running complex nav menus or using the data-wp-bind directive. Patching is non-negotiable.
Real-time Collaboration: The Internal Plumbing
The most anticipated WordPress 7.0 features include Real-time Collaboration (RTC). But here is the catch: it’s not using WebRTC. The team made a pragmatist’s call to use an HTTP polling sync provider. Why? Because WebRTC is a nightmare for universal hosting compatibility.
Technically, it uses Yjs under the hood, but the storage layer is a custom internal post type called wp_sync_storage. It stores Conflict-free Replicated Data Type (CRDT) updates in post_meta. If you’re worried about race conditions, the sync provider architecture is designed to be swappable. You can actually adjust the defaults or swap providers via a constant in your config.
// You can tweak RTC limits or providers via wp-config.php
define( 'WP_RTC_MAX_COLLABORATORS', 5 );
For more context on the long-term vision of these shifts, check out my thoughts on WordPress 7.0 development and the AI client debate.
AI Connectors: A Standard Interface at Last
We finally have a provider-agnostic way to handle AI. WordPress 7.0 introduces the “Connector” feature built around the php-ai-client package. This isn’t just another wrapper; it’s platform-level infrastructure. Instead of every plugin author writing their own OpenAI or Anthropic integration, we code against a shared interface. Switching providers becomes a simple configuration change in the new Connectors screen.
If you’re building block-based AI tools, you should stop writing proprietary API handlers and start looking at how to hook into this package. It saves you from the maintenance hell of tracking API changes for five different LLM providers.
Gutenberg Refinements: Content-Only is the New Default
One major shift in the editor is that Patterns now default to Content-Only editing. This reduces UI clutter for clients but can be a headache for devs who need structural access. You can opt out of this globally or per-pattern using a simple filter.
<?php
// bbioon_disable_content_only: Keep structural access open for unsynced patterns
add_filter( 'block_editor_settings_all', function( $settings ) {
$settings['disableContentOnlyForUnsyncedPatterns'] = true;
return $settings;
} );
We also see visual change tracking in revisions. It uses color-coded overlays (green for additions, red for removals) which is a massive win for client handovers. No more “What did I break?” phone calls. They can see the yellow outline for modified block settings themselves.
WP-CLI and Local Dev Tooling
For those of us living in the terminal, the new wp block and ability commands are huge. We’re finally getting read-only access to block entities at the CLI level, with stable support for pattern exports coming in v3.0 later this month. Also, wp-env now supports phpMyAdmin in the Playground runtime—reaching feature parity with Docker setups without the overhead.
Look, if this WordPress 7.0 features stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
Takeaway for Devs
The 7.0 release isn’t just another incremental update; it’s an architectural cleanup. Between the standardized AI interfaces, the RTC polling provider, and the SVG Icon Registration API, the “WordPress way” is becoming significantly more structured. Use this Beta cycle to refactor your legacy hooks and ensure your themes honor the new block-defined feature selectors. Stability in 7.0 depends on us following the new standards rather than hacking around them.
