Turn off javascript error when previewing scenes?

Hi Monique,

There isn't a way to turn it off - but I did see a user share a workaround the other day to set up the javascript triggers to fire based on the condition that X is equal to true...since it's just a false variable not actually used or referenced anywhere, it's never going to be true and therefore the Javascript won't execute. It's a bit to set up and remove if you have Javascript on every page so hopefully one of our other users will chime in here with additional ideas. 

I do have the same problem, it is pretty tedious to dismiss the error for every single step :(

Hi Simon,

Have you looked at publishing individual scenes or slides to Review 360 (if you're using Storyline 360)? That would help you get around the pesky Javascript preview error and see how all your courses look once published! 

The problem I am having is the message pops up and eventually stops the program from running. There should be a better solution than this. I don't see why the message pops up all the time and I already know javascript does not run in preview. 

When a message starts interfering with a program, that message is now a problem. I don't think we should have to get around something like this. Hope there is a better solution at some point.

I just tried my project again and I cannot preview one slide let alone a scene. It locks up my program when I try to dismiss the error so I have to use Task Manager to close it. I don't see this as acceptable. Am I the only one having this problem?

I have sometimes used the solution noted above if I know I will have a lot of javascript in a project.

I add a variable called preview with a default value of True. 
All of my JS triggers have a condition to run IF Preview is = to False. This essentially disables all the JS for preview during development.
Anytime I want to publish to test the script as well, I simply change the variable's value to False and publish. I don't have to change any JS since the condition on the trigger will now allow it to fire.

It's a work around for functionality that I too wish was there, but it isn't a complex one.

Thanks Owen, I looked at that solution earlier but could not find it again. So I must also change every JS trigger to have this condition. Probably easier as you build them. In this case, I will have to open all of them and add the condition. 

I sure don't remember this as a problem several years back but maybe I was not using much javascript. Thanks and I will get  to work.

Maybe I am doing this wrong, but adding that condition to my JS does not stop the pop up.

At least is allows me to keep working but the message appears on every slide. 

That looks right. I assume you set up a variable named "Preview" and set it's value to "True"?

When working with JS..i just always publish... 

Me too Math, it is the only way to test the JS. However, sometimes you just want to test everything else (non-javascript dependent stuff) without the constant pop-up telling you the JS won't work. Using a variable and adding a condition on your JS is an easy way to turn it on and off.

Just a thought, but could you avoid having to change the value of Preview to false before publishing by adding a JS trigger to set it to false?

That would leave it true in preview, but change it to false when running published output.