When I upload a new version of the document, I have some garbled images until I clear the cache.

Question

When I need to upload a new version of my file, I will delete the old version on my web server, and upload a new clean version. Sometimes this results in garbled images online. I tried the information from this question, but that didn't help. I'm running in5 3.8.3, and this is happening on Firefox 100.0 for mac. Also on Safari 15.4.

I can't expect my client to clear their cache everytime I reupload files. What is the solution here?

This is 3 separate elements: a line and two text boxes. They've moved completely out of place.

Answer 1

Try updating to the latest version of in5 which is currently version 3.8.7 and re-exporting your content. Make sure that when you upload the newly exported files that you include the latest in5.serviceworker.js that gets exported.

If you continue to have issues with your content, would you be able to send us your html5_output to troubleshoot? You can send it here:

https://ajarproductions.com/pages/contact.php

Comments

Hi Myra, we have this issue too, so much so that we have resorted to changing the folder name every time we upload a new version. We are on version 3.8.7 but I don't see a 'in5.serviceworker.js' file in the assets/js folder. Should I use the instructions from the previous post to create it instead?

---

Are you exporting a web app? The in5.serviceworker.js file should be created when you export a web app but not with other types of Output. The in5.serviceworker.js file is not in the assets/js folder. When you export a web app, it would be at the same level as the index.html file.

Instead of changing the folder name, you could try adding a query string. Here's how:

• Viewing Uncached Content While Testing

---

I see, no, we're not doing web apps. I like the query string idea, I will look into that, thanks!!

---

Ah, that makes sense for the missing file.

Sounds good on trying out the query string. :)

---

Hi Myra! I have the same problem (in5 version 3.8.8 | Output: Web | Format: Continuos Scroll vertical). Unfortunately, the query-string solution is not an option in my case, since the links have already been sent and I now need to upload revised versions that must be accessible via the same links. I already tried to force a hard reload via .htaccess and the header in the index files. Unfortunately without success. How can I ensure that there is no incorrect display when uploading the new version? Thank you very much for your help and have a nice day =)

---

I checked with Justin for any additional recommendations. He said that he uses the following method a lot for testing:

• How to Completely Disable Cache in Google Chrome

---

This is helpful, thanks Myra! For clients it seems that the cache thing is unpredictable enough that new URLs is just something they will have to understand. The query string solution appears to be the most elegant solution for that. The problem MultimediaAgentur refers to is still an issue though, wish there was some way to add something to the head of the HTML file that ensures no caching.

---

Server-side code could work to prevent caching, but it's a little more complicated. If you're comfortable trying it, and the code is correctly written in a language that matches your server, then it should work.

---

Myra, I wrote this original question, and am still having this issue. I'm running In5 3.8.17 and exporting as web, horizontal slider (though I've also had this happen with flipbooks). Is there a snippet of code I can add to my header (or a bit of js?) that forces the server to not load a cached version of the page? Thank you.

---

I can recommend the link that Justin suggested:

• https://www.technipages.com/google-chrome-how-to-completely-disable-cache/

or test using a query string:

• https://ajar.freshdesk.com/support/solutions/articles/26000037613-viewing-uncached-content-while-testing

You could also rename the html5_output folder and upload it with your content. When uploaded, that folder becomes a directory and part of the URL. This approach is similar to the query string in that it creates a unique URL. It wouldn't work for content that you're replacing.

If you need custom server side scripting to clear the cache, then I would recommend reaching out to a web developer.