Advanced Custom Fields

I just tested how the v3 block changes will impact our blocks. In doing so I see that the acf>mode value in blocks.json is no longer being respected, not for v2 blocks either (contrary to what is written in the release posts which say that v2 will keep working like it did). We usually use mode:preview, and force the users to use the fields on the side. But even with v2 blocks, you can now switch to the edit mode in the UI. I can somewhat understand that in v3 this won't be an option – because no edit mode will be available anymore. Some feedback about the edit button – might I suggest removing the edit button and instead adding a "expand" icon in the block sidepanel, which brings up the larger panel with block fields. Perhaps the "mode" needs to be thought out from scratch. Just throwing an example out there field_position: auto (both), sidebar, full auto – gives the current solution (though I would recommend adding a expand button) sidebar – fields are only shown in sidebar, full – fields are only visible in the expanded panel, sidebar shows a short text and button for accessing these. Why though? sidebar: if fields are simple, you don't really need the additional view full: if you have large repeaters, flexible content, nested fields, etc. those will just look very cluttered in the sidebar

In ACF, if we modify labels, descriptions, or options of a field, the value of field_nnnn remains unchanged. However, if we change the meta slug, a new field_nnnn is generated. This causes the existing data in post_meta to become orphaned. It would be better if changing the slug did not affect field_nnnn, so the link with existing data stayed intact. On the other hand, if we create a completely new field, then a new field_nnnn should indeed be generated. Thanks

It would be useful to be able to pass on variables to specific children in innerblocks via templates or another system. For example, the widths you put in a parent block can be passed on to the children so that the widths of columns are entered in 1 easy field, instead of in each column separately. Being able to pass variables via innerblocks ensures that we can create advanced and interesting blocks that are now quite by the wayside.

For certain applications such as creating your own column system, it would be useful to have an index for each child block. In this case, for example, we could use the index to set the width of each column in 1 field in the parent. This could also make advanced structures possible where the Xste child block needs a different structure. So in short: being able to address an index for each child block within “innerblocks”.

They are both great features but: If data is fetched in other ways than the standard ACF way, disable doesn't work out of the box and I can't find a workaround for this. I have implemented my own feature for renaming layouts which clashes with your new one and I don't want to force editors to switch to the new one and lose all names they have already set. So it would be great if those features could be disabled with filters. If possible, layout specific filters but if that doesn't work, global will also work. And preferably to be able to disable them separately. For now, I am using CSS to hide the actions but that always feels like a hack that can easily break if you change the dom. Thank you for a great plugin that is one of the major reasons as to why I have stayed with WordPress!

ACF is adding 0.545 seconds in average to the pagespeed when activated. And uses almost 1MB memory per visitor. Most plugins use 200KB memory or below, with no pagespeed impact. Here's the analysis and details: https://plugintests.com/plugins/wporg/advanced-custom-fields/latest

Add a new custom logic feature which checks if the selected block is inside another block (innerblock) or if its placed on root level. Advanced solution would be to also check if the selected block is inside a specific block (maybe with textfield where one can write the name of the block)

See https://github.com/AdvancedCustomFields/acf/issues/969 for more details. Rank Math is using the native WP link popup, so there's no way I can hide these checkboxes on popups tied to ACF. Also, it's very misleading and buggy for editors as they attempt to save the checkboxes constantly and they always remain unchecked when the admin screen is reloaded.

My company uses CloudFlare for our WAF and have configured all of our WP Engine site to use "orange-to-orange". Unfortunately this makes our environment incompatible with automatic SSL in WP Engine, since you MUST have the primary DNS pointing directly to WP Engine for automatic TLS renewals to work. I'd like to request ONE of the two features below, either one would solve our problem. Allow automatic SSL to work with Orange-to-Orange configurations. You can still do HTTP validation for the Lets Encrypt certificates on your origin. Implement an API endpoint to generate Certificate Signing Requests (CSRs) for each domain. Along with the existing API to upload third party certificates this would allow us to build a script to automate the TLS renewals.

While working with ACF Pro, I noticed that the plugin currently does not support undo/redo actions in text fields (e.g., Ctrl + Z). This makes it difficult to recover accidentally deleted content, as users have to retype everything from scratch. I’d like to request the addition of undo/redo functionality within ACF fields to improve usability and prevent data loss. This would be a valuable enhancement for everyday workflows.