Quiz is requiring multiple clicks of Submit or Next

Jan 30, 2014

I have a quiz that is requireing the user to hit submit up to 4 times before the next question will come up??

I switched to submit all at once and now requires the next button be clicked multiple times?

This particular quiz is not offering feedback following the question! 

PLEASE HELP... Users are not happy!

QUIZ MAKER 13 is being used to build the quiz, it happens in both the preview and when I load to our LMS.

13 Replies
Nathan Karet

I'm having a similar issue.

I have 2 quizzes that were created in the same way, with the same settings in Quizmaker. I can't find any difference between the two files (same settings, # of questions, type of questions, etc.)

The quiz I've attached has the same delayed response that others in this thread have mentioned. It takes 10-30 seconds for the next button to work to advance the questions.

Any insight into what happened with this file that is different than a standard quiz file would be appreciated so I know how to fix this in the future.

For now, I used a quiz that I knew was functioning properly, did a Save As, deleted all of the questions, imported the questions from this file and everything works fine.

Thanks!

Leslie McKerchie

Hi Nathan!

Thanks for sharing your file. I took a look and could see the issue that you are reporting. I then imported the questions into a new file and the course performed as I would expect, no delays. I then imported your player template to the new file, and the issues returned.

It seems to be that your player template may be corrupt.

Leslie McKerchie

Hi Nathan!

Unfortunately, that is the tough question. We have some general tips for preventing various corruption that you can check out below. I also wanted to mention that replying to the forums via e-mail attaches your signature, but you are welcome to pop in and edit that if needed.

File corruption is unpredictable, and there's no straightforward way to determine what causes it. Common causes are environmental (disk errors, power outages, improper shutdowns), viruses, failed Windows updates, and even file size (i.e., very large files have a higher risk of corrupting).

Consider these preventative measures to protect your project files:

1) Save and publish projects on your local hard drive. Working on a network drive or external USB drive can cause erratic behavior due to latency.

2) Save incrementally. If your app has an AutoRecovery feature, take advantage of it. If not, save a new version of your project every hour or so with a new file name each time. If a file becomes corrupt, you'll still have a working version available.

3) Install Dropbox. Snapshots of changes in your local Dropbox folder are kept for 30 days. If a file is damaged or deleted, you can restore a previous snapshot: https://www.dropbox.com/help/11/en.

4) Don't leave the app open and unattended for long periods of time. Some users have reported file corruption after leaving their apps open overnight. It's possible that a malware scan or disk backup could run because the machine is idle, making your app vulnerable to crashing.

This discussion is closed. You can start a new discussion or contact Articulate Support.