Re: Argh: templates, admin, and app loading order

Hm, yes, that might work, although at this point I'm a little
concerned about changing the order of applications anyway, since I'm
not sure what other side effects it might have. Mostly I'm
uncomfortable with how important application order ends up being to
how one's project operates, especially given that the behavior is
inconsistent for different aspects of the framework.

Is there any way to force the third party app's admin.register() calls
to execute before running my own -- e.g. by importing thirdparty.admin
at the top of my admin.py?

On Aug 30, 5:51 pm, Doug Ballance <dball...@gmail.com> wrote:
> Can you use the filesystem loader as the first template loader, then
> set TEMPLATE_DIRS in settings.py to specify a template directory
> outside any app?  Use this location for all of your overrides, just
> make sure the path is right... ie each app you override would have its
> own subdirectory.

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.