Skip to content

[6.x] Fix non-localizable button group fields being editable in localizations - #15151

Merged
jasonvarga merged 3 commits into
statamic:6.xfrom
lazerg:fix/issue-15149-button-group-read-only
Aug 11, 2026
Merged

[6.x] Fix non-localizable button group fields being editable in localizations#15151
jasonvarga merged 3 commits into
statamic:6.xfrom
lazerg:fix/issue-15149-button-group-read-only

Conversation

@lazerg

@lazerglazerg commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

A button_group field with localizable: false stayed clickable in a localization, and clicking an option desynced the field and wrote the new value into the localization's own content file instead of leaving it to resolve from the origin.

This used to work. fb4f58b swapped the fieldtype's :disabled="isReadOnly" for :read-only="isReadOnly", but Button was never given a readOnly prop, so since then the binding has landed on the element as an inert attribute and the click handler has stayed live.

Added the prop and folded it into the button's disabled state, the same way the Radio component handles it. The control appearance fieldtype and the revealer fieldtype's button mode pass the same prop to Button, so those are covered too.

Fixes#15149

@jasonvarga
jasonvarga merged commit 039d4e0 into statamic:6.xAug 11, 2026
61 checks passed
Sign up for freeto 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.

Non-localizable button_group field is editable and saved in localizations

2 participants

@lazerg@jasonvarga