One could append a hash as a GET parameter to the CSS file in the head -
using a different hash when the CSS is updated. Or one could change the
name of the CSS file whenever it is updated.
Stack overflow has a good description of how one could achieve this in PHP:
What is an elegant way to force browsers to reload cached CSS/JS files
<http://stackoverflow.com/questions/118884/what-is-an-elegant-way-to-force-browsers-to-reload-cached-css-js-files/118886#118886>?
Or one could use mod_pagespeed
<https://code.google.com/p/modpagespeed/>, which can be configured to do
this automagically.
Mike
On 26/08/11 4:55 PM, Bruce Clement wrote:
On Fri, Aug 26, 2011 at 4:45 PM, Hans Recter <[email protected]
<mailto:[email protected]>> wrote:
Thanks for the help.
Clearing the cache got it going and I found a broken link in a css
file.
I'm glad that's all it was.
Hijacking the thread, cached CSS files seem to be a large source of
problems, how often do we see instructions in CMS and other web based
programs to force reloads after changing themes/templates/etc?
Is there any reasonable server-side way around this type of problem?
--
Bruce Clement
Home: http://www.clement.co.nz/
Twitter: http://twitter.com/Bruce_Clement
Directory: http://www.searchme.co.nz/
"Before attempting to create something new, it is vital to have a good
appreciation of everything that already exists in this field." Mikhail
Kalashnikov
--
NZ PHP Users Group: http://groups.google.com/group/nzphpug
To post, send email to [email protected]
To unsubscribe, send email to
[email protected]
--
NZ PHP Users Group: http://groups.google.com/group/nzphpug
To post, send email to [email protected]
To unsubscribe, send email to
[email protected]
