Re: [Fwd: Re: CSS for Publishing Screen]
Michael Wechner <[email protected]>
| Newsgroups | gmane.comp.cms.wyona.devel |
|---|---|
| Message-ID | <[email protected]> |
Andreas Hartmann wrote: > > ------------------------------------------------------------------------ > > Subject: > Re: [Wyonacms-dev] CSS for Publishing Screen > From: > Andreas Hartmann <[email protected]> > Date: > Wed, 08 Jan 2003 09:35:58 +0100 > To: > Michael Wechner <[email protected]> > > > Hi Michael, > > Michael Wechner wrote: > >> Hi >> >> I have just noticed that the "generic" publish screen includes >> a CSS wyona/css/default.css, which is within the following XSLT: >> >> src/webapp/wyona/cms/stylesheets/cms/Page/util/page-util.xsl >> >> The problem is that only the "unipublic" Publication has this CSS >> within the resources and therefore all other publications generate >> an "ugly" Resource not found exception within the log file. > > > This is my fault, when I created the utility stylesheet I forgot > to make the CSS available at a publication-independent URI. > >> >> I think what we could do is to create a pipeline within the top >> root sitemap (where the publications are mounted), which is matching >> generic stuff. The matching pattern could be something like: >> >> pattern="*/wyona/**" >> >> where the first star corresponds to the publication id. >> >> What do you think? > > > This sounds practicable, but implies more reserved > URI space within the publication. > > Maybe we should apply some kind of fallback-mechanism: > First, the publication CSS is used and when it is not available > the Wyona CSS is used. (I think I mentioned this too in the > mail about a publication-independent scheduler interface) > > We could use the URI > > /<pubid>/resources/css/default.css > > If this pattern is not matched within the publication sitemap, > it is matched at the end of the main sitemap with /*/resources ... > where the default CSS is provided. What do you think? > > To make it even more flexible, we could even think about > using publication-dependent / -independent XSLTs. Sounds good to me. I think Memo also suggested something similar (but I see that you have seen that already ;-) Michael > > Andreas > >> >> _______________________________________________ >> WyonaCMS-dev mailing list >> [email protected] >> http://mail.wyona.org/cgi-bin/mailman/listinfo/wyonacms-dev > > > >