How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

What’s new for developers? (March 2026)

calendar_today March 10, 2026 person Birgit Pauli-Haack domain wordpress

The release cycle for WordPress 7.0 is rapidly advancing. The latest Gutenberg release (22.6) has rounded up the features slated for 7.0, and the Release Candidate (RC1) is scheduled for March 19, 2026. The official Field Guide is also currently in development. WordPress 7.0 Beta 3 is now available for testing. The test team encourages participation and has published a helpful guide, including summaries and videos, to help users become familiar with the new features.

Make sure you update immediately to the security-only minor release WordPress 6.9.2 from today (10 March). It patches ten vulnerabilities: a blind SSRF, a PoP-chain weakness in the HTML API and Block Registry, regex DoS in numeric character references, stored XSS in nav menus and via the data-wp-bind directive, an AJAX authorization bypass, a PclZip path traversal, and an XXE in the bundled getID3 library—now also patched upstream.

Update March 12: In the meantime WordPress 6.9.3 + 7.0 Beta 4, and then version 6.9.4 were released.

Highlights

Real-time Collaboration (RTC)  coming to WordPress 7.0 

The underlying technical plumbing for RTC is now solved ahead of Beta 4. The implementation uses an HTTP polling sync provider, replacing unreliable WebRTC for universal compatibility across hosting environments. CRDT (Conflict-free Replicated Data Type) update data is stored persistently using post_meta on a special internal post type (wp_sync_storage). The sync provider architecture is designed so that the storage and transport layer can be swapped out. Updates are periodically compacted, and requests are batched. Client-side Gutenberg code initially limits simultaneous collaborators to two, but hosts can add a different provider or adjust defaults via a wp-config constant. The decision to enable RTC by default will be finalized around RC2. See also the accompanying Dev Note.

open_in_new Read original post