Prevents creation of custom registration form without DisplayName and no DisplayNameFormat #4015
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
valadas
changed the title
|
@tauqeer-haider Please do not use external reference number in PR or issue titles as we use titles for the release notes and those references are internal and mean nothing to visitors here. I updated the title and moved your reference number in the description. Thanks. |
david-poindexter
approved these changes
Aug 28, 2020
valadas
changed the title
valadas
changed the title
Noted. Thanks. |
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.
DNN-41046: disallowed custom form without DisplayName and lacking a DisplayNameFormat
Fixes #3971
Summary
Custom Registration Form without DisplayName field on it and lacking Display Name Format is no longer allowed and considered as incorrect configuration.