My INSTALLED_APPS looks like this currently.
Note that I did not have this same problem before, when I was using
Django 1.2. I recently upgraded to Django 1.3. Could this be part of
the problem?
The only other difference between now and then is that I used to have
the entries for contrib.auth and such in the INSTALLED_APPS, but
commented out. I don't see how this could affect my current situation
though, so my guess is, something changed in Django 1.3. Can anyone
confirm or deny this? I didn't see anything different in the
documentation.
INSTALLED_APPS = (
'django.contrib.sessions',
'form_utils',
'org',
'auth',
'entities',
)
On 31 mrt, 13:07, Daniel Roseman <dan...@roseman.org.uk> wrote:
> On Thursday, March 31, 2011 10:10:27 AM UTC+1, sanderkrause wrote:
>
> > Because I'm using my own authentication and authorization system, I
> > would like to completely disable these standard apps from Django.
>
> > I've tried removing the relevant lines from MIDDLEWARE_CLASSES and
> > INSTALLED_APPS, but when I use the syncdb command, the default tables
> > that come with the default authentication system are still being
> > created. Is there a way to prevent this from happening?
>
> > Is there maybe another setting that I'm overlooking? Other possible
> > variables that could cause these standard apps to be enabled despite
> > my efforts?
>
> > I also don't use the built-in admin system, so I don't think that
> > could be a problem.
>
> > Any hints?
>
> The only reason syncdb would create the user tables is if contrib.auth is in
> INSTALLED_APPS. Can you post that?
> --
> DR.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
