Publishing without Flash using multiple tracking options - bug

Hello P T!

I'm happy to help! It sounds like you might be running into a bug that we've reported to our team. We are noticing that the Flash output appears in the published output folder when the project uses the trigger "Jump to Time/Cue Point."

Do you have this trigger in your course?

Either way, I'd like for our team to start troubleshooting in a support case so that we can offer 1:1 support. You can start a support case with our team here.

Hi Lauren,

That link doesn't seem to work for me; it says "sorry, that link no longer exists" when I click it.

The course has several slides with "Pause Timeline When Timeline Reaches time Xs" and "Resume Timeline when user clicks Y" triggers, but no "Jump to time/Cue Point" triggers.

Changing the settings in the way I described above caused me to be able to publish the course properly, without any Flash output, so I don't believe what you described is the bug we  experienced.

Hi there, P T!

Apologies for the broken link — I'm going to connect you with our Support team directly for fast help. They'll likely need to test an affected file, so please use this custom upload link to share it privately:

• File Upload Link For P T

We appreciate you helping us get to the bottom of this!

I'm happy to return to this discussion with an update!

Today, we released Storyline 360 Update 48! Here are the features and fixes released in this update. You might notice the bug you reported has been fixed!

Fixed: When publishing a course with the classic player style and HTML5-only features, such as jump-to-time triggers or multiple completion criteria, the output erroneously included Flash files.

Now all you need to do is update Storyline 360 in your Articulate 360 desktop app! Thank you for taking the time to report this bug to us.

Hi Lauren, 

I am curious about something. I have been trying to make a print to html project from Matthew Bibby work. I followed the tutorial to a T. Today I noticed when I re-opened his project files, which was created in an older version on Storyline, there was an option available that isn't in 360. "Publish>format options" I am wondering if the setting "Flash/HTML5" is the reason why his project still works and my test project does not? Either way I put my code in the project files, and the code works....my story seems to not collect or pass the variables. 

Update: (ten minutes later hehe)

So I re-published the project files and selected "html5" from the formatting options and sure enough...it didn't work!

Hi Lia,

Older files published using those options will still display the previous options. Newer files no longer have the option to publish to Flash output.

Storyline 360: The End of Flash Importing and Publishing

I see that you are working with Matthew directly here on his custom code.

Thanks Leslie. I am not too concerned with the old vs. new options. I am more concerned about variables not passing to an html file in SL360. I have text and yes/no variables setup, after publishing the course in SL360, the variables never pass from SL.

When I compared MB's project files, that is when I noted the older SL publishing settings vs. the new SL360 publish options. So as a test, I published MB's projects files as is and they worked fine. Next I published MB's files, set to "HTML5" only (to mimic SL360), and sure enough the variables didn't pass.

My current project in SL360 is dependent on being able to pass SL variables to a PDF printout. I need to gain clarity on how to get variables to pass in SL360.

Have you checked the console to see if there are any errors, I doubt it is the tracking options that are causing the issue, it may be an issue with the way the code is written

Yep! Here was my original documentation which included console errors:

"I have tried this tutorial and the original print to html tutorial and I can't figure out why my variables are not passing (or maybe they aren't storing). I have added the files to linters and combed the code side-by-side without any troubleshooting luck or obvious issues.

Only one DOM error on client-side in my code files: 

Uncaught DOMException: Blocked a frame with origin "null" from accessing a cross-origin frame.
at file:/process.js:4:32

Line 4 referenced:  var player = opener?opener.top.GetPlayer():{} ;

I then took your "pretty" story file and published with my code files and your example story file doesn't pass the variables when launching print.html. Next, I took your code files and published my story file and had the same result: now my story file doesn't pass variables even using your code. I tried using a newer version of Jquery, and ensured that the story file was updated to 360 format."

The JS error is preventing the user.is from running it is a cross domain issue.

Are you running it from inside review? As review opens it from inside an iframe it may not be visible.

Sent from my iPhone

No, I have been publishing to desktop and running direct in browser while testing. 

You need to upload the JavaScript is unlikely to work locally

Sent from my iPhone

Hmm ok, JS runs just fine in Chrome browsers. I am unaware of a case where it wouldn't work in a Chrome/Edge browser. I will try your solution. 

I am still curious about why js variables are not passing when content is published in SL 360?

You are showing console errors it is likely that the javascript is not running completely because of this, could be because you are running locally and the window that opens has a cross domain issue, testing locally is not a good way to test JS

That test was unsuccessful for me. I also remembered after receiving the "XML file does not exist" error that the project files have external file dependencies (a script, some css, and the print.html file) so testing in Review 360 wouldn't help unless I added some button to my test project that could open an html file and execute the js script in one trigger. 

Without seeing the course and code  this is very much looking for a needle in the haystack you may need to open a support case unless you can post the files here.