Skip to content
This repository has been archived by the owner on Nov 20, 2018. It is now read-only.

Releases: FineUploader/fine-uploader

Hotfix: missing null-check in uploader send method

10 Apr 19:55
Compare
Choose a tag to compare

Symptom: error with message of Cannot set property 'loaded' of undefined inside of the send method of upload.handler.controller.js.

Fixed in aef42d0.

Hotfix: Various null-value guards

10 Apr 16:55
641577a
Compare
Choose a tag to compare

Much more flexible upload support for traditional endpoints

09 Mar 05:55
5be9ba1
Compare
Choose a tag to compare

This is the biggest release in a long time, closing out a ton of long-standing cases, and making it much easier for developers to integrate Fine Uploader into their own servers. This was developed and tested over the course of 4+ months on a large closed-source project.

From the commit message notes, the following is included here:

  • Local dev/testing ports 3000/3001 clash with my local env, and possibly others - moving to 4000/4001.

  • returned onUploadChunk promise can override method, params, headers, & url

  • promissory onUpload callback

  • always ensure test server are killed either on test start or stop

  • don't try to kill test server on CI before tests start

  • option to allow upload responses without { "success": true }

  • allow default params to be omitted from upload requests

  • don't fail upload w/ non-JSON response when requireSuccessJson = false

  • more flexible chunking.success request support

  • add .editorconfig (can't believe this didn't exist until now)

  • Allow custom resume keys and data to be specified.

  • include customResumeData in return value of getResumableFilesData API method

  • add isResumable public API method

  • introduce chunking.success.resetOnStatus to allow FU to reset a file based on chunking.success response code

  • new API method: isResumable(id)

  • Allow onUpload resolved Promise to pause the file.
    Use case: When onUpload is called, you make a request to your server to see if the file already exists. If it does, you want to let your user decide if they want to overwrite the file, or cancel the upload entirely. While waiting for user input you don't want to hold a spot in the upload queue. If the user decided to overwrite the file, call the continueUpload API method.

  • Allow per-file chunk sizes to be specified.
    chunking.partSize now accepts a function, which passes the file ID and size

  • feat(beforeUnload): new option to turn off beforeUnload alert during uploads

  • feat(features.js): auto-detect folder support

  • Allow access to Blob when file status is still SUBMITTING

  • docs: options, API, and events doc updates

  • added qq.status.UPLOAD_FINALIZING - don't cancel or pause in this state

closes #848
closes #1697
closes #1755
closes #1325
closes #1647
closes #1703

Hotfix: Reported directory path (qqpath) is wrong if file name occurs in one of the parent directory names

02 Mar 04:42
Compare
Choose a tag to compare

Hotfix: Auto-retry count is not reset on successful chunk upload

27 Jan 02:54
Compare
Choose a tag to compare

Hotfix: Template is duplicated on `reset()`

23 Dec 05:12
Compare
Choose a tag to compare

The issue is described in #1945 and fixed in #1958. This appears to be a regression from #1903, which was released in v5.15.1.

First release candidate for 5.16.0, focusing on more flexible upload workflow support

04 Jan 19:47
Compare
Choose a tag to compare

Hotfix: Firefox flickers on drag

18 Nov 03:38
Compare
Choose a tag to compare

First reported in #1862 and fixed in #1946. Heavily requested fix, and now it's live!

Hotfix: Non-files trigger DnD logic

08 Nov 22:50
Compare
Choose a tag to compare

Fixed in #1819, first reported in #1588. Now, non-files dragged into the scope of the DnD module should be ignored.

S3 SSE headers & <table> handling

06 Nov 04:33
Compare
Choose a tag to compare

UI

First reported in #1246 3 years ago (!), #1903 finally provides support for <table> elements inside of the UI templates.

S3

You can now use S3 server side encryption with your own KMS key. First reported in #1803 and addressed in #1933.

build

A minor issue in the build prevented some Makefile recipes from completing in Windows environments. Fixed in #1828.