You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 28, 2020. It is now read-only.
I'd like to exclude the moderators field entirely from the CreateView, and have the logged-in user automatically set as the moderator for the organization. Then include a note that tells the user "you can add additional moderators by editing your organization page after you create it".
I tried to go ahead and do this on my own, because I already implemented something like this for the Run for Office/CandidateCreateView, where the logged-in user is automatically set as the user for the candidate profile that will be created.
However, I was unsuccessful because the moderators attribute is a ManyToManyField, and I only know how to do this for ForeignKey fields...
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'd like to exclude the moderators field entirely from the CreateView, and have the logged-in user automatically set as the moderator for the organization. Then include a note that tells the user "you can add additional moderators by editing your organization page after you create it".
I tried to go ahead and do this on my own, because I already implemented something like this for the Run for Office/CandidateCreateView, where the logged-in user is automatically set as the user for the candidate profile that will be created.
However, I was unsuccessful because the moderators attribute is a ManyToManyField, and I only know how to do this for ForeignKey fields...
The text was updated successfully, but these errors were encountered: