Changes between Version 6 and Version 7 of TracFaq

Timestamp:

Aug 7, 2012, 10:09:18 AM (12 years ago)

Author:

Christian Boos

Comment:

… when you're still accessing old CSS files after an upgrade

TracFaq

@@ -54 +54 @@
 **A:** You most certainly forgot to stop and restart your server during an upgrade. The zip importer  mechanism keeps an internal cache which has trouble detecting replaced files, so a restart is needed (see TracUpgrade#ZipImportError). Do it now.
 
+==== Q: Trac /about says 1.0, but the style looks pre-1.0
+
+**A:** You probably just need to convince your browser that the CSS files have changed. Try "force reload" (`CTRL+R` or `CTRL+Shift+R`, depending on your browser). This is a common issue (see e.g. #10797).
+
+If that still doesn't work, look in your server configuration to see where the chrome files are supposed to be served from (`Alias` or `AliasMatch` directive), and maybe you'll see that you're serving them as static files from a different location:
+{{{
+Alias /trac/bct/chrome /packages/trac/virtualenv-0.13/share/htdocs
+}}}
+In this case, don't forget to:
+{{{
+$ trac-admin <yourenv> deploy /packages/trac/virtualenv-0.13/share
+}}}
+See TracUpgrade#a5.Refreshstaticresources.