[4.x] Fix blueprint error when creating user #9276
Merged
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.
This pull request fixes an issue where you'd see an error when attempting to create a user in the Control Panel without there being a user blueprint saved (eg. no
resources/blueprints/user.yaml
file).It doesn't look like the
ensureFieldHasConfig
method works when theemail
field is added to the blueprint viaensureField
.cms/src/Http/Controllers/CP/Users/UsersController.php
Line 119 in 720d8a8
To workaround this, I've made it so the User blueprint always has an
email
field so it'll exist forensureFieldHasConfig
being called in the controller.I don't know lots about how the field ensuring stuff works so let me know if there's a better way to fix this.
Fixes #9274.