I found a even better method.

I activated the fallback for modules menus in publications. Meaning if
you want to override the xhtml module menu then just place a file called
xhtml.xsp in {pub}/conf/menus/.

salu2

El lun, 07-11-2005 a las 13:33 +0100, Thorsten Scherler escribió:
> I attached a patch to
> http://issues.apache.org/bugzilla/show_bug.cgi?id=37380
> which shows what I mean.
> 
> If you think that is a good way then I will commit the patch.
> 
> salu2
> 
> El vie, 04-11-2005 a las 16:08 +0100, Thorsten Scherler escribió:
> > Hi all,
> > 
> > I was trying to create a custom menu.xsp for a doctype that only
> > contains a couple of entries, but constantly running into the problem
> > that through the menu aggregation in the global-sitemap.xmap I get as
> > well the menus from the modules.
> > 
> > How can I exclude the menus from the modules?
> > 
> > The way I found that are working are:
> > 1) remove the menu.xmap from the modules
> > 2) add your doctype specific stuff in the menus of the modules
> > 
> > Both way meaning that you have to modify core modules and that is not
> > really nice.
> > 
> > I found as well that one way to generate the menus is from the
> > publication.xconf. 
> > 
> > Maybe we should extend the match in global-sitemap and the corresponding
> > xsl to match the doctype and exclude menu entries that have something
> > like:
> > <module name="xhtml" exclude="homepage,..."/>
> > 
> > Then we can match in modules2xinclude.xsl 
> > <xsl:for-each select="module[not(contains($doctype,@exclude))]>
> > ...
> > </xsl:for-each>
> > 
> > wdyt?
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to