Skip to main content
Known Participant
November 27, 2022
Question

Long Running Script in Preview

  • November 27, 2022
  • 2 replies
  • 1037 views

Hello All,

 

A SME was unable to complete a SCORM 2004 3rd Ed file, so I first replicated the issue in the LMS (Adobe Learning Manager). Next I went into Captivate and looked at the slide where he discovered the problem. The slide itself does not have anything unexpected in its objects, actions, etc. that would cause the issue, which is simply that when all of the 4 buttons with answers in them are not executing the "Jump To Slide" action they're all assigned (navigating to 4 different slides for particular-mistake-specific remediation).

 

I removed all pauses from buttons, and rearranged slide orders to utilize the "Go To Next Slide" action instead of "Jump To Slide," even though neither should matter in theory. FINALLY, after a dozen guesses (and previews of the project) at different things it could be, I clicked the button with the correct answer in it (which is triggering all objects not be able to be clicked any more) and sat in frustration for about 30 seconds racking my brain when the attached screenshot with its error message at the bottom of the screen came up that reads "localhost is not responding due to a long-running script" and gives me a "Stop Script" button. When I clicked Stop Script, it jumped to the proper slide and all worked well.

 

I'm no developer, so I don't know what could cause this, but I started trying to locate a root cause within the Captivate file by Previewing "From This Slide" at each of the sections of the material and working backwards. The previews ran perfectly up until I was previewing the entire Project. The same issue happened when I used the Preview Project, as well as when I previewed "From This Slide" while highlighting Slide #1.

 

I then deleted Slide #1, which was largely window dressing, thinking that the slide was corrupted for one reason or another. When I previewed the Project, I ran into the same problem on with the long running script.

 

Assuming that the long running script is causing the same problem in the Captivate Preview function as it is in the published SCORM files (without the error message coming through), I am at a loss on how to resolve it, especially since we used the same template for many other SCORM files of identical design that are working as expected in the same LMS.

 

Any ideas or experience with this would be much appreciated, thank you in advance to anyone that can help!

    This topic has been closed for replies.

    2 replies

    Lilybiri
    Legend
    November 28, 2022

    Some real important information is missing. Which exact version of Captivate are you using? The full version number, please, as you can find under Help, About Captivate.

    Second question: are you on a non-responsive or a responsive project? If it is responsive, did you use Fluid Boxes or Breakpoint views? 

    If it is a non-responsive project: did you preview with F11, Preview HTML in Browser? That is the only real valid preview in that case, contrary to responsive projects with Fluid Boxes. If you rest it with F11, didn't you get the same issue? Which browser(s) did you use?

    The Preview window of an advanced action (as Rod and myself would like to see) can be opened using this button:

    Sorry if you did know that, but around 90% of CP users ignore its existence (and a lot more of features of the AA dialog box).

    Last question: you talk about a 'template', which is a word often used for many things. I just hope you are not talking about a 'cptl' file in Captivate, which is very buggy. Moreover if the theme used in this template dates from versions ago, it could also be the cause of issues.

     

     

     

    Known Participant
    November 28, 2022

    Hi @Lilybiri , thanks for the reply! I'm definitely part of the 90% ignoring AA dialog box features... and even ignoring @RodWard 's request for that info (by accident). Here's all the info requested:

     

    -Captivate Version: 2019 Release 11.8.0.586

    -Project Type: Responsive and using Fluid Boxes (haven't used Breakpoint views before)

    -AA Previews:: Screenshots attached. The only Conditional AA of the 3 is the Pause_Button AA.

     

    In previewing the AAs, I noticed that in the RetakeChapter AA we left the Execute Javascript: cp.resetQuizData() that you guided me to replace in other files a couple of weeks ago. I've left it in there for now in case it's part of the problem, but normally I'd get rid of that since discovering the side effects of using that JS command.

     

    -Template reference: not a .cptl file, just a basis for the navigation for the remediation relationships/actions. I was saving it as a new file, then revising as necessary. I have not applied a Theme to this project file, but it's possible that the first version of this file was created in an older version of Captivate (which has been the basis for all 4 of these project files that are acting up). These project files were started 3 months ago, finalized 3 weeks ago, and Captivate is supposed to be auto-updating for me.

     

    Thanks again for the guidance!

     

    Lilybiri
    Legend
    November 28, 2022

    I wonder if this is another bug in 11.8, have seen a lot of problems mentioned for that version. 

    You always have a Theme in any project, I wanted to know if the theme was a custom theme ? From your description I understand it was created in an older version. Was that version 11.0 or even an older version. Themes had a significant update with version 11.5.

    I have seen your Toggle conditional action before (probably in another thread), even offered a link to my Play/Pause button tutorial.

    The ReplaySlide action will not reset the slide, but maybe that is not necessary.  The RetakeChapter has that famous JS command  which caused you problems in the other thread. Do you need it? 

    To see the full picture of the problem slide, can you post a screenshot of the expanded part of the Advanced Interaction panel for that slide? That way we can see which actions are triggered by which events. 

     

     

    RodWard
    Community Expert
    Community Expert
    November 28, 2022

    If this is happening on a slide where a Conditional Advanced Action is being executed, the most likely reason for the issue is a logic flaw somewhere in that Advanced Action.  

     

    Can you provide us with more information about that condtional action?  E.g, screenshots of the output when you click the Preview Action button on the Advanced Action dialog.

    Known Participant
    November 28, 2022

    @RodWard Thanks for the reply. There are no Conditional Advanced Actions being executed on the slide (screenshot attached).

     

    For the slide in question (Question 13), the On Enter Action  and Exit Action are both "No Action." Basically, we're waiting for the student to choose an answer, which works on 12 identically-setup question slides... Unlucky #13 is the problem child!

     

    In the Slide Objects screenshot, the 4 large answer choice buttons and the Previous Question button (top Fluid Box) all have an On Success Action of: Jump To Slide [X]. The slides that the answer choice buttons jump to do not have Advanced Actions being executed, they are all set up with On Enter: Continue and On Exit: Pause.

     

     All buttons in the top Fluid Box (except for the Previous Question button) have an On Success Action of: Execute JavaScript with a script window similar to this one (Current Window😞

    window.open("https://abc123.com/practice/id_code/Chart_1.pdf", '_blank', 'height=500,width=1080,scrollbars=yes,resizable=yes');

     

    On the Question 13 slide, these buttons pull up the proper PDFs until one of the answer choice buttons is clicked, which is when all freezes for 30 seconds or so before the long script error message appears.

     

    The only Conditional Advanced Action in this file is a Pause_Button AA (screenshots attached), which is not used on the slide in question (only remedation material slides). In all of the testing completed today, I never once triggered the Pause_Button AA.

     

    If all that doesn't add up, is there anything else that can cause this error message?