#18617: Pointing out a template overriding pitfall
-------------------------------+--------------------
Reporter: EvilDMP | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.4
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
I spent a lot of time trying to work out why my own base_site.html
template wasn't overriding Django's.
Eventually I realised that it was because django.contrib.admin was listed
in INSTALLED_APPLICATIONS before my own application, and so its
base_site.html won the race to be chosen.
I'm a slow learner, so I went through the same thing all over again today,
a year or more later...
To help people like me, I have added a comment in the settings.py of the
project template, and a note in the docs, in a pull request at
https://github.com/django/django/pull/185
--
Ticket URL: <https://code.djangoproject.com/ticket/18617>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en.
