Plugin ACF PRO (Advanced Custom Fields Pro)

6.8.2

Release Date 26th May 2026

• Security – ACF frontend forms (acf_form()) now respect the post_title and post_content form configuration options when processing submissions, ensuring those values are only saved when the form is configured to accept them. Thanks to Sarawut Poolkhet (MisterHelloz) for the responsible disclosure.
• Security – ACF frontend forms (acf_form()) now only save values for fields assigned to the form via the fields or field_groups parameters, or via the form’s location rules

6.8.1

Release Date 13th May 2026

• Security – ACF now correctly checks user permissions before running database upgrades on a specific site in a multisite network
• New – A wp.data store (acf/fields) is now available in ACF PRO for reading and writing ACF field values from JavaScript, which can be enabled via a new acf/settings/enable_datastore filter (requires WordPress 6.7 or later).
• New – ACF PRO block bindings now support live preview and editing in the block editor, when both the datastore and the enable_block_bindings setting are enabled.
• New – ACF PRO can now save metabox field values via Gutenberg’s native REST flow with full revision and autosave support when using the datastore.
• New – ACF PRO Blocks can now define their field group inline via an acf.fields array in block.json, or via a fields argument in acf_register_block_type(), with field keys auto-generated and scoped to the block
• Fix – Repeater and Flexible Content row helpers no longer trigger a PHP 8.x TypeError when row_index_offset or the active loop index is non-numeric
• Fix – V3 Blocks with hideFieldsInSidebar enabled no longer show fields in the sidebar after the inline toolbar popover is closed
• Fix – Scrollbars no longer appear under the tabs in field groups containing many tabs
• Fix – The acf/delete-{taxonomy} ability no longer returns a 501 error when called without an explicit force argument, as terms cannot be trashed
• Fix – The prepare_field_for_ability_import filter is now correctly removed after each Abilities field group import, preventing subsequent imports in the same request from having values corrupted

6.8.0

Release Date 30th March 2026

• View Release Post
• New – ACF now integrates with the WordPress Abilities API, allowing external consumers (AI tools) to manage field groups, post types, and taxonomies when explicitly enabled via the enable_acf_ai feature flag
• New – ACF can now generate JSON-LD structured data fields when explicitly enabled via the enable_schema feature flag
• New – ACF now includes WP-CLI support with new wp acf json commands for importing, exporting, syncing, and checking the status of ACF JSON files
• New – ACF custom post Types now support the WordPress 6.9+ “Notes” editor feature via a new “Notes” checkbox in the Supports settings
• Enhancement – The Blocks V3 “Open in Expanded Editor” button text can now be customized via a new acf.expandedEditorButtonText block.json property
• Enhancement – A new acf/blocks/default_expanded_editor_button_text PHP filter allows customizing the default “Open in Expanded Editor” button text for all V3 blocks
• Enhancement – The Blocks V3 edit and “Open in Expanded Editor” buttons can now be hidden via a new acf.expandedEditorButtons block.json property
• Enhancement – A new blocks/expanded_editor_overlay_class JS filter allows customizing the CSS class on the Expanded Editor modal overlay
• Enhancement – ACF Blocks V3 now preloads the block form HTML alongside the preview, eliminating an extra AJAX call on mount
• Enhancement – ACF inline script tags now use wp_print_inline_script_tag() for Content Security Policy (CSP) compliance and nonce support
• Enhancement – The Expanded Editor buttons are now hidden for V3 blocks that have no fields assigned
• Fix – Flexible Content fields now properly clean up nested postmeta when a parent layout containing nested Flexible Content fields is deleted
• Fix – The Expanded Editor “Done” button now stays disabled until the AJAX save completes, preventing data loss
• Fix – Pressing Escape while the Expanded Editor is saving will no longer close the modal, preventing data loss
• Fix – InnerBlocks content containing backslashes or dollar signs now renders correctly
• Fix – Auto Inline Editing now only applies to ACF Blocks V3, resolving incorrect hover/focus borders appearing on V2 blocks
• Fix – Validation errors in the V3 Expanded Editor no longer cause a dead-end state
• Fix – Icon Picker selections in Repeater fields no longer disappear
• Fix – Range field number input now syncs to the slider and correctly updates V3 block previews
• Fix – Message field Name and Instructions settings are no longer shown in the field group editor
• Fix – Image field no longer crashes in WordPress 7.0 release candidates
• Fix – Auto Inline Editing blocks now receive block context variables in render templates
• Fix – V3 blocks registered via PHP now correctly show the “Open in Expanded Editor” button
• Fix – Flexible Content disabled layouts now work correctly in Blocks V3
• Fix – Auto Inline Editing now works with blocks using renderCallback
• i18n – Added Danish translation

