ACF 6.8.1 Release: Datastore, Block Bindings, and Security Fixes
Enable the new datastore to get revision, autosave, and JS API for ACF fields, and consider block bindings and inline field groups.
Add the enable_datastore filter, test in staging, update block.json for inline fields, enable block bindings, verify multisite permissions, and run WP‑CLI sync commands.
Summary
ACF 6.8.1 introduces a new wp.data store (acf/fields) that integrates ACF fields into Gutenberg’s native save flow, enabling full revision support, autosave integration, and a JavaScript API for reading and writing field values.
The datastore is opt‑in and requires WordPress 6.7 or later; it can be enabled with add_filter('acf/settings/enable_datastore', '__return_true').
When enabled, block bindings become live‑previewable and editable directly in the editor, and ACF fields can be bound to block attributes via the new Attributes panel.
Developers can now define field groups inline in block.json, keeping field definitions co‑located with block code and eliminating the need to manage field keys manually.
A security hardening fix ensures that only super admins can run database upgrades in multisite environments, preventing subsite administrators from triggering cross‑site upgrades.
Bug fixes address PHP 8.x compatibility for repeater and flexible content helpers, sidebar field visibility after toolbar popover, tab scrollbars, and abilities API errors.
The release also includes improvements to block bindings UI, live preview, and the ability to save metabox values via Gutenberg’s REST flow.
All updates are opt‑in and should be tested in staging before production deployment.
Key changes
- New wp.data store acf/fields for revision, autosave, and JS API
- Block bindings UI and live preview enabled with datastore
- Inline field groups defined in block.json via acf.fields array
- Security fix: only super admins can run database upgrades in multisite
- PHP 8.x compatibility fixes for repeater and flexible content helpers
- Bug fixes: sidebar field visibility, tab scrollbars, abilities API errors
- Requires WordPress 6.7+ and opt‑in datastore filter
- All updates are opt‑in and require staging testing