AdvancedCustomFields / AdvancedCustomFields/acf
Block renaming and 'Block name' advanced input field not functioning for ACF Blocks in WP 6.4.1
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Since the introduction of WP 6.4 (or Gutenberg 16.9), WP blocks have the capability to rename blocks unless specifically opted out using the "renaming" support flag within block.json.
Following this update, in all registered ACF blocks, there is a new input field titled "Block name" within the advanced tab. However, content entered into this field fails to save.
Furthermore, there should be a "Rename" option available in the block inserter menu for ACF blocks, but it appears to be missing.
WordPress 6.4.1
ACF PRO 6.2.3
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
Reproduce the issue with WordPress 6.4.1 and ACF PRO 6.2.3 using a registered ACF block. Check why the Advanced tab's “Block name” value is not saved and why the block inserter lacks “Rename.” Done means both renaming behaviors work for ACF blocks without opting out of block renaming support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100