6.7.2

Release Date 26th March 2026

• Security – Users’ unfiltered_html capability is now correctly applied to REST API calls
• Security – Block Preview rendering now correctly checks the user has permission to edit that post
• Security – Repeater fields using pagination now correctly checks the user has permissions to edit that post
• Security – Flexible content fields layout title AJAX requests now correctly verify security nonces
• Security – Clone field AJAX admin endpoints now correctly check ACF admin permissions for field group listings

6.7.1

Release Date 3rd March 2026

• Security – User field AJAX queries now enforce field-configured role restrictions and validate search permissions
• Security – Post Object, Relationship, and Page Link field AJAX queries now enforce field-configured restrictions for post status, post type, and taxonomy

6.7.0

Release Date 3rd December 2025

• View Release Post
• New – ACF Blocks V3 now supports Inline Editing – edit your block content directly in place, right inside the editor. Just opt in to enable it.
• Enhancement – Accordion field accessibility improvements
• Enhancement – Google Maps field accessibility improvements
• Enhancement – Styling improvements to the V3 Blocks expanded editor
• Fix – V3 ACF Blocks validation now clears properly when more than one block is in the editor.
• Fix – Relationship, Post Object, and Page Link fields now sort posts correctly on WordPress 6.8+
• Fix – List tables now respect the convert_field_name_to_lowercase javascript filter
• Fix – WYSIWYG field on attachment pages no longer sends ajax on every keystroke

6.6.2

Release Date 29th October 2025

• Enhancement – Added a new convert_field_name_to_lowercase JS filter to allow uppercase letters in ACF field names
• Enhancement – The form for V3 Blocks can now be optionally hidden from the sidebar via a new hideFieldsInSidebar setting in block.json
• Enhancement – V3 Blocks now display an “Open Expanded Editor” button in the sidebar for easier access to the full edit form
• Fix – The buttons to reorder ACF metaboxes are no longer hidden for metaboxes in the block editor sidebar
• Fix – V3 Blocks now display a fallback message when the block preview can’t be rendered due to invalid HTML being used in field values
• Fix – V3 Blocks no longer show a loading spinner when preloaded
• Fix – V3 Blocks now save default field values even if the block wasn’t interacted with before saving
• Fix – Pressing CMD/CTRL + Z no longer causes the fields to disappear in V3 Blocks
• Fix – The form for V3 Blocks now opens on the left side in RTL languages

6.6.1

Release Date 16th October 2025

• Fix – The Color Picker palette now displays correctly with a larger number of custom palette colors
• Fix – The WYSIWYG field no longer displays an extra textarea in ACF Blocks
• Fix – The type signature of the ACF Blocks render function now matches prior to 6.6, resolving potential type hinting errors
• Fix – V3 Blocks now correctly update the block preview when changing text controls
• Fix – V3 Blocks now work correctly in the Widget block editor
• Fix – V3 Blocks no longer render an extra hidden div into the block editor
• Fix – Fields on V3 blocks now consistently render properly when switching between “Post” and “Block” view in the sidebar

6.6.0

Release Date 7th October 2025

• View Release Post
• New – ACF Blocks Version 3 supports WordPress Block API Version 3
• New – ACF now requires WordPress version 6.2 or newer
• Enhancement – Field Groups can now have a separate Display Title
• Enhancement – Accessibility improvements for button groups, checkbox, radio, and image field types
• Enhancement – Color Picker field can now use a custom palette or use theme.json colors as the palette
• Enhancement – ACF admin notices now use WordPress core styles again
• Enhancement – The Flexible Content “Delete Layout” and “Rename Layout” modals now display correctly on mobile
• Fix – Blocks V3: You can now edit ACF blocks in Edit mode inside WP Core’s pattern editor
• Fix – Blocks V3: Validation errors now first appear after you click “Save/publish”, as opposed to immediately, while you are typing into a field for the first time
• Fix – Blocks V3: After fixing a field validation error it shows as fixed immediately as opposed to needing to click out of the block and back into it
• Fix – Blocks V3: Blocks with radio buttons no longer affect each other’s field values
• Fix – Blocks V3: Blocks with required radio buttons now validate correctly
• Fix – Blocks V3: ACF field validation now works in the Site Editor
• Fix – Blocks V3: WYSIWYG fields are no longer affected by typing into other blocks
• Fix – New field names are lowercase only
• Fix – Icon Picker now enforces required validation
• Fix – Calls to jQuery’s deprecated focus function have been updated to use the trigger function
• Fix – Layouts inside cloned Flexible Content fields can now be disabled and renamed
• i18n – Updated PRO Japanese translations (props danielkun)

