AdvancedCustomFields / AdvancedCustomFields/acf
ACF Blocks Todo list
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Hi all 👋,
Welcome to the ACF Blocks todo list. Here you will find all the items we are working on for the upcoming ACF Blocks feature.
Bugs
- Unload prompt always shows even after post is published
- Field value is lost when deleting / recreating a field with the same name
- Default values are not loaded in render_callback
- Prevent "edit html" option
- Duplicate Block is not working
- Reusable Block is not working
- Conflicting input names cause issues with duplicate fields (radio)
- Field widths in sidebar should be ignored (100% width CSS override)
- Fix "reordering" rows not affecting preview (rep/flex row index number => string)
Features
- Allow "alignment toolbar' to be disabled / customized
- Support the "anchor" setting for table of contents
- Use icon in alignment toolbar to switch between edit/preview
- Add setting for default mode (edit/preview)
- Add setting for default align (full, wide, left, right)
- Add setting to restrict mode
- Allow render_callback to provide different front/back markup
- Add render_template setting to avoid callback function
- Add setting to restrict post types
Ideas
- Save values using field name instead of field key
- WP renders all dynamic blocks on "edit page load" (see
wp.apiFetch.createPreloadingMiddleware()inline script). Take advantage of this to avoid AJAX preview requests on initial load. - Use "acf/prepare_field" to change input key to name. Add hidden inputs for "_acf_reference"
- Add post_id value to $block parameter in callback
- Add JS actions during "switch" and "render" events.
Tasks
- Write documentation for
acf_register_block()function. - Write documentation for ACF Blocks feature.
Please leave any comments below, but try not to bloat this ticket into a chatroom.
Thanks
Elliot
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue is a completed ACF Blocks checklist, with every bug, feature, idea, and task marked done; no file or test is named. There is no remaining scope to start from, so review references such as acf_register_block(), render_callback, render_template, and wp.apiFetch only if maintainers reopen a specific item.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100