3 Answers, 1 is accepted
The Upload, and Kendo UI widgets in general, do not support initialization over an existing widget. The original DOM structure is not restored and side effects are almost guaranteed.
Our recommendation is to clean-up the old widget using kendo.destroy and create the source markup before each initialization. For example:
<div id="container">
<input id="upload" type="file" />
</div>
<script>
$(function() {
var container = $("#container");
$("#upload").kendoUpload({ async: { saveUrl: "/" } });
kendo.destroy(container);
container.html("<input id=\"upload\" type=\"file\" />");
$("#upload").kendoUpload({ async: { saveUrl: "/" } });
});
</script>
(Live demo on jsBin)
I hope this helps.
Kind regards,
the Telerik team
Rank 1
We are using the RadAjaxManager and re-running the initialization code after postbacks, since they don't work well with other controls. It worked fine until the Q1 release though, which is causing the drop areas to get nested on postback, instead of it just initializing them again.
I'm not sure how this is going to play with the RadAjaxManager. My recommendation is to move the initialization code for Kendo widgets outside of dynamically updated zones.
If this is not an option then perhaps you can share a sample page so we can debug it?
Tsvetomir Tsonev
the Telerik team