6.5.0

Release Date 11th August 2025

• New – Flexible Content layouts can now be renamed in the post editor, giving content editors better clarity when managing layouts
• New – Flexible Content layouts can now be disabled, preventing them from rendering on the frontend without needing to delete their data
• New – Flexible Content layouts can now be collapsed and expanded in bulk for faster content editing
• New – Editing a Flexible Content layout now highlights the layout being edited, making it easier to identify
• New – The Date and Date Time Picker fields can now be configured to default to the current date
• Fix – Custom Icon Picker tabs now work correctly when used inside an ACF Block
• Fix – Duplicating a Field Group no longer causes a fatal error when using Russian translations
• Fix – ACF classes no longer use dynamic class properties, improving compatibility with PHP 8.2+
• Fix – ACF PRO no longer shows an update available immediately after updating to the latest version
• Fix – Field group metabox collapse and expand buttons are no longer misaligned in the post editor
• Fix – The ACF Site Health section no longer causes a PHP warning when field group location rules are incomplete
• Security – HTML is now escaped from field validation errors and tooltips

6.4.3

Release Date 22nd July 2025

• Security – Unsafe HTML in field group labels is now correctly escaped for conditionally loaded field groups, resolving a JS execution vulnerability in the classic editor
• Security – HTML is now escaped from field group labels when output in the ACF admin
• Security – Bidirectional and Conditional Logic Select2 elements no longer render HTML in field labels or post titles
• Security – The acf.escHtml function now uses the third party DOMPurify library to ensure all unsafe HTML is removed. A new esc_html_dompurify_config JS filter can be used to modify the default behaviour
• Security – Post titles are now correctly escaped whenever they are output by ACF code. Thanks to Shogo Kumamaru of LAC Co., Ltd. for the responsible disclosure
• Security – An admin notice is now displayed when version 3 of the Select2 library is used, as it has now been deprecated in favor of version 4

6.4.2

Ngày phát hành 20 tháng 5 năm 2025

• Mới – Trong ACF PRO, giờ đây có thể thêm các trường vào WooCommerce Subscriptions khi sử dụng HPOS
• Bảo mật – Thay đổi loại trường không còn kích hoạt cài đặt “Cho phép truy cập giá trị trong giao diện người dùng trình chỉnh sửa”
• Sửa lỗi – Các trường Lặp lại được phân trang không còn lưu các giá trị trùng lặp khi lưu vào Đơn hàng WooCommerce với HPOS bị vô hiệu hóa
• Sửa lỗi – Các khối được đăng ký thông qua acf_register_block_type() với parentgiá trị nullkhông còn lỗi khi đăng ký

6.4.1

Release Date 8th May 2025

• New – Select fields can now be configured to allow creating new options when editing the field’s value (requires the “Stylized UI” and “Multiple” field settings to be enabled)
• Enhancement – The “Escaped HTML” warning notice introduced in ACF 6.2.5 is now disabled by default
• Enhancement – The Icon Picker field now supports supplying an array of icons to a custom tab via a new acf/fields/icon_picker/{tab_name}/icons filter
• Fix – ACF Blocks are now forced into preview mode when editing a synced pattern
• Fix – The free ACF plugin once again works with the Classic Widgets plugin and the legacy ACF Options Page addon
• Fix – ACF no longer causes an infinite loop in bbPress when editing replies

6.4.0.1

Release Date 8th April 2025

• Fix – Calling acf_get_reference() with an invalid field name no longer causes a fatal error

6.4.0

Release Date 7th April 2025

• New – In ACF PRO, fields can now be added to WooCommerce orders when using HPOS
• Enhancement – The “Escaped HTML” warning notice is now disabled by default
• Enhancement – ACF now uses Composer to autoload some classes
• Fix – Repeater pagination now works when the Repeater is inside a Group field
• Fix – Various translations are no longer called before the WordPress init action hook
• Security – Link field no longer has a minor local XSS vulnerability
• i18n – Various British English translation strings no longer have a quoting issue breaking links
• i18n – Added Dutch (formal) translations (props @toineenzo)