An option to disable fields
It would be handy to have a control to disable fields when a field group is being added/edited. This can be useful for testing purposes to quickly and temporarily switch fields off and on.
Compatibility with Big File Uploads
Any plugin hooking into uploads needs to use the equivalent sideload hooks, like wp_handle_sideload_prefilter. So ACF has no compatibility with Big File Uploads at the moment. Would be great to support this, thanks! More Infos: https://developer.wordpress.org/reference/functions/_wp_handle_upload/#hooks https://wordpress.org/plugins/tuxedo-big-file-uploads/ https://github.com/uglyrobot/big-file-uploads/issues/12
Flexible field - collapse all fields with shift
You can collapse all repeater rows when clicking "collapse" button with Shift. It would cool to implement the same logic when collapsing flexible fields.
Taxonomy: limit to choose only one for each post
Radio Buttons instead Checkboxes. Goal would be to limit the user to only select one category for each post.
Store field data in custom database tables
Instead of storing field data in the post meta table, store the field values in a custom database table. This reduced performance issues and makes the data easier to query.
Fields in Group: Support bidirectional relationships
Currently listed in known issues is the limitation that fields inside groups dont support bidirectional relationships. We use groups sometimes and would be glad if this is supported. https://www.advancedcustomfields.com/resources/bidirectional-relationships/#known-issues Thanks
Ability to use a React component as the template in the block editor preview for ACF Blocks
Currently ACF Blocks needs a PHP template to render the preview of the block in the Block Editor. However, for headless builders they are building their frontend templates not in PHP but in React or another framework. When building an ACF Block, the render template is in PHP. This is used on the frontend of the site as well in the backend as the preview when editing in the block editor. For some developers using frontend framework to render their blocks, having to recreate the same component in PHP so it can be rendered in the editor is a hassle. Allowing them to tell ACF to use the frontend component will make their lives easier and give the content editors the true preview of the block.
Now we have custom post types, it's be great to allow fields to be shown easily in admin columns without code
ACF Blocks UI to be more like native blocks
When editing fields in ACF Blocks in the block editor, the UI for inputs can be different from the native WP block settings. This can be confusing to clients.
❤️ maintain extended block.json $schema
could acf maintain this schema instead ? https://gist.github.com/saulirajala/359775273c62fa19ea232ced18c10712 Copy from WP block.json schema ( https://schemas.wp.org/trunk/block.json ), but added support for acf key as defined here: https://www.advancedcustomfields.com/resources/acf-blocks-with-block-json/ We want better acf key support right? 😉 https://github.com/AdvancedCustomFields/acf/issues/834