How to check the datatable version I am using - datatable

I am using the following function to get the version of Datatable I am using :
alert($.fn.DataTable.versionCheck());
But I am getting error as :
$.fn.DataTable.versionCheck is not a function
What is wrong in my code?

The code you are using is designed to check the current version number against the provided version number, for example:
$.fn.dataTable.versionCheck('1.9.2')
will check if the version number you are using matches 1.9.2. You are not providing a parameter to the function.
I believe the $.fn.dataTable.versionCheck() function was added in version 1.10, so if you are running an older version that may explain why you are getting your error message.
You can use the following code to get the version number:
$(document).ready(function(){
$('#myTable').DataTable();
var versionNo = $.fn.dataTable.version;
alert(versionNo);
});
Please see demo here. Hope it helps.

I know this is old, but you can just go to your browser console and run:
$.fn.DataTable.version

Related

Laravel 6 version using compact

What does Laravel 6 version using a
return view(view: 'index', data: compact(varname: 'string'));
I was following a tutorial, but the one I downloaded it seems it's different codes on the tutorial and always gets me an error. I downloaded a Laravel 6.11.0 version. I'm a beginner on this framework hope there's someone could understand and I want to learn about this laravel framework.
here is the tutorial link
https://www.youtube.com/watch?v=98ChVWjI6KI&list=PLpzy7FIRqpGC8Jk6gyWdSVdxCVXZAsenQ&index=5
You should just use:
return view('index', compact('string'));
Those view:, data: and varname: are parameter name hints from PHPStorm IDE and not the actual code.

Could not load file or assembly 'System.Net.Http.Formatting, Version=5.1.0.0'

I'm facing this issue while trying to call my bot via directline:
As you can see on the image below, my webapi bot project is using the version 5.2.4.0, but according to the log error, the Microsoft.Bot.Conector is trying to use an old version of it ?
Does anybody have a clue on how can I solve it ?
Adding a binding redirection as #Eric suggested worked fine.

async/await function error in Babeljs version 6.16.0

I'm normally using async/await and syntax-async-functions. But today when I upgraded to version 6.16.0, then my function async/await got error like below. I dont use for-of-await. Now dont know how to config label to write async/await normally?
Tks.
Error: /usr/src/server.js: You gave us a visitor for the node type "ForAwaitStatement" but it's not a valid type

Processing 3: NullPointerException using PTreeMappa

I'm using Processing 3 for generating a Treemap.I installed gicentreUtils and placed TreeMappa file in the library folder of Processing. I'm getting nullPointerException in line:
pTreeMappa = new PTreeMappa(this).
The full code can be found in this
link
Can someone please let me know how to resolve this error.
Thanks
It seems the TreeMapa library hasn't been updated in a few years and internally it may use some Processing code that changed from version 2.x to 3.x (like windows/frames/etc.) which is why the error might occur.
I advise using TreeMapa with Processing 2.2.1 available on the Processing Downloads page

parse.com cloud code set version?

I am new to parse and I am trying to figure out how to handle the version number.
I have been deploying some cloud code a bunch of times. So when I last deployed it gave me this message:
Uploading source files
Finished uploading files
New release is named v18 (using Parse JavaScript SDK v1.2.19)
So I thought I could go and hit:
https://api.parse.com/18/functions/someFunctionIWrote
So there I tried to use version 18 because of what I saw after deploying. That does not work and it returns a 404.
So, then I tried to hit:
https://api.parse.com/1/functions/someFunctionIWrote
this works and return the JSON I wanted.
So, what am I missing here?
I thought that every time I deploy the version would match. Do I need to specifically go in and change the current version somehow?
Can somebody help understand how to think about this correctly?
Thank you
If you ran a "parse deploy" it put v18 up there for you the URL stays the same.
The version in cloud can be verified in the terminal by typing: "parse releases"

Resources