-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When nova uses diff guard #27
Comments
something like this: |
@nenads thanks for your question. It seems like what you are wanting to do is use a different model for the sender than what is set as your base auth user model, correct? |
Yes. I gess quick fix it to get Nova guard provider. Maybe ideal is to have
morph on sender to.
BR
…On Fri, Dec 20, 2019, 17:18 Brandon Ferens ***@***.***> wrote:
@nenads <https://github.com/nenads> thanks for your question. It seems
like what you are wanting to do is use a different model for the sender
than what is set as your base auth user model, correct?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27?email_source=notifications&email_token=AAN5LMGI6CIKZJ4H5IN2ZILQZTV7FA5CNFSM4J57UINKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHNLI4Y#issuecomment-567981171>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN5LMA3PWHNPI6NXOA3Y2TQZTV7FANCNFSM4J57UINA>
.
|
We are working on a fix for this and may have it out next week, but as it is Christmas... |
Should sender be same model provider that is used by nova guard ?
The text was updated successfully, but these errors were encountered: