Quizmaker output won't play

I'm using Quizmaker 09 via VMFusionware on a Mac. For years I've been able to publish on the windows side and copy over to the Mac side when complete. I can usually click on the html file to view the output via Safari or Firefox. I would receive an Adobe warning, but could just close the warning and view the output. However, for this last publish on a new project, I'm suddenly unable to view the content. Adobe directs me to add the file as site I'm allowed to view via system preferences, but I'm still not able to open the file even after doing so. Any ideas?

6 Replies
Leslie McKerchie

Hi Rainey!

If you view a published Quizmaker '09 quiz on your local hard drive or send it to someone else to view on their local hard drive, you'll encounter security restrictions from the computer, web browser, Flash Player, and network that'll cause various features of your content to fail.

To properly test your published content and share it with others, upload it to the environment for which it was published. Please review this article for details.

Rainey Blackwell-Bullock

Hi Leslie,

Thank you for your response and the link to the article! I have uploaded to a shared dropbox folder (as was mentioned in the article) and still encounter the Adobe warning and just spinning when I click on the html file in the dropbox folder. Hopefully the client will be able to access the content, even though I can only view it in Windows? Is there another way I should be publishing (I opted for web) to avoid this problem? This quiz will ultimately be part of a presenter tutorial, so I'm a bit worried I'll have the same trouble there.

Many thanks in advance!

Rainey

Rainey Blackwell-Bullock

Forgot to add - I'm still able to open quizzes that I created in years past using the same method (on my Mac using Firefox). I simply click out of the Adobe warning message and the quiz loads as it should. That's one of the reasons I'm confused by this weird behavior with the latest quiz!

Thanks!

Leslie McKerchie

It sounds system specific Rainey. Perhaps an update since last publish is what is causing this issue, but I have not seen anything like this reported. If you are publishing and sharing the content as shared above, it should not cause an issue for your end user as long as they meet the system requirements.