AdvancedCustomFields / AdvancedCustomFields/acf

Flexible content expand/collapse state (ACF 6.6.2 + Blocks v3)

Open
#986 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
945
Forks
197
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
I'm using Flexible Content field with ACF 6.6.2 + Blocks v3 (loving the new edit mode by the way!). The functionality to Expand All and Collapse All layouts is working as expected. Though if I collapse all layouts, close the Expanded Editor and then reopen it, all layouts are set as expanded not collapsed as previously set.

From past experience, this is also the same for ACF Flexible Content fields in the block editor sidebar (ACF Block Version v2 & v3). Another topic, but also Repeater fields do not remain collapsed.

To Reproduce
Steps to reproduce the behavior:

  1. Create block with Flexible Content field.
  2. Open blocks ACF Expanded Editor in block editor.
  3. Click Flexible Content "Collapse All" button.
  4. Close ACF Expanded Editor.
  5. Open ACF Expanded Editor - layouts are not collapsed.

Expected behavior
Flexible Content should adhere to the state set by the user.

Screenshots or Video
If applicable, add screenshots or video to help explain your problem.

https://github.com/user-attachments/assets/8338a46a-8e70-44e1-9a9a-a64ff80f5341

Code
Please drag and drop an export of your field group, option page, custom post type or taxonomy JSON here.
If your issue relates to ACF Blocks, please also provide a reproducable code example of your ACF Block including it's block.json so we can reproduce the issue.

acf-export-2025-10-30.json
test-block.zip

Version Information:

  • WordPress Version: 6.8.3
  • PHP Version: 8.2.29
  • ACF Version: ACF PRO 6.6.2
  • Browser: Tested in Chrome v141.0.7390.123, Safari v26.0.1
  • WordPress Theme: Twenty Twenty-Five

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the behavior with the attached test-block.zip and acf-export-2025-10-30.json in the ACF Expanded Editor. Verify the Flexible Content layouts after closing and reopening the editor; done means the user-selected collapsed state is preserved.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.