Hi, I haven't used allauth specifically, but you can always do things like this:
1. Override the default templates by including your templates first. That way you will only get the functionality that your templates add. See here : https://docs.djangoproject.com/en/2.0/howto/overriding-templates/ and here: https://stackoverflow.com/questions/37439153/django-auth-where-to-put-custom-templates 2. You can only add the views that you need from the all auth package. If you check through the all auth package you will find a urls.py somewhere. Only add the views that you require for your project and you should be fine. Regards, Andréas 2018-01-02 22:13 GMT+01:00 Fun. Bytes <funbyte...@gmail.com>: > I have a set of expectations I'm trying to achieve. I want a sign up, > login, and forget password page. I also want to have social sign in using > Twitter, Facebook, or Google. Another thing I want is to send a > confirmation email to the user validating their account. > > I know I can do this with Django allauth, but allauth comes with extra > features that I don't need. For example, I don't need the password reset > and change email pages. I want to remove these pages and their > corresponding functionality, but I'm afraid I might break the code if I do > this. > > I was thinking about two solutions. One solution would be to go through > the allauth templates and change some of the code to fit my specifications, > but I feel like it would be very tedious because a lot of things might > break if I remove some funcionality. > > The second solution I was thinking of doing was building on top of auth > and using a custom User model and building custom login, sign up, and reset > pages. Adding the required functionality and everything. I could also build > the models to provide social login by copying allauth's templates. I am > just debating on what would be the best possible choice to do this. I would > be happy if anyone can point me in the right direction. > > -- > 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/5f49ce0c-9f85-4e23-a44d-2ebbe08f1695%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/5f49ce0c-9f85-4e23-a44d-2ebbe08f1695%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. 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/CAK4qSCc%2B2E6DbVn1WbA1XXwktr0YbM%3Daf2xX-a%3DiPHGYTVU0Gg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
