Fix cascading settings attr writer behavior
If set value matches the cascaded value, do not save locally. This fixes an issue where a simple settings form save by a subgroup would cause a cascaded value to be saved at the subgroup level, defeating future cascading lookups. Also, when setting a lock attribute and the local setting is `nil`, copy the value locally to ensure ancestors can't change the intended value for subgroups later. Changelog: fixed
Showing
Please register or sign in to comment