By extexan on

On a recently upgraded client's site (live site), we are having a problem with css modifications not getting refreshed. Each time I make a change and my client tries it, he sees it the old way until he clears his browser cache and refreshes the page. I've tried with caching turned on and with it turned off in Drupal - same result.

I was told that Drupal adds a unique number to the end of the css/js file names to ensure that they are loaded fresh each time. Is that true? If so, I'm not seeing that when I look "under the hood" using Firebug. Is that done with caching ON or OFF? ...not that that matters, coz I've tried it both ways.

My client says he can't expect all users who have visited his site before we made changes to automatically know they need to clear their local browser cache and refresh the various pages they visit - and he's absolutely right. Can anyone offer a solution?

⋅ Categories: Drupal 6.x

Comments

extexan’s picture

extexan commented

Anyone have any feedback on this issue?... I'm really at a loss as to what to try next.

It's never too late to have a happy childhood. ;-)

sapark’s picture

sapark commented

I have the exact same problem.

I've tried shortening the expires date from 2 weeks to 1 day in /var/www/html/[site]/.htaccess and it didn't seem to help. http://httpd.apache.org/docs/2.1/mod/mod_expires.html

# Cache all files for 2 weeks after access (A).
#ExpiresDefault A1209600
# Cache all files for 1 day after access (A).
ExpiresDefault A86400
sapark’s picture

sapark commented

It turns out the views argument I was using didn't return anything the first time the person visited the page, or whenever the page was viewed through a proxy. Set it to a default and everything works now.