I have a link in my file to a url. It is a long and complicated URL but it works fine in the story_html5 output but hits a 500 error in the story output (flash version).
Any ideas on why this may be?
I am not running it locally and it does the same thing in Chrome and IE.
Are you able to share a copy to the link? Does the link work outside of Storyline? Where are you hosting the content - could it be getting caught in the LMS or web server? If so, you may want to try in another server or LMS, such as Tempshare or SCORM cloud.
We worked out a workaround with a re-direct html file, but it's not ideal for the client.
I will have to check with the client about sharing the URL.
It was hosted on a standard Apache server, not an LMS, but I doubt that is causing this issue.
The problem is the difference in rendering between the flash version and the html5 version, because, as I said the html5 version works just fine.
Other links also work fine - this is a complicated link as I say - it takes to the right page if you are logged in to the site it is taking you to and if you are not logged in it takes you to a page that asks you to log in.
So not a straightforward link. it may be security issues? but we cant expect our users to change standard Flash security settings.
The log in element may be what is tripping up the Flash security - but there isn't a way to change Flash security settings from within Storyline as it's user and browser specific. You could look at adding instructions on the slide itself prompting the users to ensure that they are logged in prior to clicking on the link. Since other links also are working normally, and the redirect provided you with a way around it, I'd continue to utilize that method and see if you can work with the client in regards to the gated access to the links.
3 Replies
Hi Leanne,
Are you able to share a copy to the link? Does the link work outside of Storyline? Where are you hosting the content - could it be getting caught in the LMS or web server? If so, you may want to try in another server or LMS, such as Tempshare or SCORM cloud.
Hi Ashley,
We worked out a workaround with a re-direct html file, but it's not ideal for the client.
I will have to check with the client about sharing the URL.
It was hosted on a standard Apache server, not an LMS, but I doubt that is causing this issue.
The problem is the difference in rendering between the flash version and the html5 version, because, as I said the html5 version works just fine.
Other links also work fine - this is a complicated link as I say - it takes to the right page if you are logged in to the site it is taking you to and if you are not logged in it takes you to a page that asks you to log in.
So not a straightforward link. it may be security issues? but we cant expect our users to change standard Flash security settings.
thanks
Hi Leanne,
The log in element may be what is tripping up the Flash security - but there isn't a way to change Flash security settings from within Storyline as it's user and browser specific. You could look at adding instructions on the slide itself prompting the users to ensure that they are logged in prior to clicking on the link. Since other links also are working normally, and the redirect provided you with a way around it, I'd continue to utilize that method and see if you can work with the client in regards to the gated access to the links.
This discussion is closed. You can start a new discussion or contact Articulate Support.