Thorsten Scherler wrote:
El jue, 19-01-2006 a las 11:29 +0100, Felix Röthenbacher escribió:
Thorsten Scherler wrote:
...
Were else the locationmap let the *user* define the location and the
"to-be-used" fallbacks:
<match pattern="tabs.xml">
<select type="exists">
<location src="{project:content.xdocs}tabs1.xml"/>
<location src="{project:content.xdocs}tabs2.xml"/>
</select>
</match>
...
Can you give an example how Lenya's templating hierarchy will look like
implemented with the locationmap protocol?
Thanks, Felix
I will try but no guarantee that it is correct, since I could not find
any documentation about fallback in our official docu (hint, hint). ;-)
<match pattern="fallback.**">
<select type="exists">
<location src="context://{lenya:pubId}/lenya/**"/>
<location src="context://{lenya:pubId}/**"/>
<location src="context://lenya/**"/>
<location src="context://**"/>
</select>
</match>
How do you implement a recursive dependency of publications like
pubA <-- pubB <-- pubC <-- pubD
so that a resource not found in pubD is taken from one of its parents?
What are the prerequesites for configuring the templating hierarchy?
- Felix
I guess that is the basic rule, right?
The interesting is that a user can extend this default matches
(see other mail why and when).
salu2
--
Felix Röthenbacher [EMAIL PROTECTED]
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
