>> app/templates/{various top-level templates}
>> app/templates/help/help_base.html
>> app/templates/help/particular_help.html
>>
>> In particular_help.html I have to use
>>
>> {% extends "help/help_base.html" %}
>>
>> rather than a relative
>>
>> {% extends "help_base.html" %}
>
> Having a quick glance at the code, I'm not sure this can be easily
> simulated using a custom template tag, either. The difficulty is that
> although a template object carries it's own name around with it, it
> doesn't store the disk file location (in cases where that makes sense).
> So working out what directory to start from for a relative path search
> is not possible, as far as I can see, although I might be overlooking
> something.
Malcom,
Thanks for taking the time to dig into the right areas to uncover
possible difficulties with this. I hadn't considered templates
that weren't stored in non-files (possibly in either source-code
or in a DB) where "relative" and "filepath" are terms that don't
make a great deal of sense. For the time being, I'll stick with
fixed paths. Perhaps something for Django 2.0 ;)
Thanks again,
-tkc
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
