Pointing out a template overriding pitfall

[Daniele Procida]

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

[Aymeric Augustin]

Yes, it's worth highlighting why the order of INSTALLED_APPS matters.

Other resolution mechanisms depend on the order of INSTALLED_APPS (static assets collection for example) and I don't feel like listing them in the default settings.py.

The pull request also contains a stray commit. I'll just take the patch to the template docs and commit it.

[Aymeric Augustin <aymeric.augustin@…>]

In [8c670ee34714acffbc64e5cafd1e664fb8341a37]:

Fixed #18617 -- Highlighted that the app_directories template loader depends on the order of INSTALLED_APPS.

Thanks evildmp for the patch.

[Daniele Procida]

Thanks Aymeric - should I mark the pull request closed on GitHub, so it doesn't cause pollution?

[Aymeric Augustin]

Yes, I've just closed it (I forgot when I committed the patch).