Quantcast
Channel: Adobe Community: Message List
Viewing all articles
Browse latest Browse all 90089

Re: Re: Captivate 7.0.1.237 no longer pulling in variables, HTML5 output, Javascript

$
0
0

Thanks Jim. I'll post what my colleague has run into and was wondering if you had any input? See below. She thinks the issue might not be with "our" code but could be the javascript files that Captivate populates.:

 

I think I finally have something that you can ask Jim about – that's been part of the problem, I haven't been able to come up with any questions for him because we can't get past this "Uncaught TypeError" in Chrome! If I can't load the green button (or the program in general), I can't debug.

 

I did a little research on the "Uncaught TypeError: undefined is not a function". This link (http://stackoverflow.com/questions/10429838/uncaught-typeerror-undefined-is-not-a-function -on-loading-jquery-min-js) got me looking at this line of code in index.html, where it looks like it's trying to load 2 js files:

var lJSFiles = [  'assets/js/jquery-1.6.1.min.js','assets/js/CPM.js' ];

cpXHRJSLoader.js(lJSFiles,function()

{

//console.log("js loaded");

lJSLoaded = true;

constructDIVs();

 

I took a look at jquery-1.6.1.min.js to make sure it ends with a semicolon (per the stackoverflow answer), and noticed something interesting about that file. It doesn't appear to end in a semicolon because it looks like the last bit of code gets commented out (see green below), which also comments out the semicolon. Of course I tried to stick a semicolon before the //, but naturally that made it worse.

Capture2.JPG

  The "Uncaught TypeError" is the one we get in Chrome.


Viewing all articles
Browse latest Browse all 90089