Hi, yeah, I think Meta is fine.
Kind regards Juergen > -----Ursprüngliche Nachricht----- > Von: Ludwig Magnusson [mailto:[email protected]] > Gesendet: Montag, 12. Januar 2009 15:16 > An: 'Turbine Users List' > Betreff: RE: Skinning my app/working with css > > You da man Juergen! > Works now, thanks. > Sure I can post it... but where? > I'll put ut undet M.E.T.A if you don't say otherwise... > /L > > -----Original Message----- > From: Juergen Hoffmann [mailto:[email protected]] > Sent: den 12 januari 2009 15:05 > To: 'Turbine Users List' > Subject: AW: Skinning my app/working with css > > Hi Ludwig, > > go into your conf directory and find the web.xml there. Then find the > section > > <!-- > ======================================================================= > = --> > <!-- > --> > <!-- Make sure that templates, resources and logs are not available > through > --> > <!-- the servlet container. Remove security constraints or add an > authen- > --> > <!-- tication role if you need access to these paths. > --> > <!-- > --> > <!-- > ======================================================================= > = --> > > <security-constraint> > <web-resource-collection> > <web-resource-name>templates</web-resource-name> > <url-pattern>/templates/*</url-pattern> > </web-resource-collection> > <web-resource-collection> > <web-resource-name>logs</web-resource-name> > <url-pattern>/logs/*</url-pattern> > </web-resource-collection> > <web-resource-collection> > <web-resource-name>resources</web-resource-name> > <url-pattern>/resources/*</url-pattern> > </web-resource-collection> > <auth-constraint/> > </security-constraint> > > And remove > > <web-resource-collection> > <web-resource-name>resources</web-resource-name> > <url-pattern>/resources/*</url-pattern> > </web-resource-collection> > > From the security constraint. Could you please file a Bug report > against > JIRA, because IMHO this is a Bug although I know that this has reasons. > I > think we have to discuss this on the developers list further. > > Kind regards > > Juergen > > > -----Ursprüngliche Nachricht----- > > Von: Ludwig Magnusson [mailto:[email protected]] > > Gesendet: Montag, 12. Januar 2009 14:58 > > An: 'Turbine Users List' > > Betreff: RE: Skinning my app/working with css > > > > It is the one generated by M.E.T.A, I haven't touched it. > > Does it need to be configured? If so, where is this documented? > > /Ludwig > > > > -----Original Message----- > > From: Juergen Hoffmann [mailto:[email protected]] > > Sent: den 12 januari 2009 14:49 > > To: 'Turbine Users List' > > Subject: AW: Skinning my app/working with css > > > > Hi Ludwig, > > > > exactly. Could you post your web.xml? > > > > Kind regards > > > > Juergen > > > > > -----Ursprüngliche Nachricht----- > > > Von: Ludwig Magnusson [mailto:[email protected]] > > > Gesendet: Montag, 12. Januar 2009 14:44 > > > An: 'Turbine Users List' > > > Betreff: RE: Skinning my app/working with css > > > > > > No I didn't. I got a 403... > > > > > > URL: http://localhost/resources/ui/skins/blueprint/screen.css > > > Error message: > > > ------------------------ > > > HTTP Status 403 - Access to the requested resource has been denied > > > > > > type Status report > > > > > > message Access to the requested resource has been denied > > > > > > description Access to the specified resource (Access to the > requested > > > resource has been denied) has been forbidden. > > > Apache Tomcat/5.5.27 > > > ------------------------ > > > > > > Doesn't this mean that the server actually should be able to access > > the > > > file? > > > /Ludwig > > > > > > -----Original Message----- > > > From: Juergen Hoffmann [mailto:[email protected]] > > > Sent: den 12 januari 2009 14:05 > > > To: 'Turbine Users List' > > > Subject: AW: Skinning my app/working with css > > > > > > Hi Ludwig, > > > > > > can you copy the link from the <link> attribute inside your html > > source > > > code > > > and paste to your browsers Location Window and see if you get a > 404? > > > > > > Kind regards > > > > > > Juergen > > > > > > > -----Ursprüngliche Nachricht----- > > > > Von: Ludwig Magnusson [mailto:[email protected]] > > > > Gesendet: Montag, 12. Januar 2009 11:00 > > > > An: 'Turbine Users List' > > > > Betreff: Skinning my app/working with css > > > > > > > > Hello! > > > > > > > > I am trying to add some nice looks to my application. > > > > > > > > I have a dummy site written in html with css and now I want to > > > > integrate it > > > > into my functional turbine site. However, the app doesn't seem to > > > find > > > > the > > > > definitions for the div-tags. All the content of the site is just > > > > written on > > > > the screen with no formatting. But when I look at the source for > my > > > > page in > > > > my web browser, the generated page source looks exactly like the > > > dummy > > > > site. > > > > Ex, in the <head> tag of the document I find: > > > > > > > > > > > > <link rel="stylesheet" > > href="/resources/ui/skins/blueprint/skin.css" > > > > type="text/css" media="screen" title=""/> > > > > > > > > Which is generated by: > > > > > > > > > > > > > > $page.addStyleSheet($content.getURI("resources/ui/skins/blueprint/skin. > > > > css") > > > > ,"screen","","text/css") > > > > > > > > The path to skin.css is the correct one. > > > > Am I missing something? Does turbine not find the css-file? > > > > > > > > I have also been reading about the UIService > > > > (http://turbine.apache.org/turbine/turbine-2.3.3/services/ui- > > > > service.html) > > > > but I think it's pretty hard to understand what exactly that is > > > needed > > > > to > > > > get a skin working. An example would be nice. > > > > /Ludwig > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------- > -- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > ------------------------------------------------------------------- > -- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
