Gutenberg 23.4 is not a headline-grabbing release for most site owners, but it is a useful warning about what WordPress 7.1 may bring into day-to-day editing. The changes touch media uploads, grid layout transforms, the Site Editor interface, and early React 19 testing. Those are exactly the areas where small editor changes can surprise content teams, theme maintainers, and agencies managing several client sites.
The release landed on 17 June 2026, and the Make WordPress Core notes say Gutenberg 23.4 includes resilient media uploads, media editor refinements, Site Editor visual updates, new Grid transforms, DataViews improvements, design-system foundations, and an experimental React 19 flag. For production sites, the sensible response is to build a short test pass now, while the changes are still easy to isolate.
If you are already reviewing editor changes, the same principle applies to adjacent WordPress updates. Kahunam’s recent guide to testing GenerateBlocks Pro 2.6 forms before replacing a form plugin shows the same pattern: start with the workflows people actually use, then test edge cases before changing a live site.
Start with media uploads, especially weak connections
The most practical change for content teams is the work on media uploads. Gutenberg 23.4 adds upload progress feedback in the Block Editor, including batch upload counts, and the upload queue can pause while offline before resuming when the connection returns. That matters for sites where editors upload image-heavy pages, event galleries, case studies, or product collections.
A useful test is simple. Open a staging copy of a page, upload several images at once, then interrupt the network connection during the upload. When the connection returns, check whether the queue resumes clearly and whether the editor gives enough feedback for a non-technical user to understand what happened.
Do the same test on mobile if your team edits on tablets or phones. The media editor modal also received interface changes, including editable attachment fields near the top of the details panel, aspect ratio controls in the mobile toolbar, and plus/minus zoom buttons. Those changes should make media handling easier, but only if your theme, image sizes, and editorial habits fit the new flow.
Check whether Grid transforms preserve real content
Gutenberg 23.4 allows block transforms to target a variation of another block. The visible result is that Columns and Gallery blocks can transform into Grid layouts while preserving their content. This is the sort of change that can save time during layout work, but it needs testing on real pages rather than empty demo blocks.
Pick pages that use Columns for service comparisons, team profiles, logos, image groups, or repeated content panels. Transform them into Grid layouts on staging and inspect the result at desktop, tablet, and mobile widths. Look for lost spacing, unexpected ordering, image crops, button alignment issues, and any custom CSS that was written against the old Columns markup.
For agencies, this is also a good regression test for reusable patterns. If a site relies on synced patterns or a shared pattern library, test the transform on a copy first. A transform that looks fine on one page can expose assumptions in the pattern’s spacing, wrapper classes, or responsive behaviour.
Review the Site Editor in different admin colour schemes
The Site Editor sidebar and page shell now follow the user’s WordPress admin colour scheme instead of always using a fixed dark background. This sounds cosmetic, but it can affect support screenshots, internal documentation, and training material. It can also expose contrast problems in plugin UI that appears inside the editor shell.
Test this with at least two admin colour schemes. Open templates, template parts, global styles, navigation editing, and any plugin panels your team uses inside the editor. The aim is to catch controls, labels, borders, and focus states that become harder to see when the surrounding editor chrome changes.
Treat React 19 as a developer test, not a client toggle
The release includes an experimental flag that can register React 19 versions of the WordPress runtime scripts. The Make WordPress Core post says developers can activate the React 19 experiment from the experiments page at /wp-admin/admin.php?page=experiments-wp-admin. That is useful for plugin, theme, and block testing, but it should stay out of normal client workflows unless a developer is actively testing it.
The official notes call out warnings and console errors as things to watch. They also recommend testing custom admin pages that use React, editor UI that uses refs, ref callbacks, portals, or third-party component libraries, and build pipelines that use react/jsx-runtime. In plain terms, this is a compatibility pass for custom code and editor integrations.
If you maintain a custom block plugin, test it with the experiment enabled on a disposable staging site. Open the block inserter, edit saved content, change settings, save, reload, and check the browser console. Then disable the experiment and repeat the same flow. You want to know whether any issue belongs to the React 19 experiment or to the ordinary editor state.
Add smaller checks for dashboard, DataViews, and collaboration work
Some Gutenberg 23.4 changes will matter more to plugin developers and product teams than to everyday editors. The release notes include work on a new dashboard experience experiment, a filterable DataViews configuration API, Playlist block improvements, Login/out block placement inside Navigation Submenu blocks, and real-time collaboration reliability fixes.
These should not dominate a site-owner test plan, but they are worth noting if your site uses those areas. A membership site might care about the Login/out block inside navigation. A publisher with audio content might care about Playlist block settings. A team building custom admin screens may care about DataViews configuration. Match the test effort to the features your site actually uses.
A practical Gutenberg 23.4 test checklist
- Upload several media files at once in the Block Editor and confirm progress feedback is clear.
- Interrupt the connection during an upload on staging, then confirm the upload queue resumes after reconnecting.
- Open the media editor on desktop and mobile and check attachment fields, aspect ratio controls, and zoom controls.
- Transform real Columns and Gallery blocks into Grid layouts and compare desktop, tablet, and mobile output.
- Check custom CSS and reusable patterns after Grid transforms.
- Review the Site Editor with more than one admin colour scheme.
- Test custom blocks, plugin admin pages, and editor integrations with the React 19 experiment on a disposable staging site.
- Watch the browser console for warnings and errors during React 19 testing.
- Check whether Playlist, Login/out, dashboard, DataViews, or collaboration changes affect features your site uses.
What to do before WordPress 7.1
Gutenberg releases do not map perfectly to the next WordPress core release, but they are still the best early signal for editor behaviour that may reach client sites. For Gutenberg 23.4, the highest-value tests are media resilience, Grid transforms, Site Editor appearance, and React 19 compatibility for custom code.
Keep the test pass narrow. Use a staging site, pick a few representative pages, record anything that affects editors, and separate visual changes from functional regressions. That gives you a clear decision before WordPress 7.1 reaches production: update as normal, update with notes for editors, or hold back while a theme or plugin issue is fixed.
Primary source: What’s new in Gutenberg 23.4? (June 17, 2026).
Author
