Share your feedback...
Enable Styled UI using select 2 for the select element for post object fields
I think it will be great that the same "Styled UI" option available for simple selects was available too for the select that contains the list of "Post object" type.
Copy flexible content to other pages
A way to copy one flexible content from one page to another? So like the duplicate button, but then duplicate it to another page.
Feature Request: Make ACF work in the new Woo product editor
Woo are updating the produkt editor soon, are now in beta. Please make ACF work there so we can start testing.
Conditional logic across field groups for PHP-created fields
I've run into this situation a few times where I want a setting from a field in one field group to affect field/fields in other field groups. For example, let's say we have 2 ACF theme options pages. One page called "Admin settings" (available only to admins) and one page called "Site Settings" (available to everyone). I'd like to be able to set on/off options in Admin Settings, which show/hide/alter settings in Site Settings. And I'd like to be able to do it via the condition property without having to set up any filters and whatnot. Or another use case would be an on/off switch for certain fields in blocks/elsewhere in the admin. I'm suggesting this feature be only available to PHP-created fields because you can easily just type in a field key. I understand that doing this in the ACF UI field builder could be cumbersome, so perhaps this could be a feature exclusive to PHP-created fields.
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.
Add an Icon picker for CPT, instead of having to go search the official Dashicons page
I wish to be able to directly click on an icon list instead of having to search the official Dashicons page, copy the name and paste it in ACF. I always liked this little feature in Metabox : just click an icon > done !
Now we have custom post types, it's be great to allow fields to be shown easily in admin columns without code
The tax filter on relationship field breaks the editor window when you have 50 thousands tags.
I have a news site that I am using the ACF “relationship” field to create a related articles section. Our site still uses the classic editor, with traditional ACF meta boxes to house our ACF custom fields. Our site has roughly 50,000 tags in our database, accumulated from over 25 years of publishing news. When I turn on the taxonomy filter in our related articles “relationship” field it totally crashes my editor window. The page will not scroll or resize. No errors are reported anywhere: the JS console is empty, and our php debug log is completely blank. The browser tab becomes basically unusable. It will not refresh, or do anything, I have to close the tab and reopen a new one to do anything. But if I then turn the taxonomy filter in the “relationship” field back off, everything goes back to working fine. I have tested this behavior with with all of my plugins deactivated and with only the default twenty twenty-four theme activated. I have conclusively narrowed the problem down to the taxonomy filter checkbox checked with our 50k tags. I suspect that the “relationship” field is triggering the load of all of my 50k tags, when I either scroll or resize the window. And then the browser crashes when it tries to build that enormous taxonomy dropdown menu. I have two suggestions To address this situation. I would suggest that you set the taxonomy filter to not preload all of the tags, and instead use an ajax call to query the database for the results when input is entered into the box. But regardless, loading everything into the DOM is unusable if you have thousands of tags in your system. My other suggestion would be to allow refining the taxonomy filter in the admin to only allow specific taxonomies, like you do with post types. If I could have the taxonomy filter only show categories, and not tags, that would solve the issue for me, as we only have a couple dozen cats, and are general enough to be useful for filtering.
Feature request: Show/hide the password of a password field
For the creation of front office profile management forms, the password field works perfectly. It would be very nice to have an additional option to be able to show/hide the password entered by the user in the same way, for example, as on the back office login form. Thanks in advance!