payloadcms / payloadcms/payload
Backend panel: localized group field label not show the locale (same in the subfileds)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.8k
- Forks
- 4.2k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 53
Description
Describe the Bug.
When using localized fields inside a Group field type in the Payload admin panel, the current language indicator (e.g. language badge) is not displayed next to the group field's label.
As a result, it is not immediately obvious to content editors that all fields contained within that group are localized, which can lead to confusion and mistakes when managing multi-language content.
Reproduction Steps
- Create a Collection or Global in Payload with localization enabled.
- Add a group field type and set it (or its nested fields) as localized.
- Open the Admin UI to edit the document in a specific language (e.g., Italian or French).
- Observe the group field section.
Environment Info
Payload: v3
Contributor guide
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 in a Payload v3 admin panel with localization enabled and a localized group containing localized fields. Trace the admin-panel rendering path for group field labels and the existing language indicator behavior. Done means the current language indicator appears beside the group label and the relevant nested field labels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, internationalization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100