Re: Multiple implementations of django's authentication/authorization system

On Sep 16, 1:55 pm, Chris Babcock wrote: > Is there any particular reason to maintain two distinct authentication > databases? You could sub-class the Django auth models and deploy your > subclass in parallel, but that is not a trivial deployment task. It > would be

Multiple implementations of django's authentication/authorization system

Hi, Is there a way to have multiple implementations of django's authentication/authorization system? In my practice blog-type site, I've implemented django's auth/auth system as is. I'd like to use the default implementation solely for administrators of the site. For users of the site, on the

Context object not completely rendering

Hi, Below is a function I created in my views.py file and its accompanying template file. For some reason, the second Name-Value Pair i.e. 'section':'General Info' does not render in the respective template file. Anyone know what is wrong? Thanks. def lookup(request, first_name, last_name):

Deploying with Apache: confused by odd PythonPath requirement

I've 'successfully' deployed django in a development environment on Apache2. While, I've got it to work, I'm thoroughly confused by the PythonPath setting needed for it to work. I don't understand why I need to give the directory that contains the django 'project' AND the directory that contains

Couple of basic Django questions

I'm in the process of deciding between learning/using django and rails. I've already made a simple site in rails, and now I'm in the process of doing the same with django. However, there are a couple of points I'm stuck on: 1. Is there supposed to be only one 'view' (controller) file per