This allows the Recipients.email to be filled by the user who invited the guest when only_me is true and manditory #920
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
… the guest when only_me is true and manditory
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.
This relates to #900 and the presentation of the person who invited the guest would not happen if the can_only_send_to_me was set default=true and available=false in config.php.
Note that attempts to send explicit recipients if can_only_send_to_me=true is already caught in RestEndpointTransfer and blocked with TransferTooManyRecipientsException. This change explicitly sets the database up so that the inviter is captured as the recipient for presentation when can_only_send_to_me is forced to true and not even shown as an option to the user.