I am working on a project where we do not want to have any swf file in the published output. We are instructed not use any flash object from the security point of view. Does anybody know whether it is possible remove swf or there is any workaround?
Thanks for your inputs, Matthew. As you said that I need to modify the published output, what exactly I need to do. Could you please explain more in detail? Also, if I remove the flash files, will it affect the project in any ways?
Same problem. We are publishing to Absorb LMS. I deleted all swf from the output and tested on local machine, it worked fine. But on LMS, the course doesn't work.
I know some folks have looked at removing all the SWF files in Storyline 2 (or other earlier versions of the output) but it's not something we can support. We do understand the need for HTML5 only publishing and as such it was an included feature in Articulate 360 subscription and Storyline 3 perpetual license. Take a look at the trials for either of those, as it sounds like that's a crucial feature for you.
Thanks Matt, Manu, and Ashley for your valuable time and suggestions. Presently, I am using SL2; therefore, I will try the workaround suggested by Matt.
We are also going to upgrade it to SL3 very soon. :)
The steps worked, but it isn't a fool proof solution. For me deleting the swf and changing the manifest distorted player got distorted. For example, in the attached screenshot, the tab separators have moved up and scrolling arrows are displaying adjacent to tab names.
Thats the part I caution against Manu. :( It's not full proof as it's not designed to have those files removed. If you know that some things may be a bit different than expected and you can properly test for them, then it may be a viable option for you to remove the SWF files, but based on the oddities we know can occur it's not something we can support.
This seems a little paranoid to me. If there is a concern about Flash content, the Flash player should be prevented from installing. How could providing swf files that you generate be a security risk? I thought the risk would be from downloading rogue swf files.
I know a lot of corporate or government entities are starting to just shut out Flash files by default especially within a browser view - at least that's a lot of what we've been hearing, and as such with Storyline 3 and 360 made the shift to include HTML5 only output.
9 Replies
Thanks for your inputs, Matthew. As you said that I need to modify the published output, what exactly I need to do. Could you please explain more in detail? Also, if I remove the flash files, will it affect the project in any ways?
Awaiting for the response.
Yes, Matthew. I am using LMS.
Same problem. We are publishing to Absorb LMS. I deleted all swf from the output and tested on local machine, it worked fine. But on LMS, the course doesn't work.
Hi Manu and Firoz,
I know some folks have looked at removing all the SWF files in Storyline 2 (or other earlier versions of the output) but it's not something we can support. We do understand the need for HTML5 only publishing and as such it was an included feature in Articulate 360 subscription and Storyline 3 perpetual license. Take a look at the trials for either of those, as it sounds like that's a crucial feature for you.
Thanks Matt, Manu, and Ashley for your valuable time and suggestions. Presently, I am using SL2; therefore, I will try the workaround suggested by Matt.
We are also going to upgrade it to SL3 very soon. :)
Thanks Ashley and Mathew.
The steps worked, but it isn't a fool proof solution. For me deleting the swf and changing the manifest distorted player got distorted. For example, in the attached screenshot, the tab separators have moved up and scrolling arrows are displaying adjacent to tab names.
Thats the part I caution against Manu. :( It's not full proof as it's not designed to have those files removed. If you know that some things may be a bit different than expected and you can properly test for them, then it may be a viable option for you to remove the SWF files, but based on the oddities we know can occur it's not something we can support.
This seems a little paranoid to me. If there is a concern about Flash content, the Flash player should be prevented from installing. How could providing swf files that you generate be a security risk? I thought the risk would be from downloading rogue swf files.
I know a lot of corporate or government entities are starting to just shut out Flash files by default especially within a browser view - at least that's a lot of what we've been hearing, and as such with Storyline 3 and 360 made the shift to include HTML5 only output.
This discussion is closed. You can start a new discussion or contact Articulate Support.