Browser cache issues after updating an Articulate course
Oct 07, 2022
I've built an Articulate Storyline course that I now and then update. When I update the course I completely delete the folder with the course on the server and then upload the new files that I published with Articulate Storyline.
What subsequently happens quite often (even days after the update) is that users report technical issues. I think their browser still has the old version partially in its cache memory and this causes conflicts with the updated version on the server. After the user does a hard refresh, the issues they reported are gone.
How can/should I prevent this problem from happening? I understand I could give the folder on the server with the updated version a new name, but that would require me to implement changes to my LMS everytime I do an update.
5 Replies
Hello Manuel,
Glad to help out!
I'd like to ask a few questions to help clarify your experience:
Looking forward to your response!
Thanks Joe,
I'm just uploading the SCORM 1.2 output/folder from Articulate as html/Javascript files onto a server. So, independent of the LMS.
The course loads by including on a page: `<iframe id="scorm" src="/folder-path/story.html"></iframe>`
P.S. I use LearnDash LMS.
I can clear the cache there, but as expected, that makes no difference.
No course versioning is being used.
you have two options
- add an dynamic parameter (time) to "/folder-path/story.html"
or
- change the web server configuration for ".html", ".js" and ".css" -> max-age, expires
Thanks Jurgen!
Hi Jurgen,
Do you have any manual for how to do that changes?
Regards