20 Replies
cynthia Kuni

Hi Mike

After recieving this query from the cllient, I quicky created this link and published, i inserted a shape and added a jump to url trigger on it.  I then published the slide and in the output folder, tried to view the swf file which is where i found it was not working though it worked in the htlm.

Peter Anderson

Hi David, welcome to the forums!

How are you publishing the course? To web, LMS, CD? 

You'll want to be sure you're testing your output in the environment for which it was published - simply playing the .swf file from the output will cause certain features to fail. 

Have a look at this article and see if it helps explain. 

Sharat Paroor

Hello everyone, 

has anyone found a solution to this issue yet? I have the same problem, the output was published to "Web" and in this particular case is hosted in our intranet. Which is mostly based on CQ5 from Adobe. The .html output seems to work with links whereas .swf output doesn't even react/trigger. 

@Peter: I've read all the help/guide articles on publishing and related issues. The only information I gather is that it could be a security related issue. Which is odd, because a colleague published a training "Adobe Presenter" also to an flash output which works fine with the link triggers also the Studio '09 Version didn't produce this issue. 

 

Leslie McKerchie

Hi Sharat!

I'm not sure I follow what the issue is.

If you are publishing the project via 'Web' and uploading to your server, we would expect you to be utilizing the presentation.html file to access the published course.

If you view published Articulate Presenter content 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 test your content and share it with others, you'll need to upload it to the environment for which it was published. Here's how.

Sharat Paroor

Hi Leslie,

thank you for the quick response.

Unfortunately the "presentation.html" does not scale appropriately to big screens, whereas the presentation.swf does. In the *.swf though the links do not work and yes the content is uploaded to the environment in which it is used and supposed to be used by other employees (intranet CQ5), as was written by me earlier. 

And I am not allowed to upload the content myself, it is uploaded by web/intranet product responsibles.  I am a bit irritated by the fact that you refer to the same guideline link, which I also already mentioned towards Peter. This link does not hold any useful information for someone who's already working by your guidelines. 

Mike Enders

Hi Sharat,

In regards to the course not scaling properly to large screens, have you attempted to adjust the Browser Settings?  If not, I'd suggest setting the browser to fill the screen and then scale the player to fill the browser. Additionally, you could launch the course in a new window.   These options might help you achieve the same results you're getting by launching the .swf.

Mike

Mandar Phadke

Hi Leslie,
Its OK if it does not publish to a single swf, but the swf content must work! Otherwise what is the point of having the swf?
Actually I want to use a software called Multimedia Protector that wraps the articulate storyline exe files in a wrapper for security. It should work, except that the URLs in the swf (which is the start/launch file for my package) may not work (if the
URL does not work in the swf in the package). What about embedded web content. Will it work in the swf?
But my question is why can't you address this issue, I see that it is more than 2 years old!
Best Regards,
Mandar

Leslie McKerchie

Hi Mandar!

Storyline publishes a collection of files for each course, which allows the content to progressively download elements. This means your content will have faster download and playback times.

As I mentioned, we do not support publishing to a single swf nor can we support the modification of the published output.

Perhaps someone in the community will be able to assist you with this request and if you would like to see this handled differently, you are welcome to share your thoughts with our product development team here.

Justin Grenier

Hi, Mandar.

The OpenUrl function is contained within the story.js file.  The story.js file is loaded by the story.html file, so the story.swf file doesn't know anything about that JavaScript file.

In other words, published Storyline projects are not self-contained .swf files and additional files are needed to view our published output.  Viewing published .swf files directly may not work properly and is unsupported.

Good luck with your project, and have a great weekend!