Advanced Custom Fields

The current pagination system for managing a large number of rows in Repeater fields is inefficient and introduces usability challenges: Navigating between pages is cumbersome, especially when switching back and forth frequently. Pages with fewer rows sometimes load out of view, disrupting the user experience. Drag-and-drop reordering, previously available, is no longer supported due to pagination. The newly introduced number-based reordering system is unintuitive and prone to errors. Proposed Solution: Replace the pagination system with a "Load More" functionality. This approach would allow additional rows to load dynamically below the already visible rows, improving navigation and usability. Benefits include: Enhanced User Experience: Users can view and interact with all rows on a single page without disruption. Reintroduction of Drag-and-Drop: Removing pagination enables the return of the intuitive drag-and-drop interface for reordering rows. Improved Workflow Efficiency: Eliminates confusion caused by the number-based reordering method. This change would streamline workflows for users managing extensive datasets in Repeater fields while maintaining performance and usability.

Support Featured Image for ACF Forms

Now in admin panel we can only see the name of current layout. It would be cool to see the key next to the layout name, eg. Layout name <i>layout-name</i>

Please consider adding support for object caching. This will speed up the admin editing experience.

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.

Since WordPress 6.2 <InspectorControls> can have “group” attribute – for example <InspectorControls group="styles"> – possible options are: – settings (default) – styles – color – typography – dimensions – border – advanced My use cases: – when creating simple ACF blocks without any field (wrappers like “container” and “group”) – for purpose of only using native Gutenberg fields from “Styles” tab and there’s no option to remove default “Settings” group completely (so in this case I would like to have no “Settings” and “Styles” tabs – similar to native paragraph block). – ability to add fields directly to one of groups – for example to color “group” to add ability to change color of specific ACF text field (so user can set all color settings from the same place in sidebar).

It looks ACF blocks that are in patterns are not preloaded. Since patterns are loaded on every block editor edit screen, this is a big performance hit. I can set an XDebug PHP breakpoint in my block template, save the block to a pattern, then load a new post with no blocks and see the PHP breakpoint processed. The block is still listed in the browser javascript console when I run acf.get('preloadedBlocks'), but I think the PHP breakpoint indicates the preloaded block is not used for loading the pattern. The pattern is still loaded with a new request to render the block.

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.

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

When an ACF Accordion field is rendered on an editing page, the interaction to expand/collapse the content is contained within a div: <div class="acf-label acf-accordion-title"> <i class="acf-accordion-icon dashicons dashicons-arrow-down"></i> <label for="acf-field_5e6b4d8f8e1a6-row-1-field_5e6b66eb2ac7d">Module 2, 3, or 4 Columns</label> </div> In this way, the interaction to expand/collapse the content is not accessible via keyboard, effectively making it impossible to use without a pointing device like a mouse or trackpad. It would be useful to insert a button inside the div and delegate the function of expanding/collapsing the content to it.