When previewing (dropping the story.html into the browser) my file I get the following Warning: "The hyperlinks feature on this slide has been disabled while viewing locally because your browser does not support it" This is happening in Chrome, Safari, Firefox and Opera on my Mac. Is there a setting I can change to allow hyperlinks? As an aside, is there an issue with hyperlinks opening in Chrome?
You would want to publish and upload the content to it's intended environment to properly test.
Although most content displays during preview just like it would in the published output, there are a few items that are unavailable during preview. They are:
Videos from websites, such as Screenr, YouTube, and Vimeo
Web objects
Interactions imported from Articulate Engage
Print results
JavaScript triggers
Hyperlinks may not work during preview. We recommend publishing to test hyperlinks.
If you view an Articulate Storyline course 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 to fail. To properly test your published content and share it with others, upload it to the environment for which it was published. See this article for details.
I am having this same problem. I have never had an issue with publishing the file to the web. I test it on my network computer and place the published file into a shared file on the same network. If you use another computer (on the same network) to access the shared file the hyperlinks are disabled. This has never happened in the past. I am publishing the same way as I have always done and now I get the "hyperlink disabled" response. What has changed? This is such a great feature to use in our training department... very frustrating to now see it disabled. Any help you can give would be so very appreciated.
Hi, I also have the same issue where the course works fine until you attempt to use a hyperlink. Then I get:
The hyperlinks feature on this slide has been disabled while viewing locally because your browser does not support it.
The course is published and accessed on a fileserver that my students access. The really frustrating part is that it only happens on three out of ten computers. I even tried replacing one of the computers but I am still having the issue when I run the HTML document. If I have the student run the course_html5 document I do not get the error. I think it must be a computer setting for the browser otherwise it wouldn't work on the other computers, but I can't find anything that would authorize hyperlinks.
Have you published for web? Is the file server considered a local drive for them or a web server? It could be the browser security restrictions as detailed here.
This is published for the Web. The file server is a network file share, and when the story opens it has a network file address in the bar. The story works great on most computers, I just have this issue on a few computers. The link doesn't appear to have any documentation about browser restrictions.
My apologies for not clarifying, that article refers to how if you're testing the content locally or in another environment than which you published for, that the content could not play as expected based on browser restrictions. What those restrictions are is dependent on the browser, system settings, corporate security, etc. so we don't have documentation connected to those. If it's a network file share, I'd look at using one of the web options in that article to test uploading it to and see if t hose same users can access the course that way and that'll help pinpoint the problem to the file server or the browser they're using or both.
I'm very disappointed in your answers. You very clearly stated that the article was about a detailed description for browser security restrictions. Then your reply clarifies that it has nothing to do with what was stated. I am also very disappointed that you do not have any documentation on what your product needs to work. I believe I was quite clear that this method I use to distribute the content, which has worked in the past, is not working on only a few of the training computers. I believe I also mentioned that story_html5 worked as a work around. So as far as I can tell it is not the location I use, as that would affect every computer. It is also not the browser as that would not work with the html5 link.
I'm sorry to have caused disappointment, but I think there has been a bit of confusion or miscommunication. I didn't mean to indicate that all browser security restrictions were detailed in that article, just that the issue of browser security and Flash restrictions that can occur when viewing content locally or outside the published environment was mentioned/detailed in that article. We don't have a full listing of the security settings for each browser, as the options can be driven by individual or corporate settings, any browser add ins, browsers and different versions used, etc.
We do have documentation in terms of the system and viewing requirements here, and you did mention a few computers and just a few trainings, which is why I erred towards browser settings (or even different browsers) being a likely culprit as it sounds as if the course behaves perfectly normal for other users/computers. If I misunderstood your statement about it working for some users and not others, we'd likely need to take a look at the course in question and would begin with needing the .story file and then we'd do some additional testing by uploading to a web server. You are welcome to share that here using the "add attachment" button at the bottom of the reply window and I'll gladly assist. If you'd prefer to work with someone else, you can also reach our Support Engineers by uploading your files at the hyperlink included here and they are accessible 24/7. That link will also allow you to share files confidentially. If you choose to submit to our Engineers, I am also happy to follow along - so just let me know once you submit the case # you'll receive automatically via email from Support (a) articulate.com.
I hope I cleared up some of the confusion, and please let me know how else we can assist.
9 Replies
Hi Lee!
You would want to publish and upload the content to it's intended environment to properly test.
Although most content displays during preview just like it would in the published output, there are a few items that are unavailable during preview. They are:
If you view an Articulate Storyline course 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 to fail. To properly test your published content and share it with others, upload it to the environment for which it was published. See this article for details.
I am having this same problem. I have never had an issue with publishing the file to the web. I test it on my network computer and place the published file into a shared file on the same network. If you use another computer (on the same network) to access the shared file the hyperlinks are disabled. This has never happened in the past. I am publishing the same way as I have always done and now I get the "hyperlink disabled" response. What has changed? This is such a great feature to use in our training department... very frustrating to now see it disabled. Any help you can give would be so very appreciated.
Hi Chris! I'm not sure about a hyperlink disabled message. That sounds like an different issue.
Are you adding hyperlinks as explained in this documentation and publishing/sharing as explained here?
Hi, I also have the same issue where the course works fine until you attempt to use a hyperlink. Then I get:
The hyperlinks feature on this slide has been disabled while viewing locally because your browser does not support it.
The course is published and accessed on a fileserver that my students access. The really frustrating part is that it only happens on three out of ten computers. I even tried replacing one of the computers but I am still having the issue when I run the HTML document. If I have the student run the course_html5 document I do not get the error. I think it must be a computer setting for the browser otherwise it wouldn't work on the other computers, but I can't find anything that would authorize hyperlinks.
Hi Devon,
Have you published for web? Is the file server considered a local drive for them or a web server? It could be the browser security restrictions as detailed here.
This is published for the Web. The file server is a network file share, and when the story opens it has a network file address in the bar. The story works great on most computers, I just have this issue on a few computers. The link doesn't appear to have any documentation about browser restrictions.
Hi Devon,
My apologies for not clarifying, that article refers to how if you're testing the content locally or in another environment than which you published for, that the content could not play as expected based on browser restrictions. What those restrictions are is dependent on the browser, system settings, corporate security, etc. so we don't have documentation connected to those. If it's a network file share, I'd look at using one of the web options in that article to test uploading it to and see if t hose same users can access the course that way and that'll help pinpoint the problem to the file server or the browser they're using or both.
Hi Ashley,
I'm very disappointed in your answers. You very clearly stated that the article was about a detailed description for browser security restrictions. Then your reply clarifies that it has nothing to do with what was stated. I am also very disappointed that you do not have any documentation on what your product needs to work. I believe I was quite clear that this method I use to distribute the content, which has worked in the past, is not working on only a few of the training computers. I believe I also mentioned that story_html5 worked as a work around. So as far as I can tell it is not the location I use, as that would affect every computer. It is also not the browser as that would not work with the html5 link.
Hi Devon,
I'm sorry to have caused disappointment, but I think there has been a bit of confusion or miscommunication. I didn't mean to indicate that all browser security restrictions were detailed in that article, just that the issue of browser security and Flash restrictions that can occur when viewing content locally or outside the published environment was mentioned/detailed in that article. We don't have a full listing of the security settings for each browser, as the options can be driven by individual or corporate settings, any browser add ins, browsers and different versions used, etc.
We do have documentation in terms of the system and viewing requirements here, and you did mention a few computers and just a few trainings, which is why I erred towards browser settings (or even different browsers) being a likely culprit as it sounds as if the course behaves perfectly normal for other users/computers. If I misunderstood your statement about it working for some users and not others, we'd likely need to take a look at the course in question and would begin with needing the .story file and then we'd do some additional testing by uploading to a web server. You are welcome to share that here using the "add attachment" button at the bottom of the reply window and I'll gladly assist. If you'd prefer to work with someone else, you can also reach our Support Engineers by uploading your files at the hyperlink included here and they are accessible 24/7. That link will also allow you to share files confidentially. If you choose to submit to our Engineers, I am also happy to follow along - so just let me know once you submit the case # you'll receive automatically via email from Support (a) articulate.com.
I hope I cleared up some of the confusion, and please let me know how else we can assist.
This discussion is closed. You can start a new discussion or contact Articulate Support.