Using the later JS file got me past the .src error, but I'm now experiencing issues with the diagram disappearing after being (briefly) displayed. (There are no errors in the debug console, nor are there any errors on the network tab.)
If I step through the document.ready() function, I see the various shapes getting drawn (e.g., links, nodes, labels, images, etc.), but at some point the diagram disappears when stepping through the MindFusion.Diagramming.js code at the following location (I have a breakpoint set on the highlighted line below):
S.ajaxTransport(function(i) {
var o, a;
if (v.cors || zt && !i.crossDomain)
return {
send: function(e, t) {
var n, r = i.xhr();
if (r.open(i.type, i.url, i.async, i.username, i.password),
i.xhrFields)
for (n in i.xhrFields)
r[n] = i.xhrFields[n];
for (n in i.mimeType && r.overrideMimeType && r.overrideMimeType(i.mimeType),
i.crossDomain || e["X-Requested-With"] || (e["X-Requested-With"] = "XMLHttpRequest"),
e)
r.setRequestHeader(n, e[n]);
o = function(e) {
return function() {
o && (o = a = r.onload = r.onerror = r.onabort = r.ontimeout = r.onreadystatechange = null,
"abort" === e ? r.abort() : "error" === e ? "number" != typeof r.status ? t(0, "error") : t(r.status, r.statusText) : t(_t[r.status] || r.status, r.statusText, "text" !== (r.responseType || "text") || "string" != typeof r.responseText ? {
binary: r.response
} : {
text: r.responseText
}, r.getAllResponseHeaders()))
}
}
,
r.onload = o(),
a = r.onerror = r.ontimeout = o("error"),
void 0 !== r.onabort ? r.onabort = a : r.onreadystatechange = function() {
4 === r.readyState && C.setTimeout(function() {
o && a()
})
}
,
o = o("abort");
try {
r.send(i.hasContent && i.data || null)
} catch (e) {
if (o)
throw e
}
},
abort: function() {
o && o()
}
}
}),
NOTE: It consistently disappears after the 5th time hitting that breakpoint.
This happens regardless of whether I have any shapes on the diagram. (I've tried with both existing diagrams and blank [new] diagrams.)
I'm going to investigate further, but if you have any suggestions, I'm open to whatever insight you might offer.
Pages: [1] 
Errors after upgrading from 3.2.2 to 4.2.0 (Read 613 times)
