Plugin Not Allowing Saving After Update

Hey,

Already reached out to customer support on your website about this issue, but there has been no follow up since my original email.

Experiencing an issue with the plugin after updating to the latest version and purchasing a PRO license. The plugin will not allow me to ‘Save’ any of my tables. The save button is greyed out. Managed to move a copy of my production environment to staging on WPEngine, and the plugin does not have the same issue on the staging environment…

Opened my console log on production and noticed the following JS error:

tables.editor.js?ver=1.9.92:850 
Uncaught TypeError: this.plugin.matrix.needRecalc is not a function
    at t.default.renderWithRecalc (tables.editor.js?ver=1.9.92:850)
    at Object.<anonymous> (tables.editor.js?ver=1.9.92:552)
    at i (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,jquery-ui-core,farbtastic,utils,moxiejs,plupload,jquery-ui-widget,jquery-ui-mouse&ver=5.4:2)
    at Object.fireWith [as resolveWith] (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,jquery-ui-core,farbtastic,utils,moxiejs,plupload,jquery-ui-widget,jquery-ui-mouse&ver=5.4:2)
    at Object.e.<computed> [as resolve] (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,jquery-ui-core,farbtastic,utils,moxiejs,plupload,jquery-ui-widget,jquery-ui-mouse&ver=5.4:2)
    at Object.<anonymous> (tables.model.js?ver=1.9.92:85)
    at i (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,jquery-ui-core,farbtastic,utils,moxiejs,plupload,jquery-ui-widget,jquery-ui-mouse&ver=5.4:2)
    at Object.fireWith [as resolveWith] (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,jquery-ui-core,farbtastic,utils,moxiejs,plupload,jquery-ui-widget,jquery-ui-mouse&ver=5.4:2)
    at Object.e.<computed> [as resolve] (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,jquery-ui-core,farbtastic,utils,moxiejs,plupload,jquery-ui-widget,jquery-ui-mouse&ver=5.4:2)
    at Object.<anonymous> (core.js?ver=1.9.92:129)

Staging does not show this error in the console. Is there a reason for this error happening only on my production environment?