Stable version 3.2.0 (Compatible with OutSystems 11)

Other versions available for 10 and Older

Uploaded

on 7 Nov (13 days ago)

Multi Uploaders

4.6

(62 ratings)

We picked this asset for you. Give it a try.

Reactive Multiple File Upload

Compatible with OutSystems 11

Details

Allow you to upload multiple files in one upload form or using drag and drop functionality.

HTML 5 version - Allow you to upload multiple files in one upload form or using drag and drop functionality (https://github.com/valums/file-uploader).

Feature List

This widget makes possible to drag and drop multiple files and instantly start the upload process.

The files are stored on temporary entities, has a timer to delete the files.

If dont like to use the drag and drop, you can just use a button to do the same effect.

Fully CSS editable.

Main Benefits

Possibility to upload multiple files

System Requirements and Limitations

- OutSystems V9.0.1.x or later

- Optimized for Mozilla Firefox, Google Chrome and IE10+

Limited functionality on browsers non compliant with HTML5 FILE API (file corruption not detected)

Release notes (3.2.0)

Changed the Session Variables to a Temporary Database Cache in order to support more than one Block per page:

The Allowed File Extensions are now validated both on client-side and server-side, being stored on a Temporary Database Cache instead of a input parameter to the File Process URL;
The Upload File Size Limit is now validated both on client-side and server-side, being stored on a Temporary Database Cache.

License (3.2.0)

BSD-3 license (https://opensource.org/licenses/BSD-3-Clause)

Reviews (6)

17 May

in version 3.1.0

Very useful component!!

2024-01-02

in version 3.0.3

This component proves to be highly useful, notwithstanding the fact that our team discovered a vulnerability related to XSS (cross-site scripting). Consequently, we implemented an update on the ProcessFiles screen to enhance the security, as described below.

- First we added a SanitizeHtml action (from Sanitization) with the qqfile on the html input. [html = qqfile]
-Then we encoded the output URL from SanitizeHTML action.
[qqfile = EncondeURL(SanitizeHtml.SanitizedHtml)]

This was made in the beginning of the preparation action and the vulnerability was resolved.

I hope this helps!

Answer from the owner

2024-01-16

in version 3.0.3

Thank you for addressing this issue Duarte. A new version has been released where we have implemented your solution.