[4.x] Exclude super when using a custom field #9536
Merged
Conversation
This file contains 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
JohnathonKoster
pushed a commit
to JohnathonKoster/cms
that referenced
this pull request
Feb 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When you're editing a user while logged in as a super user, we add a toggle for you. We also check your permission on the server side when saving it back onto the user.
However if you explicitly added your own super field onto the blueprint,
$fieldswould containsuper, and the value gets applied without running through the check.This PR excludes it from the values so it has to go through the explicit check.
It also removes it from the "User information" step of the create form. If you're a super user, it'll already be on the "Roles & Groups" step.