Uncaught TypeError: Cannot read property 'prototype' of undefined

Uncaught TypeError: Cannot read property 'prototype' of undefined

guyclairboisguyclairbois Posts: 9Questions: 1Answers: 0

I'm having what seems to be a serious issue with the DataTables Editor. I've stripped it down to only the dataTables.editor.min.js file. I'm sure I'm using the purchased version.

Whenever I include it in a page (in this case VisualForce, part of Salesforce.com) I get the following error in the console (even without adding anything else on the page):
dataTables.editor.min.js:586
Uncaught TypeError: Cannot read property 'prototype' of undefined

This is line that's causing the issue:
(f.DateTime.prototype,{destroy:function(){thisE7;this[(J1d.g8+J1d.h4I+Z0I)](o6+k3+J1d.M5I+J1d.V8+p2I+N2I)(J1d.h4I+d9).empty();this[h1w][J5g]S9w;}

This used to work fine before (last time I checked it was 2 weeks back)..
Do you have any clue what might be causing this?

These are the scripts that I'm loading:

<script type="text/javascript" language="javascript" src="//cdn.datatables.net/1.10.12/js/jquery.dataTables.min.js"></script>
<script type="text/javascript" language="javascript" src="//cdn.datatables.net/buttons/1.2.1/js/dataTables.buttons.min.js"></script>
<script type="text/javascript" language="javascript" src="//cdn.datatables.net/select/1.2.0/js/dataTables.select.min.js"></script>
<script type="text/javascript" src="{!URLFOR($Resource.datatables_Editor, '/js/dataTables.editor.js')}"></script>

This question has an accepted answers - jump to answer

Answers

  • allanallan Posts: 63,812Questions: 1Answers: 10,516 Site admin
    Answer ✓

    That looks like the obfuscated trial version of Editor. I suspect that file is the trial file and it has expired, thus it is throwing fairly useless errors.

    If you download the licensed version and replace your current file with the new one, it should work. You may need to clear your browser's cache and any other cache you have (e.g. CloudFlare).

    Allan

  • guyclairboisguyclairbois Posts: 9Questions: 1Answers: 0

    Switched back to version 1.5.5 which resolved the issue for me..

This discussion has been closed.