I have an Engage 09 interaction that previews just fine, but when I publish locally and try to run the course, I get a blank screen instead of the interaction.
It happened again and re-publishing into a new location was not correcting it. I ended up publishing just the Engage interaction into my course and then publishing the course.
I'm glad to hear that you were able to get this working again. However, I did want to stop by to recommend a different method for testing your published project. It sounds like you're viewing it locally, which may be the cause of the issue and why changing the location may not always result in a functioning project.
If you're viewing your published files locally, this may be the problem. If you view a published Studio '13 or '09 presentation 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 the article below for more information:
If you do not have access to a web server or LMS for testing, you could try using SCORM Cloud.
Another option would be to use ourTempshareserver. Just keep in mind that this server is only available for testing content - it is not officially supported by Articulate and all content will be removed automatically after 10 days.
You're always welcome to try outArticulate Online, as well - it's available for a free 30 day trial.
4 Replies
I had published to the same location a few times, deleting the folder in between. I was able to re-publish to a new location and got it to work.
Thanks for the update Tricia
It happened again and re-publishing into a new location was not correcting it. I ended up publishing just the Engage interaction into my course and then publishing the course.
Hi Tricia,
I'm glad to hear that you were able to get this working again. However, I did want to stop by to recommend a different method for testing your published project. It sounds like you're viewing it locally, which may be the cause of the issue and why changing the location may not always result in a functioning project.
If you're viewing your published files locally, this may be the problem. If you view a published Studio '13 or '09 presentation 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 the article below for more information:
Tips for Managing Project Files
I hope this helps!
Best,
Christine
This discussion is closed. You can start a new discussion or contact Articulate Support.