Completed
Last Updated: 15 Mar 2019 08:33 by ADMIN
Created by: Alex Kapitanovskyy
Comments: 1
Category: AsyncUpload
Type: Bug Report
0
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.
Completed
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">
        </telerik:RadAsyncUpload>

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:RadAsyncUpload>
        <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)


Completed
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.

Completed
Last Updated: 14 Aug 2018 11:24 by ADMIN
ADMIN
Created by: Rumen
Comments: 0
Category: AsyncUpload
Type: Bug Report
0
The drop zone and the custom drop zones are shifted below their expected positions in Edge 40.

Check the following video demonstration https://www.screencast.com/t/2m8SxR8jbwb.

The problem is reproducible in the http://demos.telerik.com/aspnet-ajax/asyncupload/examples/draganddrop/defaultcs.aspx demo.
Approved
Last Updated: 24 Apr 2017 13:26 by ADMIN
ADMIN
Created by: Vessy
Comments: 0
Category: AsyncUpload
Type: Bug Report
0
File drag and drop is broken in MS Edge Creator's Edition. Reproducible in the following demo:

http://demos.telerik.com/aspnet-ajax/asyncupload/examples/draganddrop/defaultcs.aspx

Approved
Last Updated: 02 Nov 2016 00:47 by Polymorphic Solutions
Approved
Last Updated: 14 Jul 2016 08:20 by ADMIN
Approved
Last Updated: 06 Jul 2016 13:49 by ADMIN
Completed
Last Updated: 05 May 2016 11:46 by ADMIN
Completed
Last Updated: 04 Apr 2016 13:22 by ADMIN
Approved
Last Updated: 07 Jan 2016 16:46 by ADMIN
Completed
Last Updated: 30 Nov 2017 16:28 by ADMIN
Workaround: 

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>");

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

        if (this._isManualUpload())
            $content.addClass("ruUploadOnHold");

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

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

Sys.Application.add_load(encodeRowContent);

Won't Fix
Last Updated: 01 Oct 2015 14:56 by ADMIN
Workaround:
Set DisablePlugins="true" or
set RenderMode="Lightweight"
Under Review
Last Updated: 27 Jun 2016 15:19 by ADMIN
Upgrading to UI for ASP.NET AJAX Q2 2015 (2015.2.729.45) sets requestLimits maxAllowedContentLength in web.config to 

<requestLimits maxAllowedContentLength="0" /> <!--8MB Max upload-->

resulting in errors like "PRM_ServerError" on postbacks.
Declined
Last Updated: 01 Oct 2014 12:43 by Nick
ADMIN
Created by: Dimitar
Comments: 1
Category: AsyncUpload
Type: Bug Report
3
 RadAsyncUpload does not upload files in iOS 8 Safari. After selecting a file/files for upload, their upload remains as pending and never reaches the end of the process.
Note: there is a known iOS 8 Safari issue with <input type="file" />
Completed
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.
good.

reload.
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
bad.
Declined
Last Updated: 12 Aug 2015 16:01 by Ryan
when deleting files from radasyncupload via the "built-in" delete button, both the upload_removing and upload_removed events are fired. However, when deleting files via the api, only the uploadRemoved event is fired.

to reproduce: 
1. run attached web form. select file for upload. click remove button. view console. note console entries have text "filename in UPloadRemoving.." as well as "filename in UploadRemoved...". Good

2. click the "delete via api" checkbox to enable. select another file. view console. Note console entry only has text "filename in UploadRemoved..." bad.
Completed
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:
document.pdf

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.
1 2