Advanced Custom Fields

We are creating blocks in our local docksal setup. When we move the code changes, we keep exporting/importing the blocks json files manually. We would like to have an option to sync the blocks across all environments from lower to prod. We need a solution like this: whenever we create a block in our local environment, it automatically adds a group_key.json file under the acf-json folder, where every developer should create this folder in their theme or custom plugin. This group_key.json file will have the final version after adding/removing fields in it. If we can commit this acf-json folder, we want this new block to be auto-imported on the dev environment. Likewise, it should be with test/staging/uat and prod environments. Please let me know if you have any questions. Regards, Ram

Integrate ACF with the native WordPress Command Palette to enable quick actions like creating field groups, syncing local JSON, and navigating to ACF screens—making developer workflows faster and more intuitive.

I’ve encountered an issue when using the same field name across multiple flexible layouts. While trying to use a flexible layout field group as a clone field for a specific page, the search displays multiple fields with identical names, making it difficult to identify the correct one (screenshot: https://prnt.sc/OlqyfgIBgDMn ). I understand that adding prefixes or suffixes to field labels can help distinguish them, but I prefer to keep field labels clean and reusable across sections—for example, using “Title” instead of something like “Welcome Section Title.” As a solution, I suggest displaying the field name in the format: Field Label (field_name) instead of showing the input type like Field Label (text). This would greatly improve usability when selecting fields from a list. Appreciate your consideration! Thanks!

Is there any plan for a future release to allow content fields to dynamically load in the admin? I ask because I am using ACF to create a page builder, but I'm noticing that by nesting cloned field groups inside flexible content fields, the post editor page in the admin loads extremely slowly, due to the number of post meta fields being loaded. You're probably aware. What are your thoughts about lazy-loading field groups or fields only when they are called?

Now we have custom post types, it's be great to allow fields to be shown easily in admin columns without code

I would love to have a grid option available. Flexible Content is nice, but fields currently stack on top of each other. It would be great if there was a column option, allowing you to place multiple elements in a Flexible Content field side by side. Essentially, something like this: https://www.acf-extended.com/features/fields/flexible-content/grid-system But in the core, so that Flexible Content becomes more modern and easier to use.

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.

Add a new field type of Phone Number - pairs well with the email field. When you're asking for one, you're probably asking for both. Give options to choose how that phone number is validated (allow countries, default country, preferred countries) And allow various return formats (full number, country, number without country code, etc) JS validation: https://intl-tel-input.com/

Sometimes you need to use a WYSIWYG field for shorter texts and when a WYSIWYG field field is placed next to normal input it's initial height is just too huge. It would be nice to have some control over it.

Type declarations -> https://www.php.net/manual/en/language.types.declarations.php