Re: from django.contrib.auth.views import login

hi, instead of from django.contrib.auth.views import login you need to use from django.contrib.auth import login regards. On Sat, Jul 7, 2018 at 6:41 AM, Ahmad wrote: > hello everyone, > > when i import this line it's not working. > from django.contrib.auth.views import

Re: from django.contrib.auth.views import login

you want LoginView https://docs.djangoproject.com/en/2.0/topics/auth/default/#django.contrib.auth.views.LoginView On Saturday, July 7, 2018 at 7:42:53 AM UTC-4, Ahmad wrote: > > hello everyone, > > when i import this line it's not working. > from django.contrib.auth.views impo

from django.contrib.auth.views import login

hello everyone, when i import this line it's not working. from django.contrib.auth.views import login My Django Versions is 2.0 from django.conf.urls import url from . import views from django.contrib.auth.views import login urlpatterns = [ url(r'^$',views.home), url(r'^login

Re: How to use password_change function from django.contrib.auth.views

You need a url() with name='password_change_done' -- instead you wrote 'change_password_done'. On Monday, June 27, 2016 at 11:39:23 AM UTC-4, Juan Sebastian Avila Rodriguez wrote: > > I tried to implement the password_change view but is not working. I only > add the code below to the urls.py:

How to use password_change function from django.contrib.auth.views

I tried to implement the password_change view but is not working. I only add the code below to the urls.py: from django.contrib.auth import views as auth_views ... url( r'^change-password/$', auth_views.password_change, name='change_password' ), url(

Re: Why is there no view for sign up in django.contrib.auth.views?

Russell, I disagree. You say that logging in has constant requirements but it doesn't. Some applications will require a username and a password, others will require an email address and a password, others will have some sort of captcha, others will have 2-factor authentication... So logging

Re: Why is there no view for sign up in django.contrib.auth.views?

On Sat, Apr 6, 2013 at 8:40 AM, Cody Scott wrote: > If I want users to sign up for my site, I need to make a register view, > register form and a register template. > > Why is there a view and form for every other user account action (login, > logout, etc.) > > Logging

Why is there no view for sign up in django.contrib.auth.views?

If I want users to sign up for my site, I need to make a register view, register form and a register template. Why is there a view and form for every other user account action (login, logout, etc.) -- You received this message because you are subscribed to the Google Groups "Django users"

TEMPLATE_CONTEXT_PROCESSORS and request context in django.contrib.auth.views

I'm using django.contrib.auth.views for user management like login wrapped in my own views for example: @login_required def password_change(request): return django.contrib.auth.views.password_change(request, template_name='userpanel/password_change.html') But my template context

Re: django.contrib.auth.views

On 6/27/07, rycole <[EMAIL PROTECTED]> wrote: > Or, will these views stay backwards compatible through > future versions? These views provided by auth are exactly what I need, > but I don't want to use them if I will need to change stuff later. Any > ideas? I'm pretty sure they'll be updated to

django.contrib.auth.views

I'm beginning a site with Django, and am starting with the fundamental elements of the site first. I figured I'd get the user login / registration working before I do anything. Should I still use django.contrib.auth.views for login, logout, etc, even though they use oldforms? Or, will these views

use of template_loader in django.contrib.auth.views

Hi all, Would there be any interest in a patch to make the views in django.contrib.auth.views accept a template_loader argument, like the generic views do? I'll probably be using this to have the login page rendered from a Breve [0] template. Or are there any other, cleverer ways to do