WordPress 7.0 is still in beta, having missed its first release candidate deadline due to concerns around installation size and the default behavior of real-time collaboration.
Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.
Program transcript
Hello, I’m Alicia Ireland, and you’re listening to WPpodcast, bringing the weekly news from the WordPress Community.
In this episode, you’ll find the information from March 16 to 22, 2026.
The WordPress 7.0 release cycle had a small adjustment this week. Release Candidate 1, originally scheduled for Thursday, March 19, has been pushed back to Tuesday, March 24. The reason is three last-minute concerns: real-time collaboration performance, client-side image optimization, and the size of the installation package.
Beta 6, which includes over 130 fixes, brings notable changes since Beta 5. The client-side image processing feature has been temporarily reverted to resolve the issues found. Real-time collaboration is now opt-in by default, with a configuration constant for those who want to control it at the server level using WP_ALLOW_COLLABORATION. Additionally, the collaboration sync intervals have been multiplied by four — from 250 milliseconds to 1 second — to reduce the number of HTTP requests and server impact.
The final release date for WordPress 7.0 remains April 9, so the window is still workable if the first release candidate ships in the coming days.
WordPress 7.0 brings a solid set of block editor updates, and several dev notes have been published covering the details:
Text indent. The paragraph block now includes an indent control in the typography options — one of the community’s longest-standing requests. It can be configured to apply only to paragraphs that follow another paragraph, as is common in English-language publishing, or to all paragraphs, which is more typical in other languages.
Per-block custom CSS. It is now possible to add custom CSS to any individual block directly from the Advanced panel in the editor, without having to go to the Site Editor or add classes manually. Changes are reflected in real time while editing. Only users with permission to edit CSS have access to this option.
Block width and height. Width and height controls are now standard options in the Dimensions panel, on par with margin and padding. Themes can also define preset sizes so users can choose from specific options instead of entering values manually.
Per-device visibility. Any block can now be shown or hidden based on device type — desktop, tablet, or mobile — independently of one another. Controls are available in the toolbar, the sidebar panel, and the command palette. The List View displays icons indicating which devices a block is hidden on.
Improved pattern editing. Unsynced patterns and template parts now default to a content-focused editing mode that hides block structure and layout controls, letting users focus on text and media. Full editing mode is accessible with one additional click when layout changes are needed.
Pattern overrides for custom blocks. Synced pattern overrides — which allow customizing the content of each pattern instance without altering the original design — now work with any custom block, not just core blocks as before.
Connectors API. WordPress 7.0 introduces a new screen under Settings called Connectors, which centralizes the management of connections to external services. For now it focuses on AI providers, with built-in support for Anthropic, Google, and OpenAI. From this screen, users can install the corresponding provider plugins, enter API keys, and check the status of each connection. The architecture is designed to expand in the future to other types of services.
The Plugin directory has received its own MCP server, meaning AI assistants like Claude, Cursor, or AI-enabled VS Code can connect directly to the directory to help developers prepare and submit their plugins.
Three tools are available: validating the readme.txt file before submitting a plugin, checking the status of a pending review request along with reviewer feedback, and submitting a new plugin or updating one already in the review pipeline. The AI agent also has access to reference documents such as the directory guidelines, the developer FAQ, and the list of reserved slugs, allowing it to provide accurate, up-to-date guidance while you work.
And finally, this podcast is distributed under a Creative Commons license as a derivative version of the podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WPpodcast .org.
Thanks for listening, and until the next episode!
Leave a Reply