Re: Browser Refresh Issues
Quote:
Originally Posted by
behzad
Clients always complaining that after an update their browser does not show the changes. I tell them to press F5 to refresh. But I believe this is a Xara issue. This has been an issue even for myself with Chrome and other browsers.
Also check my other post on the same issue with Apples Safari Browser.
behzed, in a heavy development phase, I might force all fetches back to the server using META statements in the website head code section:
Quote:
<meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" />
<meta http-equiv="Pragma" content="no-cache" />
<meta http-equiv="Expires" content="0" />
A useful approach is to have a Latest changes page and have it no caching so you can inform your client and client's customers that a Refresh might be useful.
When things are quieter, setting expiry dates might be useful to say 30 days.
You could spice things up a bit with a Page Modified block.
Website body code:
Quote:
<script> document.getElementById("dateLastModified").innerH TML = document.lastModified;
</script>
Placeholder body code:
Quote:
<div id="dateLastModified">Date</div>
.
I am sure the modifiedDate of a page in a website could be interrogated by other pages to force an update to them.
The problem is the one I know about is deprecated and only was for SSL sites. Automatic purging of a user's cache might not be appreciated.
Acorn
Re: Browser Refresh Issues
Thank you, will try those. Appreciate your help as always.