Skip to content

fix(ui): render named group child fields when permissions.fields is empty (Closes #17812) - #17814

Open
waterWang wants to merge 1 commit into
payloadcms:mainfrom
waterWang:fix/group-child-fields-not-rendered-main
Open

fix(ui): render named group child fields when permissions.fields is empty (Closes #17812)#17814
waterWang wants to merge 1 commit into
payloadcms:mainfrom
waterWang:fix/group-child-fields-not-rendered-main

Conversation

@waterWang

Copy link
Copy Markdown

Same fix as #17813 but for the main branch.

Description

When a named group field renders its children, it passes permissions?.fields to the inner RenderFields component. If permissions.fields is empty or missing, the inner RenderFields receives undefined or {} as permissions, causing getFieldPermissions to return read: false for all child fields — producing an empty .render-fields container.

Changes

  1. Permissions fallback: When permissions.fields is empty or missing, fall back to the group's own permissions object.
  2. forceRender propagation: Added missing forceRender prop to the inner RenderFields.

Closes #17812

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

group fields render an empty RenderFields container — no children in the admin

1 participant