[faisalahammad]

With many Flexible Content layouts, the "Add Layout" menu is one long flat list and related layouts are hard to find. This adds an optional "Category" setting per layout and groups the menu by it.

What changed

• class-acf-field-flexible-content.php
  • New category layout setting (default '') in get_valid_layout(), so older layouts get the key too.
  • "Category" text input in the layout settings of the field group editor.
  • translate_field() translates the category like the label.
• FlexibleContent/Render.php
  • add_layout_menu() groups layouts by category. Layouts without a category stay at the top, so existing menus look exactly the same.
  • Categories follow the order of their first layout, and layouts keep their defined order inside a category. No extra sorting setting.
  • Each group gets a non-interactive <li class="acf-fc-popup-category"> heading, escaped with esc_html(). No JS change was needed: the popup JS only targets [data-layout], so min/max badges, disabled state and clicks skip the heading.
• SCSS for the heading and the new input, schema description and docs line.

The optional search input from the issue is not part of this PR, it can be a follow-up.

How to test

1. Add a Flexible Content field with layouts: Note (no category), Image (Media), Quote (Text), Gallery (Media), Info (no category). Save.
2. Edit a post and click "Add Row". The menu shows Note, Info, then a "Media" heading with Image and Gallery, then a "Text" heading with Quote.
3. Click a heading. Nothing happens. Click a layout. It is added as before.
4. Set Max = 1 on Quote and add one. Quote is disabled in the menu. Set Min on Image, the required badge still shows.
5. A field with no categories shows the same flat menu as before.
6. Export the field group as JSON or PHP and import it again. category is kept.

PHPUnit tests added for the default value, the flat menu, grouping order and escaping. Full PHP suite and Jest suite pass.

Closes #570

Use of AI Tools

Claude Code was used to help write the change and tests. I reviewed and tested the changes before submitting.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @Faton1995.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

Core Committers: Use this line as a base for the props when committing in SVN:

Props faisalahammad.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[cbravobernal]

Thanks for the contribution and the effort here! 🙏

A heads-up on how this repo works: a large part of SCF's codebase (field types, Flexible Content, Blocks v3, local fields, forms, value formatting, and most of includes/ and assets/src/js/) is regularly synced from an upstream codebase. Any change we make there, whether a bug fix or a new feature, gets overwritten or causes hard merge conflicts on the next sync. That includes features behind a beta flag. Fixes for those areas arrive through the sync itself, so we can't accept PRs that touch that code, even good ones.