An unplanned Beta 6 landed on March 20, 2026, and Release Candidate 1 moved back to March 24. Anyone who has run production sites for a while reads the word “unplanned” as a warning about the weekend ahead. This one is the opposite. A project manager loses four days of schedule, and everyone else gets four more days of testing before WordPress 7.0 is called done.
Why an extra beta is good news
RC1 did not slip over UI polish. This release carries the DataViews-based admin overhaul and drops support for PHP 7.2 and 7.3, and either of those can take plugins down with it. I went through this in my earlier take on WordPress 7.0 Beta 6 stability, and the short of it is that an extra testing round at this point in the cycle is usually what stops the fires on launch day.
What the Connectors API standardizes
The Connectors API is the addition with the most weight for plugin authors. Until now, every plugin that talked to an external service, OpenAI or Mailchimp or anything else, shipped its own settings page and its own credential storage. The result was fragmented and hard to secure.
Provider setup and credential handling now live in a shared core layer. A plugin asks for a connection, and core decides how those credentials are stored and refreshed, so talking to an external provider looks the same whichever provider it is.
<?php
/**
* Registering a custom service provider using the Connectors API
*/
function bbioon_register_custom_service_connector() {
if ( ! function_exists( 'wp_register_connector_provider' ) ) {
return;
}
wp_register_connector_provider( 'my-custom-service', array(
'label' => __( 'My Custom Service', 'text-domain' ),
'description' => __( 'Connects your site to a custom external backend.', 'text-domain' ),
'type' => 'api_key', // Standardized credential type
'setup_url' => 'https://example.com/setup-guide',
) );
}
add_action( 'init', 'bbioon_register_custom_service_connector' );
Twenty Twenty-Seven and the open floor
The same dev chat put out a call for volunteers on the Twenty Twenty-Seven default theme. It is early days, and the core team wants to push block-based design further with it. The open floor at the end of the agenda is still the most reliable way to unstick a ticket that has stalled in the milestone backlog, so if you have a PR gathering dust, raise it in the #core Slack channel.
If WordPress 7.0 is eating your dev hours, or you are not sure whether your custom stack survives the update, I can take it off your plate. I have been wrestling with WordPress since the 4.x days.
What this means for your sites
The RC1 delay says the core team knows how much is moving in this release. Between the new Connectors API and the refined admin views, WordPress 7.0 is closer to a platform shift than a routine update. Test your hooks and filters against it now. Finding out on release day that your legacy code fails the new PHP requirements is a much worse afternoon.
