Thanks for your reply, but now that I've read up on custom profile and
permissions, it doesn't seem like a solution.
Here's another way of explaining it: in my urls.py file, I have two
entries inside the urlpatterns definition, like this:
(r'^dashboard/', include('mysite.console.urls')),
(r'^console/', include('mysite.console.urls')),
And then inside the /dashboard/urls.py file I have this:
urlpatterns = patterns('',
(r'^login/$',
'django.contrib.auth.views.login',
{'template_name': 'dashboard/login.html'}),
[etc]
)
And inside /console/urls.py is this:
urlpatterns = patterns('',
(r'^login/$',
'django.contrib.auth.views.login',
{'template_name': 'console/login.html'}),
[etc]
)
Basically, since /console and /dashboard provide different
functionality to different types of users, they have different
templates (and their db model definitions are quite different; /
dashboard users are not a type of /console user, nor can they really
be both inherited from the same user profile class).
So, ideally, what I'd like to be able to do is something like this, to
force the built-in authentication to use a different url than the
single LOGIN_URL specified in settings.py:
urlpatterns = patterns('',
(r'^login/$',
'django.contrib.auth.views.login',
{'template_name': 'dashboard/login.html', LOGIN_URL='/dashboard/
accounts/'}),
[etc]
}
and:
urlpatterns = patterns('',
(r'^login/$',
'django.contrib.auth.views.login',
{'template_name': 'console/login.html', LOGIN_URL='/console/
profile/'}),
[etc]
}
Is there a way to do that?
On Jul 21, 9:23 pm, Andre Terra <[email protected]> wrote:
> Why not make custom user profiles and write permission checks on your views?
>
> Cheers,
> AT
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
