I think I missed a part <body onload="alert('onload');" onunload="">
StackOverflow - This is because the browser assumes the page is uncacheable if it has a onunload handler (the page has already destroyed everything; why cache it?)
Re: Workaround so site viewers don't need to clear cache on update?
I think I missed a part <body onload="alert('onload');" onunload="">
StackOverflow - This is because the browser assumes the page is uncacheable if it has a onunload handler (the page has already destroyed everything; why cache it?)
Member
Re: Workaround so site viewers don't need to clear cache on update?
Ah, if the stack overflow comment is true, that's interesting, though I wonder if it just applies to the page HTML and not the content?
Anyway, good spot.
Member
Re: Workaround so site viewers don't need to clear cache on update?
Unfortunately, my server will only accept secure FTP sessions, so I can't take advantage of the built in FTP tool - but thanks for the tip though!Originally Posted by Drwyd
Xara Group Ltd Developer
Re: Workaround so site viewers don't need to clear cache on update?
You should not have this problem if you export the HTML properly.
It's really important that you export into the same folder every time. That allows the program to see what the old graphics names were and to avoid them so that the new HTML never refers to graphics that might be in people's browser caches.
Phil
Member
Re: Workaround so site viewers don't need to clear cache on update?
Cool, thanks Phil.
Member
Re: Workaround so site viewers don't need to clear cache on update?
I am exporting to the same folder every time of course,
The problem goes away after a while but not if the viewer loads the page soon after the page has been re-uploaded.
I will need to update the site tomorrow night so I will see if I can reproduce an image, I will make sure to have 'Export changed files only' is ticked as well.
Posting Permissions
Reply With Quote
Bookmarks