Jörn Nettingsmeier schrieb:
Andreas Hartmann wrote:
Hi Lenya devs,
in a custom publication I'm facing the situation that I have to
override single pipelines from the default publication sitemap. Since
the pipelines are called using cocoon:/ (with a single slash), I can't
use the common pattern of mounting the default publication sitemap at
the end of my custom sitemap.
I think a quite convenient solution would be to mount a custom sitemap
at the beginning of the default publication sitemap:
<map:pipeline>
<map:select type="resource-exists">
<map:when test="{fallback:custom.xmap}">
<map:mount src="{fallback:custom.xmap}" pass-through="true"/>
</map:when>
</map:select>
</map:pipeline>
Maybe we can provide something like this in 2.0.1.
WDYT?
i don't like that. cruft and bad modularization should be cleaned up,
not painted over with another hook or layer of indirection. this is one
more thing that will make lenya mysterious for newbies.
OK, so how should this issue be addressed?
let's provide a real basic publication instead that doesn't have so much
cruft and can be used as a template for both the default and any custom
publication.
Hmmm - how would that solve the problem that I want to override single
pipelines? Or do you mean that the basic publication should be so basic
that it contains virtually no pipelines which could be worth overriding?
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
