> > You can use both schemes.
>
> Defaults in app/templates, overrides of defaults in project/templates.
You want to use both places to store templates?
Look at TEMPLATE_LOADERS:
TEMPLATE_LOADERS = (
'django.template.loaders.filesystem.load_tem
On 20 March 2010 12:48, <reg...@messir.net> wrote:
> You can use both schemes.
Defaults in app/templates, overrides of defaults in project/templates.
HM
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to thi
You can use both schemes.
> Is there any reason to have a global directory with all templates
> instead of to have the templates for each application:
>
> project/
> \___ apps/
> \___ templates/
>
--
You received this message because you are subscribed to the Google Groups
"Django
django-developers is for the discussion of the development of Django
itself, not development with Django.
As such this mailing list is not appropriate for this message,
django-users would be more appropriate.
But to quickly answer, yes. Especially if you're using many 3rd party apps.
-- Gert
Is there any reason to have a global directory with all templates
instead of to have the templates for each application:
project/
\___ apps/
\___ templates/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send
