Forum Discussion

JosephZimmerman's avatar
JosephZimmerman
Community Member
6 years ago

articulate could not find slide in string table AND articulate actionator::exeJavaScript - $ is not defined

Hi, I'm new to Articulate and this forum. I am primarily concentrating on things that can be done with javascript.  Last week I had several things working and then I allowed some Articulate updates to be installed. 

Today I am receiving these two errors. The first one about not being able to find slides doesn't seem to be breaking anything so I'm not sure what that's about.

But the second error, where it doesn't know what the dollar sign is? That's the variable for jquery. That should automatically be recognized. Did Storyline stop supporting/including jquery? I cannot find anything in the published html includes that include jquery nor do I see any jquery js files in the published folders.

I searched for these two errors and found no discussion of them. I am assuming these were caused by the latest updates? According to the published story.html file I am on version 3.36.21213.0.

Thanks for your time.

28 Replies

  • TanyaBanninga's avatar
    TanyaBanninga
    Community Member

    Hi there, I have the error:

    'could not find slide in string table npnxnabnsnfns00000000001' in 'ds-frame.mobile.min.js:formatted:2651'

    Clip of offending code attached.

    I get it on every slide when the slide loads. I have not been too concerned as it all seemed to be working, but then I got feedback from a tester running the course on a tablet. They are unable to interact with 3 buttons on the result page. The review, replay and complete buttons.

    I tried the course in chrome with dev tools emulating an ipad and I was able to replicate the issue like this. There was no problem with the desktop view.

    I have since updated my version of storyline to the latest one and now I have the video at the start of the course unable to play on any device...

  • odell's avatar
    odell
    Community Member

    This thread contains two issues that should be separated.

    1. Errors related to removal of jQuery
    2. Error 'could not find slide in string table pxabnsnfns00001100101' in 'ds-frame.*.min.js' and the like

     

    FOR ERROR 'could not find slide in string table pxabnsnfns00001100101'

    1. Could be a bug related to the player? Typo in code somewhere?
    2. It happens also if I: 
      • start a new project
      • editing nothing whatsoever, only slide is the single blank slide created by default
      • publish to html5
      • using latest version of Storyline (as of 9-Sept 2020)
      • open in browser (chromium based)
    3. Here is a mention of string table pxabnsnfns00001100101 found in \html5\data\js\frame.js  --
      • "slide" is not there? 

      • odell's avatar
        odell
        Community Member
        Samantha Lowe

        @ville-

        Where did you find that?

        In the published output you can find it in \html5\data\js\frame.js

  • NickGarrod's avatar
    NickGarrod
    Community Member

    Hello.

    I am having some learners experience the ability to not be able to resume/restart SCORM launched courses as the Yes/No buttons are not being displayed when the module is launched. Is there a fix for this please?

    Thanks.

    Nick

  • Having the same issue. Checking in to see if support/anyone has resolved this issue?

  • VincentGama's avatar
    VincentGama
    Community Member

    Hi

    I had several student bring up the same issue on my side, that the published modules they are uploading to their LMS are not working on the tracking and updating the pass/fail statement. After further testing this error was appearing when running the published modules in the LMS and also on various different browsers.

    I have gone through all the recommended steps mentioned in the discussion to fix the issue and to no resolve. I have tested this on my own published build with very little content and it does exactly the same thing.

    Are these some form of restrictions for trail users?

  • Fast forward 3 years and this bug is still cropping up??!
    The could not find slide in string table... error where frame.desktop.min.js  is from a Bootstrap library causing an issue with a SCORM 2004 4th ed package.
    Upon resumption of a course in the LMS (Cornerstone) users are getting the 'spinning wheel of death' before they can even select whether to resume or not.

    But here is a quirky remedy we've passed along to our Help people - have the user simply downsize any full-screen window, or rt-click in Chrome to "view in tab".

    And the course itself has no special branching - it's quite linear with just a few scenes separating dozens of pages. 
    But the bigger issue is - why hasn't Articulate pushed out a patch for this yet??

    • JoseTansengco's avatar
      JoseTansengco
      Staff

      Hi Craig,

      Happy to help!

      Would you be willing to share a copy of your project file here or in private by opening a support case so I can take a closer look at the error shown in your screenshot? We'll delete it when we're done testing! I'll be sure to pass along any information that I find in my testing to our engineering team for further investigation.

    • ClintonOtte-For's avatar
      ClintonOtte-For
      Community Member

      Hi @Craig and @Jose,
      Have you all been able to find information that could help the rest of us with this "could not find slide in string table..." issue? 
      If so, could you share it with us in this thread? Thank you!

      • CraigBunyea-23d's avatar
        CraigBunyea-23d
        Community Member

        In my case Articulate Support was able to identify the relaunch wheel spin issue as one of our developers needed to update their version of Storyline (which was woefully out of date) - which is why it seemed to so randomly show up. As of today it's Build 3.87.32265.0 pushed 4/30/24
        But this didn't resolve the "find slide in string table" warning, which is coming from a Bootstrap included script, which as Jürgen mentioned, isn't a show-stopping error, just a nuisance.

  • this is only a warning, no error - every course I have ever seen has the warning

    @articulate: every developer who develops for the web should regularly check the browser console on all current browsers and fix ALL irritating messages that appear there