OWF.ready() events not getting called

[cbenn...@hotmail.com]

Occasionally (< 5% of the time) an error will occur during OWF initialization that will prevent any function we've registered with OWF.ready() from getting called. The error from the console is:

TypeError: this.widgetEventingController.subscribe is not a function
https://cma.gcss.ms.northgrum.com/owf/js-min/owf-widget-min.js
Line 1

Note that this subscribe call is made from OWF itself. When this error occurs, OWF falls out of its init process and the OWF.ready functions are not called. This prevents any of our subscriptions (which are all called from OWF.ready()) from getting registered.

 

 

I was  eventually able to reproduce the error in my dev environment, so we could get an actual line number in non-minified code:

TypeError: this.widgetEventingController.subscribe is not a function

https://localhost:8443/owf/js-min/owf-widget-debug.js

Line 19130

 This appears to happen while OWF is initializing drag and drop. Since we’re not using drag and drop I figured maybe we could still fix things after the fact, as long as Eventing is working. However, after prototyping this, once the OWF error occurs, OWF is permanently broken. The OWF.Eventing object is empty, and we have to reload the widget to fix it, so I don’t see a way to work around the issue.

 

Any ideas, or has anyone else experienced this?

Thanks,

Cheryl Lewis

[gren...@gmail.com]

I am having a similar issue.

owfdojo.addOnLoad(function() {

alert('WORKS');

OWF.ready(function(){

alert('DOES NOT WORK');

});

});

[steve....@omicronresearch.com]

I'm seeing this as well.  We've got one case in which I can reproduce the error every time.  Another path will never cause the error.  I haven't been able to diagnose the different paths to see why the OWF initialization process is different.

[Al]

We had the same problem.  Our solution was to use jQuery instead of the owfdojo.

So, replace owfdojo.addOnLoad() with $(document).ready().

Hope this helps.

[jok...@gmail.com]

Were either of you able to determine the root cause of this behavior? 

Also, any other solutions besides the jQuery one mentioned? Maybe a OWF version upgrade?

I'm running into the same issue on OWF 7.0.0. I was able to reproduce the behavior in all three browsers IE/FF/Chrome

but it happens sporadically and is more frequent with IE and on machines with lower memory...happens almost 99% of the time on the lower end machines.  

Thanks a lot,

John