WordPress 7.0 is getting smarter about when to load the post editor inside an iframe: it will now only do so when every block in the post is API version 3 or higher. Gutenberg 22.6 starts enforcing this for classic themes, while full rollout in core is being phased in gradually. If you maintain custom blocks, now is the time to upgrade to v3.
See what's changing
Amy Kamala and Jb Audras are officially WordPress Core Team Representatives for 2026. Kamala, sponsored by Elementor, also serves as Hosting Team Rep and release coordinator for the upcoming 7.0 launch, bringing a strong hosting and development background to the role. Audras returns as a veteran committer with deep roots in the project.
Meet the reps
A security flaw in the Embed Optimizer plugin was responsibly disclosed and patched fast, with a fix already out in the wild. The performance team also flagged a concern: real-time collaboration features may inadvertently disable object caching on the frontend.
Read the full summary →
WordPress 7.0 Beta 2 is landing on February 26, keeping the project on track for its April 9 final release. Today's dev chat puts the AI Connectors feature under the spotlight and opens discussion on three Real Time Collaboration issues flagged during last week's review with Matt Mullenweg.
Check the agenda →Laravel's Blade templating engine is now within reach for WordPress developers, thanks to the Radicle starter theme and Acorn framework. Kinsta's hands-on tutorial walks you through building reusable layouts, slots, and components so a single file update covers your entire site's nav or footer. A cleaner, more maintainable way to build.
Read the tutorial
This week's news circles back to one theme: WordPress 7.0 is not just a version bump, it's a platform shift. From iframe logic overhauls and new leadership to Beta 2 on the doorstep and AI Connectors in active development, the core team is moving with rare focus and speed. Developers who want to stay ahead should be watching every release note closely.