On Monday, October 7, 2013 5:33:39 PM UTC+2, olemis wrote: > > On 9/25/13, Jingyu Li <[email protected] <javascript:>> wrote: > > We recently installed the most recent version of Trac to a different > > server. The pages that display ticket list and tickets are ugly now. I > > compared the source of http://trac.edgewall.org/report/1 with our > pages, > > found that ours do not have this attribute before </header>: > > > > <link rel="stylesheet" type="text/css" href=" > > http://www.edgewall.org/css/projects013.css"; /> > > > > AFAICT this is a custom theme for edgewall.org >
Edgewall runs some layout customizations for own use, not part of either default Trac or your Trac. It should not have anything to do with your problem > > Please advice me how to fix this problem. Thanks! > > > > It'd be useful if you could refresh your pages with Firebug activated > and report back if any .css downloads are in error , or anything else > weird that you might notice . > The most probably cause is serving old styles and javascript with a new code and templates. Other than browser (and proxy) caching, this can also arise if you at some stage ran 'deploy' to extract resources in order to have them served directly by web server (instead of serving through Python and Trac code). If not changed when updating code, your clients may still get old versions of css and javascript and more. In addition to looking for errors, also have a look at the source and make sure it actually matches the corresponding version stored in Trac repository. :::simon -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/groups/opt_out.
