Saving Course Progress - Web Publish After An Update
Mar 10, 2016
So I know that SL uses Flash cookies to save progress on web output projects, and the progress is saved just fine in most instances. However, I have a client who has files that will require occasional updates (sometimes very minor items, such as link changes, that don't affect the substantive content), and this ruins the whole thing.
The meta file that is created has a project id, courseid, and other identifying files, but I can't manipulate these sufficiently to "trick" the system. I've even tried copying the entire meta file from the previous file (where progress was save) to a new updated upload and it started from the beginning.
The issue is that this project has several chapters per module, and each individual module is 30+ minutes with locked navigation (don't get me started on that). If a user stops in the middle, it'll be very irritating to have to start over, obviously. They are deploying via web for now, and LMS later, but they would like both to work.
I know any solution is just a workaround, but has anyone been able to get this to work?
3 Replies
Hi Rich,
Are you editing the published output files to do so? If so, that's not something that we can offer support for but perhaps someone in the community can weigh in on your set up here. We would recommend making the changes in the .story file and then publishing again to upload to your LMS/web server. This will count as a new version though and not save the progress where the user left off.
Ashley,
We are making the changes in SL and then republishing, and we know that the progress is not being saved. I need to go ahead and put in a feature request, I know, but I am curious as to why the information is in the meta file to begin with. Is it just generated regardless of output type and then ignored for web?
Is there anyone that can let me know where the information that is used to create the Flash cookie is generated, since that's obviously resetting upon a new upload?
Hi Rich,
It's not something that I could answer in terms of the meta file as I'm not a part of our engineering/development team - but if you're republishing and not just looking to make the modifications of the published output - I suspect it's overwritting your previous course and therefore the Flash cookie is being regenerated as a part of the web browser looking at a brand new file.
This discussion is closed. You can start a new discussion or contact Articulate Support.