I’ve been watching the Gutenberg version numbers climb for years, and plenty of releases amount to polish. Gutenberg 23.0 is not one of those. It goes after a couple of structural problems that have annoyed developers since the FSE (Full Site Editing) rollout started: there is finally a path toward template revisions, and a way to stop legacy meta boxes from killing real-time collaboration.
Revisions for templates and patterns
If you have ever spent three hours getting a Header template right and then watched a client delete a Group block, you know the feeling of hitting save and realizing there is no undo. Revisions used to be a posts and pages thing only. Gutenberg 23.0 starts changing that.
The new experimental revisions panel brings the standard revision UI to templates, template parts and patterns. It ships inside the Editor Inspector: Use DataForm experiment, so you have to switch it on under Gutenberg → Experiments before you can test it. It runs on the unified DataForm-based inspector, which is where the whole Site Editor is heading. It is rough at the moment, which is what experimental means, but it is the biggest step yet toward a Site Editor you can hand to a non-technical user.
For a sense of how this interface has been shifting, I covered Gutenberg 22.9 updates a while back.
RTC and the legacy meta box problem
Real-Time Collaboration (RTC) gets treated as the holy grail of the block editor, and it shipped with a kill switch: if the editor spotted a legacy meta box, RTC was disabled, no questions asked. Plugin authors had no way around it.
Gutenberg 23.0 adds a filterable flag, __rtc_compatible_meta_box. It lets you tell WordPress that your meta box will not cause race conditions while two people edit at once. Apply it through the filter_block_editor_meta_boxes hook.
<?php
/**
* Mark a specific meta box as RTC compatible.
*/
add_filter( 'filter_block_editor_meta_boxes', function( $meta_boxes ) {
foreach ( $meta_boxes as &$meta_box ) {
if ( 'bbioon_custom_settings' === $meta_box['id'] ) {
$meta_box['__rtc_compatible_meta_box'] = true;
}
}
return $meta_boxes;
} );
Polling reliability got hardened too. One corrupted sync update no longer takes down the poll cycle for everyone else in the room. On enterprise sites with several editors in the same post, that is the fix that has been missing since the initial RTC rollout in version 22.8.
The guidelines rename will bite you
The Guidelines experiment is the part that needs a warning label. If you were using it before, Gutenberg 23.0 renames everything internally: slugs went from content-guidelines to plain guidelines, and that covers the Custom Post Type (CPT) slug, the REST base and the Redux store.
The experiment flag was renamed along with the rest, so it will probably read as disabled once you update. You will need to turn it back on, and if you were depending on those specific meta keys, you may have to migrate your data. Update the plugin, lose the settings. Go slowly here.
Smaller refinements
- Site Title and Tagline are now editable straight from the Design › Identity panel in the Site Editor, so you stop bouncing back to Settings → General.
- Block toolbar tooltips finally show the move-up and move-down shortcuts, which makes a keyboard-only workflow noticeably quicker.
- The four side inputs for padding and margin re-order into a more sensible layout once you unlink them.
If this Gutenberg 23.0 work is eating your dev hours, hand it over to me. I have been wrestling with WordPress since the 4.x days.
Where this leaves you
This one is part “finally” and part “watch out.” 174 PRs went in, and the direction is clear enough: make the Site Editor as dependable as the Post Editor. If you build custom blocks or run complicated client sites, start testing the __rtc_compatible_meta_box flag now, because multi-user editing in WordPress is going to run through it.
