OK, so it sounds like the default would be to use the normal auth
system.
Are there any tips on doing things like member lists and such as part
of the public website for logged in users. Can I just tie into the
existing Users model?
--~--~-~--~~~---~--~~
You rec
On 5/26/06, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> I've built a small website for a club with Django trunk so far and it's
> working very well. I'm ready to start thinking about member management
> -- user account creation, logins, member list and details pages, etc.
>
> IIRC, there was some m
On 5/26/06, Rob Hudson <[EMAIL PROTECTED]> wrote:
> IIRC, there was some mention of a new auth system. Is the auth system
> documented here:
The multi-auth branch, currently under development, is meant to make
it easier to drop in something other than the Django auth database for
authentication
I've built a small website for a club with Django trunk so far and it's
working very well. I'm ready to start thinking about member management
-- user account creation, logins, member list and details pages, etc.
IIRC, there was some mention of a new auth system. Is the auth system
documented h
4 matches
Mail list logo
