URL external link not working
Apr 24, 2014
I've done this before in Stoyrline so I don't know what is going on now.
When I setup a trigger on an object to go to an external link (new window) it takes me to a blank page instead of the address I set it up as. The address it goes to is C:// user.../output file/story_content/blank.html.
I have to get it to work using javascript, but I would prefer using the jump to url trigger. What I'm really trying to do is go to a bookmark on a webpage. The webpage is a glossary and I want to be able to place a trigger on the word in the course and go directly to the bookmark on the page. Right now the javascript just goes to the main page and not the bookmark. I've tested out the javascript in Chrome's developer tools and it works fine, is this just one of those quirks in storyline?
4 Replies
Hi Jerson,
I'm not able to assist with the Javascript, but in regards to your regular jump to file/url trigger - what is the url you're trying to use? Is it a local link like the one it's directed you to? Also, just to confirm you're testing the published content within the intended environment?
That's the thing, I've used the jump to URL trigger before and it worked while I ran it from my computer. This time it won't. Plus it keeps creating a blank.html file in that directory. I"m wondering if something else caused this or is it my recent update to version 5.
Hi Jerson,
I haven't noticed the "blank.html" file being created with my files, so we'd want to take a look at your .story project to see if it's something project specific. Running content locally is generally something we advice against due to browser security restrictions and other unpredictable behavior. I do know that there is a newer issue with Google Chrome trying to run content locally as described here - is that the browser you were using?
I'll see if I can pull a slide and duplicate the problem. I tried it on both IE9 and chrome. I'll update this as soon as I can. Maybe there is another simple solution that I'm missing.
This discussion is closed. You can start a new discussion or contact Articulate Support.