Forum Discussion

ManuelKaptein's avatar
ManuelKaptein
Community Member
3 years ago

Browser cache issues after updating an Articulate course

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.

storyline 360
  • JoseTansengco's avatar
    JoseTansengco
    Staff
    3 years ago

    Hello Manuel, 

    Glad to help out!

    I'd like to ask a few questions to help clarify your experience: 

    • Have you tested the issue in SCORM Cloud? Testing the issue in another LMS is a great way to identify if it is something specific to your LMS. 
    • Does your LMS have the option to clear its cache before you upload a different version of your course? 
    • Does your LMS have course versioning enabled? This means that users who have already started a course will see an older version of you upload a new version while they are in the middle of taking your course. 
    • Are you able to replicate the behavior when you publish to Web or Review 360? 

    Looking forward to your response! 

  • ManuelKaptein's avatar
    ManuelKaptein
    Community Member
    3 years ago

    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.

  • Jürgen_Schoene_'s avatar
    Jürgen_Schoene_
    Community Member
    3 years ago

    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

     

     

  • VolkanDalyan's avatar
    VolkanDalyan
    Community Member
    2 years ago

    Hi Jurgen,

    Do you have any manual for how to do that changes?

    Regards

Related Content