I have directories that map to url space, but the directories contain
templates that are just content and WRAPPERs are used to build the
full HTML page.
So, say the directory is docroot/info/policy/. Imagine a template
named "index.html" that includes:
PROCESS page_content;
PROCESS footer;
...
BLOCK footer;
'<p>footer</p>';
END;
Now later I need to add more pages in that policy directory, but I
want them all to share that footer.
If I want to keep all those related files in the same directory,
including the new separate footer template I have to change to:
PROCESS info/policy/footer;
It would be somewhat handy if simply "PROCESS footer" would also look in the
current directory. That is, the current template's directory is
shifted onto INCLUDE_PATH.
Of course, would not want web users to be able to access
/info/policy/footer directly. So might need to do other ugly magic
like name it _footer and test for underscore when calling process.
Basically, I'm trying to figure out how to let the person that
manages the "policy" directory setup a library of templates, yet keep
all their templates (and included templates) in one place.
Any suggestions?
--
Bill Moseley
[EMAIL PROTECTED]
_______________________________________________
templates mailing list
[email protected]
http://lists.template-toolkit.org/mailman/listinfo/templates
