4.3.5
Hotfix release — restores the Gutenberg block editor experience.
Root cause
If you’ve been running 4.3.3 or 4.3.4 and noticed the Core Forms block in the editor showing a generic blue “CF” square icon and a single dropdown — no live preview, no inspector panels — this release fixes it.
src/admin/class-admin.php was still enqueuing a legacy assets/js/gutenberg-block.js (a pre-4.0 hand-written registerBlockType call) on enqueue_block_editor_assets. That script registered core-forms/form first, so every modern block-form.js bundle — with ServerSideRender, inspector controls, and the correct form icon — was shipping in every zip but never actually loading in the editor.
The legacy wp_enqueue_script() call also passed no version argument, which is why network-tab diagnostics showed gutenberg-block.js?ver=7.0 (the WP core version) instead of the plugin version. Thanks to the user who reported this from their network tab — that’s what pinpointed it.
Changes
- Removed the
enqueue_block_editor_assetslistener andenqueue_gutenberg_assets()method fromclass-admin.php. - Deleted the orphan
assets/js/gutenberg-block.js. - block.json now owns the entire editor lifecycle —
register_block_type(__DIR__ . '/block.json')loadsassets/js/build/block-form.jswith the modern Edit component, and theversion: "4.3.5"field cache-busts it againstCORE_FORMS_VERSION. - Reverted the 4.3.4 form-picker label change back to
Title (slug)so forms sharing a base title stay distinguishable in the dropdown.
Upgrading
Just update. Hard-refresh the editor once (Cmd/Ctrl+Shift+R) to clear the cached gutenberg-block.js?ver=7.0 from your browser — after that the modern block editor UI is back.
🤖 Generated with Claude Code