I have a problem that quite frankly don't know if it's even a Moodle issue. We use Moodle 2.1.3+ and Articulate to create our SCORM modules for Moodle. At times, people complain that they can't launch the course. The first thing I have them try is to clear their browser's cache. That seems to fix it 99% of the time.
Can somebody help explain to me why this works and what the root cause of the problem is?
There are multiple separate modules and I don't seem to get any concerns at the very start of the course.
Caching is usually desired so that upon subsequent views, a user can view content more quickly. Caching issues that you may observe are not related to Articulate products, but rather to Flash, the Web browser, and / or the server on which the content is hosted.
I also have a problem with varnish cache clearing. The Moodle hosting I am using employs server level varnish and I have 2 Moodle apps on the same server. I want to clear varnish cache of one moodle app only. How do I do that?
3 Replies
Hi Dave,
Caching is usually desired so that upon subsequent views, a user can view content more quickly. Caching issues that you may observe are not related to Articulate products, but rather to Flash, the Web browser, and / or the server on which the content is hosted.
Hey Peter,
I thought it would be related to the amount of information that a SCORM package was storing on the LMS and thus 'clogging things up'.
We publish to SCORM 1.2 standards if that makes any difference.
How would the server come into the equation? Is there a setting we can adjust to 'handle more info' or am I way off base.
What are your thoughts?
Cheers,
Dave
I also have a problem with varnish cache clearing. The Moodle hosting I am using employs server level varnish and I have 2 Moodle apps on the same server. I want to clear varnish cache of one moodle app only. How do I do that?
This discussion is closed. You can start a new discussion or contact Articulate Support.