"Marcin Soltysiak" <[EMAIL PROTECTED]> wrote: > > > |> One way to go (which we used at some point), is to > > > |> write all css in a page content. This way you could > > > |> call it with URL "/style.css" and all you need to do > > > |> is to create a page called "style.css" under root page. > > > | > > > | I can't seem to get this to work properly. > > > > > > Damn, I forgot... this used to work until Midgard 1.5.0... > > > We hit the wall with this issue at one of our clients > > > after they upgraded to 1.5.0. > > > > > > Could you try to delete the styles.css page and import > > > the same content as a text file attachment to root page? > > > (This used to work too...) > > > > Afraid this doesn't seem to work either. If anyone has more suggestions > > please let me know. Otherwise I give up. Personally I'll be keeping the > > CSS in the file system outside Midgard. > > This DO WORK on any midgard since I always do it this way. Create /style.css > page under root, assing empty style and put content: >
BTW, maybe this is known issue , but I discovered it last times though :) There were thread about serving pdf attachments with wrong header. I had similiar problems with css, images and pdf as well. For all pages like style.css, attachments etc it is enough to create empty inheritable code-global o code-init element to have clean headers, if You used to send cookie or any other headers in code-global for the root page. Of course empty style is mandatory. Piotras --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
