Links in resources tab not opening in published file

Jan 30, 2014

Hi all,

I'm testing a module and have published my file to the web which includes two web links accessed from the resources tab in the player. I tested the links within storyline and they are working fine.


When i click to open the icons appearing in the resources tab of  my published product nothing happens.

Any ideas please

10 Replies
Christine Hendrickson

Hi Fiona,

Make sure you're not testing the links locally. If you view a published Storyline 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:

Publishing and Sharing Articulate Storyline Content

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 our Tempshare server. 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.

In addition, you could also use Dropbox. Just remember that you'll need to place your content in the "Public" folder. Also, you'll need to make sure that the folder is enabled. To do so, click on this link.

You're always welcome to try out Articulate Online, as well - it's available for a free 30 day trial.

Let me know if you upload the project to a server and still have trouble opening the links in your Resources tab.


Ashley Terwilliger-Pollard

Hi Mark and welcome to Heroes! 

Are you sharing the .story file with them to view or the published presentation? As Christine mentioned you'll want to test the content within the intended publish environment, and it could be the server blocking access to the URLs and browsers. If you've saved the .story file to a server or published it to the server, you could also be causing issues within the file as mentioned here - you'll want to save and publish to a local drive.  

I'd suggest trying to upload the published output to one of the web server options Christine previously mentioned to help narrow down if your network server is causing issues with the links. 

Judy Hartmann

I don't actually see an answer to the question on why the resources or, i.e., help files are not opening in published format.  I have two Storyline projects, one in Spanish and one in English.  The English help tab file works, the Spanish does not.  No difference other than the language.  Any thoughts?

Sarah Pouezevara

I'm having a similar issue. Looking for the answer here, this seems to be the most relevant thread, but there is no answer!  I have published my courses to a scorm LMS.  Some users can open some resources from the resources tab (.pdf documents), others can not open the same resource. There doesn't seem to be any pattern. If it were browser settings, then one individual could presumably not open ANY of the resources, right?  If it were a problem with the file name or that the file actually wasn't published, then NO ONE would be able to open the particular file. Users opening the same file from different browsers have different experiences. Any ideas?

Alyssa Gomez

Hi Sarah,

Sorry to hear your learners are having trouble with the resources! I can be tough to nail down an issue that happens sporadically--have you found that a particular browser is giving learners the most trouble? Also...

  • What version of Storyline did you use to create this course?
  • Where are the PDF documents stored--on your local computer or on a server?

We'd be happy to help you test your file, if you'd like. Simple upload the unpublished file to this form, and we'll take care of the rest. 

Becca Levan

Hi Andrea,

Thanks for reaching out, and I'm sorry you're hitting this snag!

Without seeing your file, it's hard to pinpoint what's causing this, but let's start with these tips:

If you've already followed the steps in this article, I'd recommend opening a case with our Support Engineers to investigate. Once we receive your file, we'll be in touch with a next step!