Storyline and browser cache

Feb 25, 2020

I developed an animation with Storyline 3 which is read on the web, so with a browser. Variables are sent to the animation with the Storyline output/story_content/user.js file, as soon as it is opened:

var player = GetPlayer ();
player.SetVar ("JavaScript_Var_Nav", myvar1);
player.SetVar ("JavaScript_Var_Nav", myvar2);

These variables change with each session.
The exchange of variables with the animation works perfectly. Except that the browser does not take into account the last variables but those saved in the browser cache. For the browser to take into account the last variables, I must delete the cache (therefore the browsing history).
Have you ever faced this problem? Anyone have a solution other than manually clearing the cache by the user. Or how to force Storyline to take the variables from the user.js file?

Thanks for your help
Regards

7 Replies

Rick Cheeseman

over 3 years ago01/25/21 at 12:53 am (UTC)

I have a similar issue with frequently-evolving content and I posted a similar question a couple of months ago. Like you, I received no response.

Is this an issue that Articulate is avoiding?

If there is no way to make Storyline automatically look for a new version of a story, then it would be great if Articulate would please just say so and you and I can stop wondering.

(-:

Leslie McKerchie
Staff

3 years ago01/28/21 at 6:49 pm (UTC)

Hi Rick,

Thanks for bringing this back to our attention. I was also able to track down your original post here.

The conversation here by Dominique seems specific to his JS code, which is not supported by our team due to the custom nature.

In hindsight, we could perhaps be sure that he's using 'Never Resume' for his course.

For your question, the same article may be applicable. You mentioned setting the resume behavior on the last slide (which I assume was via slide properties), but not for the overall course.

Rick Cheeseman

3 years ago01/28/21 at 11:41 pm (UTC)

Hi Leslie,

Thanks for getting back to me. I have all slides set to Reset to Initial State and the Player set to Never Resume. However, Storyline still goes to the cached version. I suspect that there is no way to avoid this but hope springs eternal.

(-:

Rick

Leslie McKerchie
Staff

3 years ago02/03/21 at 4:02 pm (UTC)

Thanks, Rick.

With your permission, I'd like you to share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.

Volkan Dalyan

2 months ago03/12/24 at 6:52 am (UTC)

I have the same problem goes to the cached version. So users need to clear cache after every update otherwise slides look wierd.

Rick Cheeseman

2 months ago03/12/24 at 11:56 am (UTC)

hi Volkan – as a result of some ongoing tumult i don't think i ever followed up on Leslie's suggestion that I submit the project file. i have now done so and i just received a case #. i will share what comes from that in this thread. always the best, rick

Rick Cheeseman

1 month ago03/15/24 at 9:28 pm (UTC)

hello encore,

as usual, Articulate Support was quick and thorough in replying. here is their guidance on the caching issue:

"there isn't a feature in Storyline to clear the browser cache and ensure that the latest version of a course will load. If this is becoming problematic in your environment, a recommended approach is publishing a new version of the course and uploading that to your LMS/server separately from the earlier instance. That would allow learners to have a brand new link to access the new course, and they shouldn't run into any caching issues from the server."

c'est la vie.
(-:
may always the best be with us all, always.