I think, it would by great, to have option to chunk files into smaller pieces. It allows better uploading big files. When using PHP backend, there is max post size restriciton. I think, chunking method is faster etc.
There appear to be a number of options missing from this control that keep it from being really powerful. For example: - there does not appear to be a method in which to access the files currently selected, in order to remove one. - If you want to limit the file types selected, you have to cancel the entire selection event, which will only piss off end users. -The only way to show a "remove" button is to have something post back to the server, which makes no sense if AutoUpload is false. - If you want to clear the list of uploaded items, you have to use jQuery to remove the LI's (WTF?) My proposed changes: - Have a Remove button regardless of whether there us a Remove URL set or not. If there is not a Remove URL set, disable the Remove/cancel button while files are being uploaded. - Add a clear() method to remove all files, uploaded or otherwise. - Add a getFiles() method to get a list of all in-memory files being managed. - Add a remove(file) method, so that files that were accidentally selected can be removed in the Select event handler without having to choose between adding a server-side call and pissing off the end user. - Add a setFileTypes() method that lets you pass in an array of file types to accept. All others will be automatically removed from the collection. - Make the Drag&Drop capability set the drop zone visibility by default. You can manage that in jQuery without making me add more styles manually. Thank you for your consideration.
Add support to the Upload widget to upload files to an OData service, for instance to add attachments to SharePoint list items using SharePoints OData service. At the same time it would be good to be able to specify the urls for the Upload widget in an upload-datasource in a view model to which the Upload widget is databound, basically separate the uploading from the widget. That way you can choose to use an OData upload-datasource or a multipart/form-data upload-datasource. Obviously this OData upload-datasource may only be supported in browsers that support the HTML5 file api.
i really needed Upload By Folder like goolge drive uploader. i hope kendo will add that feature.
Provide the image preview option for kendo upload.
Upload for MVC lucks upload in chunks feature as upload for ajax. So it is impossible to upload large files (like more than technical limit for asp.net in 4Gb). In my current project with 360 degrees videos where files might be 10+ Gb it is vital.
When we have a scenario with the Upload component configured with a chunk upload configuration, we cannot upload a file that contains an apostrophe in its name.
The selected for upload file is not being uploaded.
** If the above scenario is tested in an MVC project, the error returned from the server is "A potentially dangerous Request.Form value was detected from the client". Below you will find a test project:
ChunkUpload.zip
The files selected for upload should not have any issues with their uploading, no matter if there is an apostrophe in their name or not.
If we have a upload control with simple validation on allowed extensions and upload 50 files, the "k-upload-status" element prematurely gets set to "Done" once it finds a file type that is not allowed. If a user is not paying attention they could think that the upload is complete. It seems silly to mark an entire queue of files as "Done" after the first failure while uploading multiple items and while items are still uploading. While the upload may technically be "done" it really failed and should say "Partially done" or some other message than "Done". Also, placing an exclamation icon next to done is not very clear when an file does legitimately fail. The icon needs to be more prevalent and have a tooltip to describe it further. Most of my users in production have not noticed the icon and have thought that the upload completed. This is especially a problem if a user is uploading thousands of files and does not scroll down during/after upload.
When we upload files with the Kendo Upload, it would be nice to upload them sequentially, in separate requests
Scenario: Imagine you implemented upload widget within grid and it can upload multiple files. After you upload, you realize you need to delete one of the uploaded file. Currently you cannot choose to delete either of the uploaded multiple files in edit mode. It would be nice to display preuploaded files in upload widget when the grid is in edit mode, so that user can delete the files that are not necessary anymore.
It would be nice to have xhr in upload's remove event handler since sometimes we need to modify/add http headers on request.
The upload control takes up a lot of space on the web page when you upload a lot of files. As each file completes, I want an easy way to remove those files. Ideally, a configuration option to automatically remove completed files otherwise a function to remove the file from the list from within the Success event.
can refer http://tus.io/demo.html for resumable file upload. and http://www.dropzonejs.com/ for drop zone. its beautiful and important plugin. hope fully kendo can intergrated.
When a user clicks the Kendo UI Upload's "select files" button in Firefox, they will need to click twice.
The first click should trigger the menu to open for uploading files.
Filter just certain types of files by extension (.csv, .doc, .jpg, etc.).
The suggested way to omit the Remove button is to not provide a Remove URL/Action. However this breaks the list of the async upload such that the list doesn't get cleared with each new upload. Since its an async upload that automatically uploads, there no point in accumulating a list of uploads. Whether or not you expose a remove button shouldn't be tied in any way to the clearing of the list when a new upload is made. That should only affect the availability of a remove button. At the very least you could provide some documentation on this quirky behavior. Instead its random walk of, ok if I change this property what happens, how about this one, how about both, and whirl away a few hours screwing around with unpredictable behaviors. @(Html.Kendo().Upload() .Name("pdfFiles") .Multiple(false) .Async(configuration=> configuration .AutoUpload(true) .Save("UploadTemporaryPdf", "StatementOfCredit") //.Remove("RemoveTemporaryPdf", "StatementOfCredit") ) .Events(events=> events .Select("onUploadSelect") .Success("onUploadSuccess") .Error("onUploadError") ) .HtmlAttributes(new { accept = "application/pdf" })
Please resolve this, as this is a pain point for our customers.
The Upload popup is not opened if you click near the button's border
The select popup does not open
The select popup should open
When the 'Select files' button and the 'Submit' button are rendered close to each other and the 'Submit' button is clicked the 'Select files' popup is opened. Thus, the selected file could not be submitted. The issue appears on IOS in Safari and Chrome.
The 'Select files' popup is opened.
In case there are selected files when the submit button is clicked, the files should be submitted. The 'Select files' popup should not be opened.
If you destroy the Upload after uploading a file, a JS error occurs in the console.
An error is thrown after destroying the component
No errors should be thrown