A sixth beta looks like bad news until you have watched a couple of “final” releases fall over in week one. WordPress 7.0 Beta 6 is out, and the extra cycle reads to me as the core team buying itself room to stabilize. If you have been following the WordPress 7.0 roadmap, you know how much is riding on this version.
The headline move is a retreat. Client-side Media Processing has been reverted, which cuts the package size and leaves the core more focused. I will take a delayed feature over debugging a race condition in a client’s media library on launch day.
What actually changed in WordPress 7.0 Beta 6
There are 132 updates and fixes since Beta 5, and the most technical of them sits in the Real-Time Collaboration (RTC) infrastructure. Polling intervals are now 4x longer, which cuts the stream of HTTP requests a collaborative session fires at the server.
RTC handling was one of the rough edges in earlier betas. In WordPress 7.0 Beta 6 collaboration is opt-in by default, which is the right call. Most sites do not need the overhead, and a constant set at config level keeps that decision with whoever runs the server.
Defining the collaboration constant
Switching the collaboration features on means adding a constant to your wp-config.php. Guard it the way below so older environments do not trip over it.
<?php
/**
* Enable Real-Time Collaboration in WordPress 7.0
*/
if ( ! defined( 'WP_ALLOW_COLLABORATION' ) ) {
define( 'WP_ALLOW_COLLABORATION', true );
}
The constant exists, but RTC still leans hard on server resources. Test it on a staging environment that matches your production hardware, and do that before the April 9th release rather than after.
Performance and package size
Reverting Client-side Media Processing shrank the overall package, which helps automated deployment pipelines and anyone on a slow connection. It is ordinary refactoring judgment: a feature that adds 20% to the weight and 2% to the utility gets cut until the implementation gets better.
Report whatever you hit during testing on WordPress Trac. One reproducible bug report beats a thousand complaints in Slack. The editor is the place to look hardest, since the new 4x polling interval can feel laggy on a high-latency connection.
If WordPress 7.0 Beta 6 testing is eating your dev hours, hand it to me. I have been wrestling with WordPress since the 4.x days.
The road to RC1
RC1 is scheduled for March 24th, which makes WordPress 7.0 Beta 6 the last chance to clean up inside the beta stage. Most of the 74 editor fixes in this build go at how fragile the block editor feels when several people work in the same post.
The official Make WordPress Core blog carries the detailed technical notes, and it stays the source of truth for what the rest of us build on. Happy debugging.
