If you are using django allauth and include this in your settings.py ACCOUNT_EMAIL_VERIFICATION = 'mandatory'
then you will be good to go. On Apr 12 2019, at 10:03 pm, Flip Matter <silverstrings...@gmail.com> wrote: > Django you so much, I believe having a separate Post model would be the way > to go. Recifes to get going on allauth and that's turning out to be way > easier than I expected so all of you have basically fixed everything so thank > you VERY much. Now I just need to figure out how to do email verification and > I'll be good to get the rest of the site done. > > On Wed, Apr 10, 2019, 12:34 PM 'dtdave' via Django users > <django-users@googlegroups.com (mailto:django-users@googlegroups.com)> wrote: > > > > To me the way I build my models is so that if anyone looked at the code > > they would see exactly what the model represented. I had a great mentor in > > Daniel Greenfield of Two Scoops Fame. > > So my models would be users and then a separate model for public posts. > > The you have the following in your settings > > > > AUTH_USER_MODEL = 'users.CustomUser' > > and everything would br fine. > > You could then use this users modle elsewhere. > > Also I have never seen the templates done your way. You can just have a > > single: > > 'DIRS': [os.path.join(BASE_DIR, 'templates')], > > Then you can either have your templates in under the relevant app name e.g > > public_posts/templates/public_posts > > or in one template folder split into the apps. Different people have there > > own ideal method so it is really up tp you. > > Hope this helps > > > > > > On Wednesday, 10 April 2019 13:45:27 UTC+1, Flip Matter wrote: > > > Thank you very much for the resources! However it is installed in my > > > settings.py the exact line is... AUTH_USER_MODEL = > > > 'public_posts.CustomUser' > > > > > > Is there a different way to do it? This is the only way I have seen to > > > set your AUTH_USER_MODEL, or does my custom user model have to be in a > > > 'users' app? > > > > > > > > > > > > On Sat, Apr 6, 2019 at 10:26 AM 'dtdave' via Django users > > > <django...@googlegroups.com> wrote: > > > > The error you are getting is because the CustomUser is not included in > > > > your settings.py > > > > Because I use a separte user model my settings.py has this line in it: > > > > AUTH_USER_MODEL = 'users.CustomUser' > > > > I would recommend that you have your Custom User as a separate user > > > > model. > > > > > > > > For good tutorials on user models have a look at these links: > > > > https://wsvincent.com/django-tips-custom-user-model/ > > > > https://wsvincent.com/django-login-with-email-not-username/ > > > > https://wsvincent.com/django-custom-user-model-tutorial/ > > > > > > > > Django All-Auth is a good app for customising your user models: > > > > https://www.intenct.nl/projects/django-allauth/ > > > > Hope this helps! > > > > > > > > > > > > > > > > On Friday, 5 April 2019 15:58:19 UTC+1, silverst...@gmail.com wrote: > > > > > Hello, I've been trying to make a social media site and know nothing > > > > > about django (i've been teaching myself using the documentation and > > > > > tutorials) I've had to redo the site three times and now have to do a > > > > > fourth because (even though I got AUTH_USER_MODEL in, all the forms > > > > > ect. ect. before first migration) for some reason it is saying that > > > > > "Manager is unavailable; auth.User has been swapped for > > > > > public_posts.CustomUser". I have not been able to find a decent > > > > > description on exactly how work flow NEEDS to be done. Obviously > > > > > create user models and set AUTH_USER_MODEL before first migration but > > > > > what about the Manager? I made my CustomUserManager at the same time > > > > > as everything else. > > > > > > > > > > I tried to use django-registration, then found out they upgraded to > > > > > django_registration, couldn't find ANY documentation on it until > > > > > almost a week afterwards. So now my code is partially a bunch of > > > > > tutorials and partially old (possibly deprecated) code, is there > > > > > somewhere that all of the new stuff and how to transfer to the new > > > > > stuff posted? This seems to be the hardest part about Django, for me > > > > > anyway. I've tried get_user_model where user comes up to no avail. I > > > > > have three apps, admin_posts, public_posts and accounts (get ready to > > > > > smirk cuz this was stupid of me) I have all my CustomUser stuff in > > > > > public_posts and have everything required by django_registration in > > > > > accounts. I'm positive that was a huge fail on my part but Where > > > > > SHOULD all of the user stuff go?? I have no been able to find > > > > > anything about that anywhere everything only says ' > > > > > appname.CustomUser' (example) leading me to believe that it doesn't > > > > > matter where you put them. but since django_registration has its own requirements and user dealings, will using django_registration and CustomUsers cancel each other out/mess up each others managers? > > > > > > > > > > Everything I have done has only been in my project(s) and not in the > > > > > root dir. Also, if anyo contributors to django read this, thank you > > > > > for making such a freaking amazing framework, I mean this thing is > > > > > just a pure beauty so thank you!!! Y'all be some geniuses! I hope to > > > > > be good enough to contribute. > > > > > > > > > > Thank you for making it to the end and thank you for any responses. > > > > > P.S I only post as a last resort, I've spent HOURS researching this > > > > > to no avail, not even a tease of an answer...I'm only saying this so > > > > > you know I do indeed do the research required and don't want others > > > > > to do my work for me but MAN I cannot find anything. Also, if any > > > > > Django contributors read this, Thank you for making such an amazing > > > > > framework!!!!!! > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "Django users" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to django...@googlegroups.com. > > > > To post to this group, send email to django...@googlegroups.com. > > > > Visit this group at https://groups.google.com/group/django-users. > > > > To view this discussion on the web visit > > > > https://groups.google.com/d/msgid/django-users/5aedce0e-870b-48ea-89cb-98e7b022d66d%40googlegroups.com > > > > > > > > (https://groups.google.com/d/msgid/django-users/5aedce0e-870b-48ea-89cb-98e7b022d66d%40googlegroups.com?utm_medium=email&utm_source=footer). > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to django-users+unsubscr...@googlegroups.com > > (mailto:django-users+unsubscr...@googlegroups.com). > > To post to this group, send email to django-users@googlegroups.com > > (mailto:django-users@googlegroups.com). > > Visit this group at https://groups.google.com/group/django-users. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/django-users/c7a62690-2a21-4add-8e6f-26ceb13b6b13%40googlegroups.com > > > > (https://groups.google.com/d/msgid/django-users/c7a62690-2a21-4add-8e6f-26ceb13b6b13%40googlegroups.com?utm_medium=email&utm_source=footer). > > For more options, visit https://groups.google.com/d/optout. > > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Django users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-users/eub2cwPxG1o/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > django-users+unsubscr...@googlegroups.com > (mailto:django-users+unsubscr...@googlegroups.com). > To post to this group, send email to django-users@googlegroups.com > (mailto:django-users@googlegroups.com). > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/CAL_q77KgmRKtL_qaUSD%3DUiCKfAXk2rbhivjYk3FJMqyUTfLCSQ%40mail.gmail.com > > (https://groups.google.com/d/msgid/django-users/CAL_q77KgmRKtL_qaUSD%3DUiCKfAXk2rbhivjYk3FJMqyUTfLCSQ%40mail.gmail.com?utm_medium=email&utm_source=footer). > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/AB762F2B-E1DC-4AEA-922B-604251020009%40getmailspring.com. For more options, visit https://groups.google.com/d/optout.
