Advanced Custom Fields

With the introduction of the ability to create new options directly in select fields (ACF v6.4.1), I’d like to propose extending this logic to taxonomy fields as well. Specifically, I suggest enabling the display and use of custom ACF fields in the ajax_add_term pop-up that appears when adding a new taxonomy term directly from a post (e.g., category or tag). Currently, in order to fill in custom field data for new terms, users must first create the term, then navigate to “Posts > Categories” (or equivalent) to edit it. This breaks the content creation flow and adds unnecessary friction. Allowing ACF fields in the term creation lightbox would significantly enhance the editing experience and improve efficiency, especially for projects that rely on complex custom taxonomies. Thank you for your consideration and for the ongoing development of this excellent plugin! --- Related discussions from the support forum: Add ACF field in ajax_add_term pop-up: https://support.advancedcustomfields.com/forums/topic/add-acf-field-in-ajax_add_term-pop-up/ Add field to add_term lightbox in taxonomy field: https://support.advancedcustomfields.com/forums/topic/add-field-to-add_term-lightbox-in-taxonomy-field/

This is a known issue with WYSIWYG stripping line breaks when published. I've installed Advanced Editor Tools (formerly Tiny MCE) solely to maintain the line breaks. It would be great feature to add to your plugin.

We often use the ACF Link Field ( https://www.advancedcustomfields.com/resources/link/ ) in combination with with image elements. Each image is wrapped in a link. We set the Link Field to required but the user can still leave the Link Field blank, which causes an accessibility issue ("Link has non-empty accessible name" – https://www.w3.org/WAI/standards-guidelines/act/rules/c487ae/ ). This is what we get: <a href="{{ link.url }}" aria-label="{{ link.title }}><img /></a> Users with screenreaders and impaired vision will not be able to understand where the link will take them – when {{ link.title }} is empty. We have a simple workaround for that: In addition to the ACF Link field, we create an ACF Text field ( https://www.advancedcustomfields.com/resources/text/ ). We make that a required field and use the value as the actual link text: Workaround: <a href="{{ link.url }}" aria-label="{{ customTextfField }}><img /></a> This works in the fontend but it is confusing for the editor. The text input "Link Text" in the ACF Link field is now without effect – and they don't know why. So the idea would be, that you add an optional parameter to the ACF Link field ( https://www.advancedcustomfields.com/resources/link/ ), that allows us to set the text input "Link Text" required – if it is needed. As far as I can tell from the available documentation online ( https://www.advancedcustomfields.com/resources/link/ ), there is no such feature yet. Thanks in advance!

The block editor has device previews (Desktop, Tablet and Mobile). Currently there is no way to detect the device type in ACF blocks. This will be handy to reinit block assets e.g. slider library js so they work correctly across all previews. There is the core function select('core/editor').getDeviceType() available, though ACF currently does not work with it.

It would be great if you could include some function into ACF for checking automatically if the max_input_vars is enough to save the actual changement of a fieldgroup. And in the case it finds it too low, to reject saving to avoid deleting existing data.

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.

Please add a Gutenberg (Block Editor) field type (similar to the WYSIWYG field type).

The feature request I would like you to consider implementing is for me to be able to set those field lengths on the back end with either a universal selection for a field group by setting all fields to 100% width for mobile within a viewport size range or to be able to adjust the field width individually for responsiveness. This especially for mobile viewports. Though not a solution for all ACF Pro users, but maybe having an added plugin or a feature that can be turned on in the pro version of your plugin is to be able to do this within different page builders. I currently use Elementor pro as my page builder and I know many people who use Elementor pro also have ACF or ACF pro as a plugin they use to help create custom post types. Having something specific to help people who are weak at coding, but would like to be able to make their forms look better and be easier to fill in would love an added feature like that either connected with there page builder or something they just have to edit in either their field group or to individual fields. You could make it so you could enter the viewport dimensions and then the field width at those dimensions. You could also make it so you can add another set of dimensions with an "add dimensions" button for either a field group or for an individual field.

Currently there is no way to attach a custom taxonomy to the users natively in ACF. Would love to see this feature getting added to ACF.

What I'm suggesting is to follow standard WP design as other parts of the system do and use this red circle counter on the main menu. Whenever there are unsynced field groups a count of them would appear in such a circle next to the ACF main menu item. It's really important to keep field groups in sync, failing to do so can cause lots of confusion and lost time. This would make it instantly clear to a dev that the site is out of sync with the json files.