After recently upgrading versions of Kendo Mobile, I get this error on a simple button widget:
<a data-role="button">Back</a>
Clicking on it produces the following error:
Uncaught TypeError: Cannot read property '0' of undefined kendo.all.min.js:41
o.extend._mouseup kendo.all.min.js:41
arguments.length.t.(anonymous function) kendo.all.min.js:10
b.event.dispatch jquery-1.9.1.js:9593
v.handle
I am using Kendo Mobile v2013.2.910 with jQuery 1.9.1. My console window is blowing up with red text now... Any thoughts?
Related
I am using Kendo version: "2016.1.112" . And google Chrome Version 50.0.2661.94 m
I am facing error .its console error Uncaught ReferenceError: $0 is not defined
it is referencing in below kendo script:
setTimeout(function(){
// just in case devtools opens as a result of "Inspect
// Element", make sure we update window.$K if necessary
if ($0) {
tools.inspectKendoWidget($0);
}
}, 300);
That issue is due the the KendoUI inspector Extension which you have in your chrome as extension. Either remove it or wait for an update from the Telerik team to fix their extension.
However that error should not have any impact on your application.
I disabled the inspector and the error has gone.
Go to extensions option menu and uncheck the inspector.
I have started to do this example
http://docs.telerik.com/kendo-ui/controls/data-management/grid/adaptive
but I get an error Uncaught TypeError: $(...).kendoGrid is not a function
I think its because the AppBuilder Template just references Kendo Core and not
kendo.all.min.js still looking into it but figured someone else might have some
pointers
I am new to kendo ui mobile wanted to know why I am getting this specific error:
Uncaught TypeError: Cannot read property 'useNativeScrolling' of undefined
The code in the view is as follows:
<ul kendo-mobile-list-view
k-data-source="xyz.list"
k-template="xyz.Template"
k-on-click="xyz.previewList(kendoEvent)"
k-use-native-scrolling="true"
data-endless-scroll="true"
></ul>
This seems like a bug we introduced in one of our releases - please try upgrading to the current one (Q1 2014 SP1).
Add the latest kendo cdn.
Add this to your project.
<script src="http://cdn.kendostatic.com/2014.1.318/js/kendo.all.min.js"></script>
I solved this problem with this latest cdn
I am looking at KendoUI for a js app that will run in house. I download the kendoui (either opensource or the latest from them) and follow these very simple directions:
http://docs.kendoui.com/getting-started/introduction
Doing exactly as they suggest results in a js error of (same js error if I run the files through a local apache server or directly as file:// in Google Chrome).
Uncaught SyntaxError: Invalid regular expression: missing /server/js/kendo.web.min.js:10
Uncaught TypeError: Object [object Object] has no method 'kendoDatePicker'
What gives?
The js files are found and loading. But it chrome complains about
GET http://0.0.0.0:7773/server/js/jquery.min.map 404 (Not Found)
Perhaps these instructions are old?
Update:
It appears that the js files in the Kendo downloads are corrupt today. It works if I either link directly to the Kendo CDN, or if I download web.ui from github. Its not my zip expansion software (OS X 10.8), as the query 1.9.1 included in the kendo download works perfectly.
This is due to a known issue. Long story short you need to download the bits again and use the updated JavaScript files.
In my local dev environment, any time I try to add a widget to a CMS page I get a javascript error: Result of expression 'el' [null] is not an object.
Does anyone know what might cause that?
Magento 1.5.1
Mac OS X 10.6.7
Apache 2.2.17
Safari 5.0.5 / Firefox 3.5.9
In Chrome 12.0.742.100, the error is:
The page at localhost.com says:
Cannot read property 'selectionStart' of null
Has anyone seen this before?
I have got the exact same error on a v1.5.1 CE Magento system when I choose to add via the large orange 'Add Widget' button to a static block or cms page.
However, when I add a widget via the WYSIWYG editor, the widget is added as expected and I do not receive the 'el null' error.
A strange bug that will hopefully be fixed in v1.6.