On Tuesday, May 24, 2016 at 8:48:07 PM UTC-7, Mike Dewhirst wrote:
>
> On 25/05/2016 1:25 PM, [email protected] wrote: 
> > But I did not act according to the configuration you provide links 
> > I have added two directory style file, but no action 
> > 
> > /home/projects/xxx/htdocs/style.css 
> > /usr/share/trac/htdocs/site/style.css 
> > 
> > | 
> > [root@host105 ~]# cat /usr/share/trac/htdocs/site/style.css 
> > #content.ticket { 
> > Â width: auto; 
> > Â max-width: 100%; 
> > } 
> > | 
> > 
>
> I'm sure that will work. But what will happen next time you upgrade Trac 
> if you forget you have done this? 
>
> To avoid problems of an update overwriting your good work you need to 
> contain your css changes completely in files which don't get 
> overwritten. You need your own css file and make your own site.html load 
> that css. 
>
> Mike 
>

Right. To expand on that, the pattern that should be followed is to place 
site.css in /home/project/xxx/htdocs and then run "trac-admin 
 /home/project/xxx deploy /usr/share/trac".

You can look at the page source, and if there's not a link for site.css, 
then the problem is with the site.html template:
https://trac.edgewall.org/wiki/TracInterfaceCustomization#SiteAppearance

If the link for site.css is present in the page source, but does not link 
to a site.css, then the problem is most likely with your web server not 
serving the static resource. Alternatively the static resource might not be 
in the expected location, due to failure to run the deploy command, but it 
sounds like you've ruled that out.

Make sure to restart your web server after making changes to site.css and 
running deploy, and also do a hard refresh on your web browser.

- Ryan


-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to