On a related note, the admin login screen doesn't seem to be willing to redirect users to a "next" destination outside the admin app, which means having two separate login screens for different purposes, which doesn't make any sense at all.
On Sep 10, 5:12 pm, ringemup <[email protected]> wrote: > I'm a little frustrated trying to set up logins for my site. Using > @permission_required, if a user is already logged in but doesn't have > sufficient permissions for a particular view, they just get redirected > to the login form, with no explanation. > > I can set up a custom login view that will give the user to a > "permission denied" page if they're already logged in or redirect them > to the login screen otherwise. > > However, due to the way that admin handles logins there's still no way > to give the user a useful error message if they try to log into the > admin and log into the site successfully but don't have permission to > use the admin at all. Any suggestions? -- 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.
