O que mudou em cada versão, da mais recente para a mais antiga. As notas são as publicadas pelo desenvolvedor, no idioma original.
Mais recente 6.8.11 · 2 nov 2026
61 versões
Desde ago 2023
2026
15 versões
Versão 6.8.11
Mais recente
Notas da versão 6.8.11: 3 correções12 reforços de segurançaMostrarOcultar
Correção
The [acf] shortcode and ACF block bindings no longer cause a fatal error on PHP 8 when a field returns objects, such as a Relationship field set to return post objects. These values, and arrays containing nested values such as an Image field set to return an array, now output nothing, except for User fields, which output user IDs
Field settings containing &, <, or certain HTML entities no longer cause the field to revert to its default settings after saving
Saving a custom choice no longer removes backslashes from the field's other settings
Segurança
Custom values submitted to Checkbox, Radio, and Select fields with "Save Custom Values" enabled can no longer corrupt the field's settings or add HTML attributes to the field's wrapper. The new acf/fields/allow_append_choices filter can be used to restrict who can add new choices to a field. Thanks to Jakub Herman via WPScan for the responsible disclosure
ACF now sanitizes field, field group, post type, taxonomy, and options page settings saved by users without the unfiltered_html capability. For those users, a field's wrapper settings are limited to width, class, and id. Event handler (on*) attributes in a field's wrapper setting are no longer output for any field, including fields registered in PHP or local JSON
Field values of password-protected posts are no longer shown by the [acf] shortcode, block bindings, JSON-LD output, or the REST API until the password is entered. REST responses also no longer expand a referenced password-protected post into a full post object
The [acf] shortcode and ACF block bindings now output only user IDs for User fields, rather than personal data such as names and email addresses. The previous output can be restored with the new acf/bindings/allow_user_data filter
Files uploaded through the basic uploader by users without the upload_files capability no longer generate PDF preview images or save embedded audio and video cover art. This can be changed with the new acf/upload/generate_previews filter
ACF now discards submitted field values unless the field was rendered for the content being saved or its field group's location rules match it. Inputs outside these rules, such as fields added with JavaScript, can be allowed with the acf/form/{context}/allowed_field_keys and acf/options_page/allowed_field_keys filters. Registration forms no longer save fields from field groups set to "User Form is Add / Edit". Thanks to vuxvinh via WPScan for the responsible disclosure
WordPress's Custom Fields meta box, its AJAX handler, and XML-RPC can no longer change meta that belongs to ACF fields
Basic uploader nonces are now tied to the content being edited
The AJAX request that loads field groups while editing a post no longer returns field groups assigned to other content
The Relationship, Post Object, and Page Link fields no longer reveal the titles or statuses of posts the current user cannot read, and no longer save newly selected posts the user cannot read. Existing selections the user cannot read are shown as "(Restricted item)" and are kept when the user saves. Thanks to vuxvinh via WPScan for the responsible disclosure
Relationship, Post Object, and Page Link values rendered in ACF Blocks now leave out posts the author of the post cannot read, such as another user's unpublished drafts. This can be disabled with the new acf/fields/relational/hide_unreadable_posts filter
Bidirectional fields now only add references to posts the current user can edit, terms they can assign, and users they can edit or set as a post's author. Saves made with update_field, WP-CLI, or cron are not checked, and the new acf/bidirectional/can_update_target and acf/is_trusted_save_context filters can adjust this. Thanks to vuxvinh via WPScan for the responsible disclosure
Notas da versão 6.8.10: 7 reforços de segurançaMostrarOcultar
Segurança
ACF now validates that uploaded PDF files begin with the standard %PDF- header before further processing, rejecting files that do not match the expected format
The Relationship, Post Object, Image, Gallery, and File fields now enforce WordPress read permissions on referenced posts and attachments when returned in REST API responses
ACF now verifies both preview context and the caller's edit capability before substituting revision data when field values are retrieved for a post
The _acf_form token used by frontend forms now expires and is bound to its issuing render, and acf_encrypt / acf_decrypt gain an optional $context argument for domain separation between token uses
ACF now consistently runs field validation on frontend form submissions containing field data, ensuring required-field checks and custom acf/validate_value filters cannot be circumvented
ACF's REST API schema no longer discloses per-object field-group configuration in OPTIONS requests to callers who lack read permission on the target object
The User field AJAX endpoint now validates that the request nonce was created for a User field
Notas da versão 6.8.9: 2 melhorias3 correçõesMostrarOcultar
Melhoria
ACF Blocks registered via acf_register_block_type or block.json without an explicit version now default to v3 on WordPress 7.1 or later. Blocks that specify a version continue to use the version they declare, and the default can be customized via the acf/blocks/default_block_version filter
ACF Blocks v3 now supports a renderPreview option in block.json. Setting "renderPreview": false shows a placeholder with the block's icon, title, and an "Edit Block" button in the editor instead of rendering the block's template as a live preview. The block continues to render normally on the front-end, and legacy v2 blocks combining "mode": "edit" with "supports": { "mode": false } are automatically migrated when upgraded to v3
Correção
Inline editable fields in ACF Blocks V3 no longer require a second click before they can be edited
Radio buttons now appear correctly in ACF admin screens
Image and Gallery fields no longer reject SVG uploads when the Safe SVG plugin is active
Notas da versão 6.8.7: 6 reforços de segurançaMostrarOcultar
Segurança
ACF Image and Gallery fields now enforce server-side validation to accept only image files
The path attribute of registered ACF Blocks is now protected from being overridden by client-supplied block data
ACF's acf_encrypt and acf_decrypt helpers now authenticate encrypted values with an HMAC and no longer fall back to base64 encoding when OpenSSL is unavailable
ACF's comment, user, and options page form save handlers now only save values for fields whose field groups are assigned to the current save context
The Post Object, Page Link, and Relationship field AJAX search queries now enforce WordPress read permissions, preventing unauthenticated visitors from seeing non-public post statuses or post types
The User field now returns only user IDs in REST API responses to requesters without the list_users capability, preventing unauthenticated visitors from seeing user email addresses
Google Maps field values are no longer double-encoded when saved in an ACF block
Inserting a Link field value in the Classic Editor no longer triggers validation for other required fields before the post is saved
Auto Inline Editing blocks no longer return truthy placeholder strings for empty field values fetched from a different post inside the block render template
ACF Blocks (V2 and V3) no longer crash when rendering an oEmbed field whose title begins with [ or {
Field group location rules without a location value no longer cause PHP warnings on page load
The appearance of the URL, Number, and Select fields has been improved on WordPress 7.0+
ACF fields now save on WooCommerce orders when using HPOS in compatibility mode
Notas da versão 6.8.5: 4 reforços de segurançaMostrarOcultar
Segurança
ACF PRO's save handler for WooCommerce order fields now verifies security nonces and only attaches on the order edit screen, preventing unauthenticated field value updates for stores utilizing HPOS
The Flexible Content "Rename Layout" modal no longer allows for the execution of a potential stored XSS vulnerability
A default limit of 1000 has been applied to user-contributed choices for Checkbox, Radio, and Select fields to improve security, with a new acf/fields/max_appended_choices filter available for customization
Special characters within LIKE patterns are now fully escaped in wp_options queries via $wpdb->esc_like
Versão 6.8.4
Notas da versão 6.8.4: 2 melhorias4 correções1 reforço de segurançaMostrarOcultar
Melhoria
ACF PRO now satisfies plugin dependencies declared against advanced-custom-fields, so plugins requiring ACF can activate when only ACF PRO is installed
Acf_inline_toolbar_editing_attrs now accepts a return_array argument that returns the attributes as an escaped array suitable for use with wp_get_attachment_image
Correção
Acf_form with 'post_id' => 'new_post' and a fields list of field names no longer fatal errors when acf_form_head runs before WordPress's main query is built
Multiple acf_form calls wrapped inside a single outer tag with one submit button no longer silently drop field values, post_title, or post_content from the non-last forms
Duplicating a V3 block with identical attributes no longer displays corrupted preview content in the duplicate
Switching between tabs containing WYSIWYG fields no longer leaves the admin menu pinned against a shorter page, which could lock page scroll
Segurança
ACF AJAX field handlers now validate that the request nonce was created for the expected field type
Notas da versão 6.8.2: 2 reforços de segurançaMostrarOcultar
Segurança
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.
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
Notas da versão 6.8.1: 4 novidades5 correções1 reforço de segurançaMostrarOcultar
Novidade
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).
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.
ACF PRO can now save metabox field values via Gutenberg's native REST flow with full revision and autosave support when using the datastore.
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
Correção
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
V3 Blocks with hideFieldsInSidebar enabled no longer show fields in the sidebar after the inline toolbar popover is closed
Scrollbars no longer appear under the tabs in field groups containing many tabs
The acf/delete-{taxonomy} ability no longer returns a 501 error when called without an explicit force argument, as terms cannot be trashed
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
Segurança
ACF now correctly checks user permissions before running database upgrades on a specific site in a multisite network
Notas da versão 6.8.0: 4 novidades7 melhorias14 correções1 reforço de segurançaMostrarOcultar
Novidade
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
ACF can now generate JSON-LD structured data fields when explicitly enabled via the enable_schema feature flag
ACF now includes WP-CLI support with new wp acf json commands for importing, exporting, syncing, and checking the status of ACF JSON files
ACF custom post Types now support the WordPress 6.9+ "Notes" editor feature via a new "Notes" checkbox in the Supports settings
Melhoria
The Blocks V3 "Open in Expanded Editor" button text can now be customized via a new acf.expandedEditorButtonText block.json property
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
The Blocks V3 edit and "Open in Expanded Editor" buttons can now be hidden via a new acf.expandedEditorButtons block.json property
A new blocks/expanded_editor_overlay_class JS filter allows customizing the CSS class on the Expanded Editor modal overlay
ACF Blocks V3 now preloads the block form HTML alongside the preview, eliminating an extra AJAX call on mount
The Expanded Editor buttons are now hidden for V3 blocks that have no fields assigned
I18n - Added Danish translation
Correção
Flexible Content fields now properly clean up nested postmeta when a parent layout containing nested Flexible Content fields is deleted
The Expanded Editor "Done" button now stays disabled until the AJAX save completes, preventing data loss
Pressing Escape while the Expanded Editor is saving will no longer close the modal, preventing data loss
InnerBlocks content containing backslashes or dollar signs now renders correctly
Auto Inline Editing now only applies to ACF Blocks V3, resolving incorrect hover/focus borders appearing on V2 blocks
Validation errors in the V3 Expanded Editor no longer cause a dead-end state
Icon Picker selections in Repeater fields no longer disappear
Range field number input now syncs to the slider and correctly updates V3 block previews
Message field Name and Instructions settings are no longer shown in the field group editor
Image field no longer crashes in WordPress 7.0 release candidates
Auto Inline Editing blocks now receive block context variables in render templates
V3 blocks registered via PHP now correctly show the "Open in Expanded Editor" button
Flexible Content disabled layouts now work correctly in Blocks V3
Auto Inline Editing now works with blocks using renderCallback
Segurança
ACF inline script tags now use wp_print_inline_script_tag for Content Security Policy (CSP) compliance and nonce support
Notas da versão 6.6.0: 2 novidades6 melhorias11 correçõesMostrarOcultar
Novidade
ACF Blocks Version 3 supports WordPress Block API Version 3
ACF now requires WordPress version 6.2 or newer
Melhoria
Field Groups can now have a separate Display Title
Accessibility improvements for button groups, checkbox, radio, and image field types
Color Picker field can now use a custom palette or use theme.json colors as the palette
ACF admin notices now use WordPress core styles again
The Flexible Content “Delete Layout” and “Rename Layout” modals now display correctly on mobile
I18n - Updated PRO Japanese translations (props danielkun)
Correção
Blocks V3: You can now edit ACF blocks in Edit mode inside WP Core's pattern editor
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
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
Blocks V3: Blocks with radio buttons no longer affect each other's field values
Blocks V3: Blocks with required radio buttons now validate correctly
Blocks V3: ACF field validation now works in the Site Editor
Blocks V3: WYSIWYG fields are no longer affected by typing into other blocks
New field names are lowercase only
Icon Picker now enforces required validation
Calls to jQuery’s deprecated focus function have been updated to use the trigger function
Layouts inside cloned Flexible Content fields can now be disabled and renamed
Notas da versão 6.4.3: 6 reforços de segurançaMostrarOcultar
Segurança
Unsafe HTML in field group labels is now correctly escaped for conditionally loaded field groups, resolving a JS execution vulnerability in the classic editor
HTML is now escaped from field group labels when output in the ACF admin
Bidirectional and Conditional Logic Select2 elements no longer render HTML in field labels or post titles
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
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
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
Versão 6.4.2
Notas da versão 6.4.2: 1 novidade2 correções1 reforço de segurançaMostrarOcultar
Novidade
In ACF PRO, fields can now be added to WooCommerce Subscriptions when using HPOS
Correção
Paginated Repeater fields no longer save duplicate values when saving to a WooCommerce Order with HPOS disabled
Blocks registered via acf_register_block_type with a parent value of null no longer fail to register
Segurança
Changing a field type no longer enables the "Allow Access to Value in Editor UI" setting
Versão 6.4.1
Notas da versão 6.4.1: 1 novidade2 melhorias3 correçõesMostrarOcultar
Novidade
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)
Melhoria
The "Escaped HTML" warning notice introduced in ACF 6.2.5 is now disabled by default
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
Correção
ACF Blocks are now forced into preview mode when editing a synced pattern
The free ACF plugin once again works with the Classic Widgets plugin and the legacy ACF Options Page addon
ACF no longer causes an infinite loop in bbPress when editing replies
Versão 6.4.0.1
Notas da versão 6.4.0.1: 1 correçãoMostrarOcultar
Correção
Calling acf_get_reference with an invalid field name no longer causes a fatal error
Versão 6.4.0
Notas da versão 6.4.0: 1 novidade3 melhorias2 correções1 reforço de segurançaMostrarOcultar
Novidade
In ACF PRO, fields can now be added to WooCommerce orders when using HPOS
Melhoria
ACF now uses Composer to autoload some classes
I18n - Various British English translation strings no longer have a quoting issue breaking links
Repeater pagination now works when the Repeater is inside a Group field
Various translations are no longer called before the WordPress init action hook
Segurança
Link field no longer has a minor local XSS vulnerability
Versão 6.3.12
Notas da versão 6.3.12: 1 melhoria2 correçõesMostrarOcultar
Melhoria
Error messages that occur when field validation fails due an insufficient security nonce now have additional context
Correção
Duplicated ACF blocks no longer lose their field values after the initial save when block preloading is enabled
ACF Blocks containing complex field types now behave correctly when React StrictMode is enabled
2024
25 versões
Versão 6.3.11
Notas da versão 6.3.11: 1 melhoria3 correçõesMostrarOcultar
Melhoria
Field Group keys are now copyable on click
Correção
Repeater tables with fields hidden by conditional logic now render correctly
ACF Blocks now behave correctly in React StrictMode
Edit mode is no longer available to ACF Blocks with an WordPress Block API version of 3 as field editing is not supported in the iframe
Versão 6.3.10.2
Notas da versão 6.3.10.2: 1 correçãoMostrarOcultar
Correção
ACF Free no longer causes a fatal error when any unsupported legacy ACF addons are active
Versão 6.3.10.1
Notas da versão 6.3.10.1: 1 correçãoMostrarOcultar
Correção
ACF Free no longer causes a fatal error when WPML is active
Versão 6.3.10
Notas da versão 6.3.10: 2 melhorias1 correção2 reforços de segurançaMostrarOcultar
Melhoria
A new “Close and Add Field” option is now available when editing a field group, inserting a new field inline after the field being edited
ACF and ACF PRO now share the same plugin updater for improved reliability and performance
Correção
Exporting post types and taxonomies containing metabox callbacks now correctly exports the user defined callback
Segurança
Setting a metabox callback for custom post types and taxonomies now requires being an admin, or super admin for multisite installs
Field specific ACF nonces are now prefixed, resolving an issue where third party nonces could be treated as valid for AJAX calls
Versão 6.3.9
Notas da versão 6.3.9: 1 correção2 reforços de segurançaMostrarOcultar
Correção
ACF fields now correctly validate when used in the block editor and attached to the sidebar
Segurança
Editing an ACF Field in the Field Group editor can no longer execute a stored XSS vulnerability. Thanks to Duc Luong Tran (janlele91) from Viettel Cyber Security for the responsible disclosure
Post Type and Taxonomy metabox callbacks no longer have access to any superglobal values, hardening the original fix from 6.3.8 further
Versão 6.3.8
Notas da versão 6.3.8: 1 reforço de segurançaMostrarOcultar
Segurança
ACF defined Post Type and Taxonomy metabox callbacks no longer have access to $_POST data. (Thanks to the Automattic Security Team for the disclosure)
Versão 6.3.7
Notas da versão 6.3.7: 1 reforço de segurançaMostrarOcultar
Segurança
ACF Free now uses its own update mechanism from WP Engine servers
Versão 6.3.6
Notas da versão 6.3.6: 3 correções2 reforços de segurançaMostrarOcultar
Correção
Validation and Block AJAX requests nonces will no longer be overridden by third party plugins
Detection of third party select2 libraries will now default to v4 rather than v3
Block previews will now display an error if the render template PHP file is not found
Segurança
Newly added fields now have to be explicitly set to allow access in the content editor (when using the ACF shortcode or Block Bindings) to increase the security around field permissions. See the release notes for more details
Field labels are now correctly escaped when rendered in the Field Group editor, to prevent a potential XSS issue. Thanks to Ryo Sotoyama of Mitsui Bussan Secure Directions, Inc. for the responsible disclosure
Versão 6.3.5
Notas da versão 6.3.5: 5 correçõesMostrarOcultar
Correção
The ACF Shortcode now correctly outputs a comma separated list of values for arrays
ACF Blocks rendered in auto mode now correctly re-render their previews after editing fields
ACF Block validation no longer raises required validation messages if HTML will automatically select the first value when rendered
ACF Block validation no longer raises required validation messages if a default value will be rendered as the field value
ACF Block validation no longer raises required validation messages for fields hidden by conditional logic when adding a new block
Versão 6.3.4
Notas da versão 6.3.4: 5 correções1 reforço de segurançaMostrarOcultar
Correção
Users without the edit_posts capability but with custom capabilities for a editing a custom post type, can now correctly load field groups loaded via conditional location rules
Block validation no longer validates a field’s sub fields on page load, only on edit. This resolves inconsistent validation errors on page load or when first adding a block
Deactivating an ACF PRO license will now remove the license key even if the server call fails
Field types returning objects no longer cause PHP warnings and errors when output via the_field, the_sub_field or the ACF shortcode, or when retrieved by a get_ function with the escape html parameter set
Server side errors during block rendering now gracefully displays an error to the editor
Segurança
The ACF shortcode now prevents access to fields from different private posts by default. View the release notes for more information
Black FridayR$ 19,90por mês
Plano Budget no cartão, preço travado
na Black Friday
Lote 1 termina em00d00h00m
Próximo lote
R$ 24,90Ver a ofertaVer oferta