4.4: Unable to get property 'isValid' of undefined or null r

Scheduler Javascript
#1

When I’ve dhtmlxscheduler_key_nav.js loaded I get this error:

jQuery.Deferred exception: Unable to get property 'isValid' of undefined or null reference TypeError: Unable to get property 'isValid' of undefined or null reference at Anonymous function (http://informatica5/girh_gt/assets/dhtmlx/dhtmlxScheduler/ext/dhtmlxscheduler_key_nav.js?v=DESENVOLUPAMENT:86:386) at z (http://informatica5/girh_gt/assets/dhtmlx/dhtmlxScheduler/dhtmlxscheduler.js?v=DESENVOLUPAMENT:39:477) at obj.callEvent (http://informatica5/girh_gt/assets/dhtmlx/dhtmlxScheduler/dhtmlxscheduler.js?v=DESENVOLUPAMENT:39:230) at scheduler.render_view_data (http://informatica5/girh_gt/assets/dhtmlx/dhtmlxScheduler/dhtmlxscheduler.js?v=DESENVOLUPAMENT:164:23) at scheduler.update_view (http://informatica5/girh_gt/assets/dhtmlx/dhtmlxScheduler/dhtmlxscheduler.js?v=DESENVOLUPAMENT:116:32) at scheduler.updateView (http://informatica5/girh_gt/assets/dhtmlx/dhtmlxScheduler/dhtmlxscheduler.js?v=DESENVOLUPAMENT:119:15) at scheduler.setCurrentView (http://informatica5/girh_gt/assets/dhtmlx/dhtmlxScheduler/dhtmlxscheduler.js?v=DESENVOLUPAMENT:119:124) at scheduler.init (http://informatica5/girh_gt/assets/dhtmlx/dhtmlxScheduler/dhtmlxscheduler.js?v=DESENVOLUPAMENT:83:80) at init_scheduler (http://informatica5/girh_gt/index.php/planificador_unitat:3024:9) at Anonymous function (http://informatica5/girh_gt/index.php/planificador_unitat:3004:9) undefined jquery-3.1.1.min.js (2,31469)

#2

Hi,
can you please PM me a link to some kind of demo?
The error doesn’t seem to happen in our samples (e.g. docs.dhtmlx.com/scheduler/sample … lugin.html ), so having a way to reproduce it would help a lot.
If it’s not possible - what extensions do you use? Could you also share some code that you use to initialize scheduler, configs, etc.

#3

Hello,

I had the same problem in 4.4 when dhtmlx dhtmlxscheduler_key_nav.js is loaded.
It looks like it happens more under IE than other browsers.

Anyways this modification seems to do the trick and fixed the problem on our side
Make sure you do it before calling scheduler.init

       /* Dirty hack to fix key_nav bug in 4.4*/
        scheduler.$keyboardNavigation.dispatcher._old_getActiveNode = scheduler.$keyboardNavigation.dispatcher.getActiveNode;
        scheduler.$keyboardNavigation.dispatcher.getActiveNode = function(){
            var node = this._old_getActiveNode();
            if(!node)
            {
                this.setDefaultNode();
                return this.getDefaultNode();
            }
            return node;
        };