Skip to content

[6.x] Fix customized listing columns being overridden by default preferences - #15040

Merged
jasonvarga merged 1 commit into
statamic:6.xfrom
mynetx:fix/preference-list-merging
Jul 21, 2026
Merged

[6.x] Fix customized listing columns being overridden by default preferences#15040
jasonvarga merged 1 commit into
statamic:6.xfrom
mynetx:fix/preference-list-merging

Conversation

@mynetx

@mynetx mynetx commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

When default preferences exist in resources/preferences.yaml (or on a role), customizing listing columns in the CP doesn't stick. The selection saves correctly, but on the next page load any columns you removed come back.

Preferences from each level are flattened with Arr::dot() before merging, which splits lists into numeric keys. A shorter user list keeps its own indexes but inherits the extra ones from the level below, so the removed entries reappear in the merged result. This affects any list preference, on every listing type.

Lists are now treated as single values during the merge, so the highest precedence list wins wholesale.

Fixes #14314

🤖 Generated with Claude Code

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@jasonvarga
jasonvarga merged commit 0e7e555 into statamic:6.x Jul 21, 2026
20 checks passed
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.

Listing columns don't save properly w/ global preferences

2 participants