On Mar 24, 12:42 am, Malcolm Tredinnick <malc...@pointy-stick.com>
wrote:
> On Mon, 2009-03-23 at 17:21 +0000, Colm Dougan wrote:
>
>
> There is, however, no concept of "context" passed through to the
> template loader. Everything is loaded from the same base situation,
> which is what I believe your question is asking. The relevant code is in
> django/template/loader_tags.py.
I understand. Apologies for my sloppy terminology wrt. "document
root". I just meant "the templates folder" Unfortunately I don't
know python so just to make sure I'm clear, I'm going to restate my
question based on what you have said.
Assuming I had only one app called "foo_app" and my templates were
laid out as follows :
foo_app/template/template1
foo_app/template/path1/template2
foo_app/template/path2/template3
Assuming foo_app/template/template1 looks like this :
{% include "path1/temtlate2" %}
If template2 wants to include template3 should it do this :
{ % include "../path2/template3" %}
OR this :
{% include "path2/template3" %}
>From what you have said I'm gathering it is the latter. Is that
correct?
Also, is the former idiom (the use of "..") meaningful at all when
evaluating includes and if so what does it mean? If it is meaningful
at all does it mean "relative to the templates directory"? i.e. if I
had :
templates/foo
otherstuff/blah
.. could I include "blah" by saying {% include "../otherstuff/blah"
%}. Or does that not make sense?
Thanks,
Colm
--~--~---------~--~----~------------~-------~--~----~
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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
