WordPress 7.2 Beta 1: What Developers Must Test Now

WordPress 7.2 Beta 1 drops October 20 — three days from now. If you ship plugins or themes, the Beta-to-RC window (October 20 to November 17) is the only time your bug reports can actually change what ships. After RC1, the feature set freezes. The final release is December 8. That’s your deadline to find breakage — not December 7.

Here’s what’s worth your attention before Tuesday.

InnerBlocks Template Props Are Deprecated — Migrate Before RC1

The highest-stakes change isn’t new: template and templateInsertUpdatesSelection must move from InnerBlocks props to block type settings in registerBlockType(). The props still work in 7.2 — they’re deprecated, not removed — but migrating before RC1 gives you a month to shake out bugs before the December release.

The reason for the change is real-time collaboration. The prop-based path applied templates after mount, on each connected client. Three editors inserting a List block simultaneously produced three list items. Moving the declaration into block settings means the block and its template land in a single store operation.

// Before (deprecated):
<InnerBlocks
  template={ MY_TEMPLATE }
  templateInsertUpdatesSelection={ true }
/>

// After (required):
registerBlockType( 'myplugin/my-block', {
  template: MY_TEMPLATE,
  templateInsertUpdatesSelection: true,
  // ... rest of settings
} );

About twenty core blocks are already migrated. If you haven’t acted on the deprecation notice yet, RC1 on November 17 is your practical deadline.

wp_kses() Has a New Parser — and It Changes Output

WordPress’s HTML sanitizer has run on a chain of regex functions, PCRE patterns, and outdated string processing since 2004. WordPress 7.2 targets a rewrite on top of the HTML API. This is a good thing for security and correctness — and a potential breaking change if your plugin compares, stores, or tests sanitized HTML output.

The new parser normalizes character references, strips the contents of <script> and <style> elements (not just the tags), rejects some malformed SVG and MathML, and handles broken comments differently. Output that matched a stored string before may not match after.

There’s an escape hatch — treat it as a stopgap, not a fix:

add_filter( 'wp_kses_force_legacy_parser', '__return_true' );

Ryan Welcher’s kses-html-api-demo repo lets you compare old and new output side by side — use it before Beta 1. The change targets 7.2 or 7.3 depending on testing results, but your exposure is real either way.

330 Core Icons Are Now Stroke-Based — Fill Rules Break

Gutenberg 24.1 completed the Core icon stroke redesign that started in 24.0. Roughly 330 icons are now stroke-based. A CSS fill rule or fill prop no longer recolors them.

/* Old approach — no longer works: */
.my-plugin-icon { fill: #005fcc; }

/* Correct: */
.my-plugin-icon { color: #005fcc; }

Search your codebase for hardcoded fill rules on Dashicons or block editor icon selectors. Icons still render — they just render in the wrong color. That’s the kind of bug that slips past visual QA.

Responsive Style Helpers Are Now Public

Responsive style states shipped in WordPress 7.1, but only Core blocks could use the underlying helpers — they were private. Gutenberg 24.1 changed that. @wordpress/block-editor now exports getStyleForState() and setStyleForState(), and the block editor store adds getSelectedBlockStyleState() and hasSelectedBlockStyleState().

Custom blocks can now offer the same responsive style controls Core blocks have had since 7.1 — without reaching into private APIs. If you’ve been waiting for an official path to per-viewport style overrides in custom blocks, this is it. Check the official developer roundup for usage examples.

@wordpress/dataviews Drops Private API Dependency

If you’ve seen “Cannot unlock an object that was not locked before” in a plugin that bundles @wordpress/dataviews, this fixes it. Calendar and RangeCalendar moved to @wordpress/ui, and ValidatedInputControl is now public. The issue was two copies of the private-APIs runtime in one bundle unable to unlock each other’s objects. Update your dependencies and remove any workarounds.

How to Test — and When

Install the WordPress Beta Tester plugin, switch to “Bleeding edge,” and select the Beta/RC channel. Use a staging environment, not production.

The window that matters most is Beta 1 (October 20–22). That’s when feedback can still change the December release. By RC1 (November 17), you’re verifying fixes, not requesting them.

• Blocks using InnerBlocks with a template prop
• Plugins that sanitize HTML and compare or store the output
• Theme CSS targeting icon fill colors
• Plugins bundling @wordpress/dataviews
• Anything using the Interactivity API with raw user-supplied values

Report issues on the WordPress 7.2 roadmap tracker or the relevant Gutenberg GitHub issues. Beta 1 feedback that lands before October 22 has the highest chance of making it into the final December release.