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.
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.
(in fact, i never use the default publication as a template in my custom
stuff, because i don't need all the DAV and BXE stuff that clutters the
default.)
--
Jörn Nettingsmeier
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
