Last Updated: 07 Oct 2013 08:47 by ADMIN
Created by: Hristo Valyavicharski
Comments: 0
Category: AsyncUpload
Type: Bug Report

Last Updated: 30 Nov 2017 16:28 by ADMIN

function encodeRowContent() {
    var asyncUpload = $find('<%= RadAsync_FileUpload.ClientID%>');
    var $ = $telerik.$;
    asyncUpload._updateRowContent = function (row, inputValue) {
        var $progress,
            $content = $("<span class='ruUploadProgress'>" + $telerik.htmlEncode(this._getFileName(inputValue)) + "</span>");

                .addClass("ruFileLI ruUploading")
                .prepend("<span class='radIcon'></span>");

        if (this._isManualUpload())

        if (this._enableInlineProgress) {
            $progress = $('<span class="ruFileProgressWrap"><span class="ruFileProgress"></span></span>');

        $('.ruFakeInput, .ruBrowse', row).remove();
        $(".ruFileWrap", row).append($content); // Replace fake input


Last Updated: 20 Aug 2014 14:25 by ADMIN
Last Updated: 09 Apr 2015 10:16 by ADMIN
Last Updated: 09 Apr 2019 15:06 by ADMIN

Documentation says Firefox should be ok with LastModifiedDate, but it's not.  It's consistently being set to 1/1/0001 12:00:00 AM, which is not useful.

Happens in any RadAsyncUpload example if you look at the value for LastModifiedDate in the AsyncUploadedFile objects.

Works fine in Chrome, Edge.  Fails in Firefox for Mac or Windows.

Last Updated: 19 Feb 2020 12:55 by ADMIN
Release R1 2020 SP1
Created by: Jeff Cuddigan
Comments: 0
Category: AsyncUpload
Type: Bug Report

This issue is observed only in R1 2020. The solution is to not disable the FileAPI.

Reproduction steps:

    Telerik.Web.UI.RadAsyncUpload.Modules.FileApi.isAvailable = function () { return false; };
    Telerik.Web.UI.RadAsyncUpload.Modules.Flash.isAvailable = function () { return false; };
    Telerik.Web.UI.RadAsyncUpload.Modules.Silverlight.isAvailable = function () { return false; };
<telerik:RadAsyncUpload runat="server" ID="RadAsyncUpload1" ></telerik:RadAsyncUpload>

Last Updated: 08 Mar 2019 09:39 by ADMIN
When the ChunkSize of RadAsyncUpload is set the files are not fully uploaded. A sample excel file to reproduce the issue is attached to this reply.
Temporary fix:
Remove the ChunkSize setting of the AsyncUploade:

        <telerik:RadAsyncUpload ID="UploadFile" runat="server" MultipleFileSelection="Automatic"
            OverwriteExistingFiles="true" ReadOnlyFileInputs="true" InputSize="45" EnableViewState="true" TargetFolder="~/UploadedFiles">

Steps to reproduce:

1. Run the following configuration and upload the attached to this item file
        <telerik:RadAsyncUpload ID="UploadFile" ClientIDMode="AutoID" runat="server" MultipleFileSelection="Automatic"
            OverwriteExistingFiles="true" ReadOnlyFileInputs="true" ChunkSize="3145728" InputSize="45" EnableViewState="true" TargetFolder="~/UploadedFiles">
        <telerik:RadButton runat="server" Text="Upload"></telerik:RadButton>

Expected: An 11MB file is uploaded
Actual: An 8MB file is uploaded (the last chunk part is missing)

Last Updated: 15 Mar 2019 08:33 by ADMIN
Created by: Alex Kapitanovskyy
Comments: 1
Category: AsyncUpload
Type: Bug Report
After the update from version 2018.2.710 to 2019.1.2015 the files bigger than 2 MB are cut off (up to 2 MB) and broken during the upload.
Last Updated: 12 Aug 2015 15:51 by Ryan
when deleting files from radasyncupload via the "built-in" delete button, "get_fileName()" method in both the upload_removing and upload_removed events returns correct data. However, when deleting files via the api, the get_fileName() method returns bad content.

built-in button something like:

api something like:
document.pdf<span class="ruFileProgressWrap"><span class="ruFileProgress"></span></span>

to reproduce: 
1. run attached web form. select file for upload. click remove button. view console. all good.

2. click the "delete via api" checkbox to enable. select another file. view console. bad.
Last Updated: 12 Aug 2015 15:46 by Ryan
when files are deleted via the user interface, this "frees up" the max file count for additional files to be uploaded. When files are deleted via API, the deleted files are still counted against the maxfilecount, and are not "freed up"

to reproduce:
run the attached web form.
do not select "delete via api" checkbox
add and remove a number of files.

do not select "delete via api"
upload file A
select "delete via api"
upload file A one more time (note it will be deleted via api before it actually gets uploaded)
deselect "delete via api"
upload file B
note you can no longer upload files, allthough only 2 have been uploaded and maxfilecoutn is 3
Last Updated: 04 Apr 2016 13:22 by ADMIN
Last Updated: 05 May 2016 11:46 by ADMIN
Last Updated: 14 Aug 2018 11:24 by ADMIN
Created by: Rumen
Comments: 0
Category: AsyncUpload
Type: Bug Report
The drop zone and the custom drop zones are shifted below their expected positions in Edge 40.

Check the following video demonstration

The problem is reproducible in the demo.