[6.x] Default legacy setAttributes to not use safeOnly#18849
Merged
riasvdv merged 1 commit intoMay 13, 2026
Conversation
riasvdv
deleted the
rias/cms-2073-6x-plugin-settings-not-saving-consistently
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fixes #18848
By default, the legacy model's
setAttributesonly allows safe attributes that are being validated. In 5.x the plugin settings would call->setAttributes($values, false)explicitly however the safeOnly behavior is not ported to 6.x as it was not necessary.All legacy callsites of
->setAttributes()call it withfalsecurrently, so making this the default for the adapter is a logical compatibility fix.