On Mon, May 3, 2010 at 3:01 PM, Remy Blank <[email protected]> wrote:
> Simon Martin wrote:
>> I don't now why, but the error disappeared after a few restarts of
>> tracd.
>
> This is likely due to the browser caching the Trac CSS. I have seen
> similar effects that went away with a Shift+reload.
>
> Maybe we should add a comment to that effect on TracUpgrade? Or is there
> a way to force a reload of the CSS on upgrade?
>
I am not sure , but I suppose that if a timestamp (e.g. CSS | EGG file
creation time) is sent back to the client when requesting static
resources then the browser should notice that there's a new file in
the server and reload it into its own cache
BTW:
- Does anybody know if Trac (AFAICR Chrome component)
sends such headers back to the client ?
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
[svn r7916] XmlRpcPlugin: Pluggable protocols through new API + rework
of most request-handling internals. Bump version to 1.1.0. Closes
#5437. Big thanks to Olemis Lang for getting this completed. -
http://bitbucket.org/osimons/trac-rpc/changeset/1c8f489fbfb1
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en.
