>
> > On Dec 29 2007, 11:03 am, Alex Koshelev <[EMAIL PROTECTED]> wrote:
> > > Is there 'django.contrib.auth.middleware.AuthenticationMiddleware' in
> > > your MIDDLEWARE_CLASSES ?
>
> > No. Uncommenting
> > 'django.middleware.common.CommonMiddleware',
> > 'django.contrib.sessions.middleware.SessionMiddleware',
> > 'django.contrib.auth.middleware.AuthenticationMiddleware',
> > in the distribution settings file was progress, resulting in a
> > complaint about no login.html file.
>
> Going from the online version of the book, this was included in Step 3 here:
>
> http://www.djangobook.com/en/1.0/chapter06/
A search of chapter06 for MIDDLEWARE_CLASSES turns up only the
following sentence:
Also uncomment all the lines in the MIDDLEWARE_CLASSES setting tuple
and delete the TEMPLATE_CONTEXT_PROCESSOR setting to allow it to take
the default values again.
>From this I concluded that other stuff didnt' need to be uncommented.
I guess there's more there or elsewhere in the chapter than I
understand.
> ("Also uncomment all the lines in the MIDDLEWARE_CLASSES setting tuple...")
>
> Copying django/controb/admin/templates/admin/ to templates fixed that
Both fixed, simplifying my setup and perhaps avoiding future trouble.
Thanks.
Rereading chapter06 on template directories I see that if I'd looked
carefully at the commented-out lines in the initial settings file I
could have deduced that uncommenting was the way to go. But a more
straightforward reading of chapter06 could easily convince a newby
that the directory copy I did instead as the way to go.
> > and it works now.
>
> You should not have had to copy the admin templates anywhere, if the app
> template loader ( '
> django.template.loaders.app_directories.load_template_source') is listed in
> TEMPLATE_LOADERS. I thought it was there by default -- was it not in your
> case?
>
> The generally excellent book indicates only a few of the changes
>
> > necessary to enable the admin system.
>
> Near as I can tell (working from the online version), the book does cover
> all that needs to be done to enable admin. Nevertheless it seems like I've
> seen a lot of people post here with trouble in this area, so I'm trying to
> understand why. Perhaps step 3 in Chapter 6 should be more specific (list
> exactly what should be in MIDDLEWARE_CLASSES), or split into two steps,
> since it covers both ensuring that INSTALLED_APPS and MIDDLEWARE_CLASSES are
> set properly. But even that wouldn't address whatever caused you to have to
> copy the templates -- I don't understand what happened there.
If chapter 6, and doubtless some others, were more explicit it would
help. I've seen related comments on this site. In some cases
(especially databases) there are system variations and changes that
would make this degree of explicitness impractical and even
counterproductive, but that doesn't seem to be the case in this
chapter. Just trying to be helpful in convening the newbe perspective.
The very good news for this newbe, anyway, is that this mailing list
has been very responsible with helpful fixes.
Chris
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
