When I preview my project all of my tabs work fine (Menu, Notes, Resources) and I can see the lists of Menu items, notes, and resources. But after I publish, when I click on each tab I get small up/down arrows with not information displaying.
I am using Storyline 2 and publishing SCORM 1.2, HTML 5 Output. I have not had this problem previously.
Hi, Lisa -- Thanks for your question! Can you please confirm that you are testing your published output in the intended environment, and let us know if you are seeing the same behavior there as you are seeing in Preview? You may also want to check out this information on Unexpected or Erratic Behavior in SL2 and see if you find improvement.
Thanks! I think the environment could be part of my problem. I am trying to view the HTML5 file in Internet Explorer 11. Would that be the problem? It seems to look fine when I view in Safari.
However, I'm still not able to open the Resource. It shows under the Resources tab, but it won't open. Could this be because I removed the file from it's original location?
Hi, Lisa -- Thanks for your reply, and please see this information under the VIEWING CONTENT section within our System Requirements for SL2, and you will see that HTML5 is not supported in any version of IE:
HTML5
Windows: Google Chrome (latest version)
Mac: Safari 7 and later, Google Chrome (latest version)
Mobile: Safari in Apple iOS 7 and later, Google Chrome (latest version) in Android OS 4.1 and later
And yes, if the path to the items you are trying to access in the Resources tab has been changed, you may want to store the items in a project folder on your local C: drive, remove and reload the resources, and when you test in the intended environment, you should no longer encounter an issue.
If issues persist, you are welcome to share your file and I would be happy to take a closer look for you. :)
Hooray! I think my issue is resolved. I copy/pasted my resource files into the "external files" folder in story_content and that seemed to work. I also opened in the course in Google Chrome (and Safari), which worked perfectly. Thanks for your speedy response.
Double hooray, Lisa! So glad that you are all set and thanks so much for the update! Please don't hesitate to let us know if you should find you need anything else. :)
5 Replies
Hi, Lisa -- Thanks for your question! Can you please confirm that you are testing your published output in the intended environment, and let us know if you are seeing the same behavior there as you are seeing in Preview? You may also want to check out this information on Unexpected or Erratic Behavior in SL2 and see if you find improvement.
Thanks! I think the environment could be part of my problem. I am trying to view the HTML5 file in Internet Explorer 11. Would that be the problem? It seems to look fine when I view in Safari.
However, I'm still not able to open the Resource. It shows under the Resources tab, but it won't open. Could this be because I removed the file from it's original location?
Thanks again for you help.
Lisa
Hi, Lisa -- Thanks for your reply, and please see this information under the VIEWING CONTENT section within our System Requirements for SL2, and you will see that HTML5 is not supported in any version of IE:
And yes, if the path to the items you are trying to access in the Resources tab has been changed, you may want to store the items in a project folder on your local C: drive, remove and reload the resources, and when you test in the intended environment, you should no longer encounter an issue.
If issues persist, you are welcome to share your file and I would be happy to take a closer look for you. :)
Hooray! I think my issue is resolved. I copy/pasted my resource files into the "external files" folder in story_content and that seemed to work. I also opened in the course in Google Chrome (and Safari), which worked perfectly. Thanks for your speedy response.
Double hooray, Lisa! So glad that you are all set and thanks so much for the update! Please don't hesitate to let us know if you should find you need anything else. :)
This discussion is closed. You can start a new discussion or contact Articulate Support.