A DataForm group with children is a layout container, not another data field. If an update changes its validation or collapsed panel summary, check whether your form depended on the group's ID also matching a field definition.
This is a developer diagnostic for custom WordPress admin interfaces. It is separate from an excerpt panel disappearing entirely. For that symptom, begin with the DataForm inspector compatibility guide.
Find the accidental contract
The merged Gutenberg change treats combined fields consistently as layout containers. Their IDs no longer cause the group itself to inherit a same-ID field definition's validation. The panel layout also stops using that ID overlap as an implicit summary definition.
Inventory the actual fields and the form layout separately. A field definition describes data and its behavior. A form group describes how children are arranged. Giving both the name address1 does not make the group an address value.
For each combined group, write down its ID, child IDs, any matching field definition, the expected collapsed summary and the business rule that must still hold on save. Inspect nested groups too. A correct outer group does not prove a nested one is independent of the old behavior.
Container: Separate layout ID from data. Children: Validate the actual fields. Summary: Choose displayed fields explicitly. Save: Preserve existing records. Proposed verification, not a customer test result.
Put validation on the value it protects
Suppose a custom address panel contains street, city and postal code. A required rule attached only to a field definition whose ID matches the container may no longer protect the child values in the way your integration expected.
Move the relevant rule to the actual field that needs it. If the rule concerns several fields, handle that relationship through a supported validation path in your installed version and enforce the requirement on the server as well. Do not invent a hidden required field solely to keep a group-level error alive.
Test three synthetic records: a complete address, a visible required city with no value, and a record where a field is deliberately hidden by your interface rules. Record which control displays an error and what the server accepts. Client visibility is not permission to save prohibited data.
The upstream regression test demonstrates that a hidden child is skipped in the relevant client validation path and that the same-ID container definition does not supply an extra required rule. It does not promise that every custom validator or endpoint behaves the same way.
Make the panel summary intentional
If the collapsed panel previously showed a status or first address line only because a group ID matched a data field, configure the panel's summary explicitly. The upstream migration uses layout.summary with field identifiers.
For a synthetic address group, the intended relationship might be:
Container ID: address-panel
Children: street, city, postal-code
Panel summary fields: street
Validation: attached to real child fields
Stored record: unchanged by opening the panel
This is a configuration worksheet, not a complete DataForm API example. Build the actual layout using the types supported by your installed package. Check the current panel layout options rather than copying a proposal into a production plugin.
Compare collapsed and expanded views. Change the street, save, collapse and reopen. Then change a non-summary child such as postal code. The summary should represent the chosen field without silently overwriting or hiding the other changes.
Test both editing surfaces
If the same configuration powers a post inspector and Quick Edit, run the same records through both. Confirm that their save payloads contain the same intended values and that permissions remain enforced. An attractive collapsed row is not evidence that the record was saved correctly.
For a regression report, include a minimal fields definition, the combined form layout, a synthetic record, the old and new package versions, and the exact error or summary difference. Remove real addresses and private post content.
Do not rename database keys to repair a layout-only collision unless a separate data migration is actually required. First fix the UI configuration, then verify that existing records survive an open/save/reopen cycle. Get help with a WordPress admin regression when the same form serves several roles or editing surfaces.
Primary evidence: combined fields change and migration examples, including its validation test and panel story updates. This guide proposes checks for your integration; it does not claim that all WordPress admin forms use this implementation.
References reviewed October 20, 2026. Diagrams and test fixtures are explanatory, not customer results.
If the summary targets the correct field but looks blank when its value is empty, use the placeholder-specific diagnostic: WordPress DataForm Shows a Blank Panel Summary: Add a Placeholder.