Custom error messages for S3 signature requests

In #1724, the ability to pass a custom error message to Fine Uploader from your signature endpoint was added. Simply include an error property in your JSON response along with an appropriate error response status code, and Fine Uploader will make use of this error message in the UI, and pass it along to error even handlers as well. For more details, please see the server-side documentation page at http://docs.fineuploader.com/branch/master/endpoint_handlers/amazon-s3.html.

Optionally allow empty files to be uploaded

Implemented in #1710 and initially requested 3.5 years ago back in #903, this has finally landed in a released version of Fine Uploader.

By default, empty files are rejected, as always. But this validation can be turned off simply by setting the new validation.allowEmpty option to true.

Hotfix: jQuery builds are missing $.fn.fineUploaderDnd

Fixed in #1700. Also fixed a smaller bug in #1691 that inflated the size of most built JS files a bit.

Hotfix: Auto-retry, chunking, & S3 signature fixes

• #1670 - The qq.status.UPLOAD_RETRYING status is now used before the waiting period starts between auto-retry attempts. This makes it easier to determine (for API users) when a retry attempt is in progress.
• #1669 - When a file is deleted or unavailable mid-upload, previously it would take a while for Fine Uploader to fail the attempt. Now, that is fixed.
• #1630 - With version 4 signatures enabled for Fine Uploader S3 and with the objectProperties.key option set to "filename", the signature generated for keys w/ non-ASCII characters is invalid, which causes the Initiate Multipart Upload request to S3 to fail.

Hotfix: Azure delete SAS request ignores custom headers

Reported in #1661 and fixed in #1662. Thanks to @danielebriggi for both. Now, signature.customHeaders will be sent to the SAS endpoint before a DELETE request is sent.

Hotfix: S3/Traditional/All Uploader does not load in IE8/9

This was caused by a missing qq.WindowReceiveMessage object in the generated build artifacts. More details in #1653.

Better "Getting Started" guide

The "Getting Started" guide at http://docs.fineuploader.com/quickstart/01-getting-started.html was completely rewritten for this hotfix release, and some noise and incorrect markup was removed from the template files. Fine Uploader should now be even easier to setup! Thanks goes to @strohhut for the suggestions and proofing.

More details at #1646.

Hotfix: Azure and S3 jQuery wrappers missing plug-in aliases

The files that include the $.fn.fineUploaderS3 and $.fn.fineUploaderAzure functions were mistakenly omitted from the build. This is a regression, caused by work on 5.11.0, detailed in #1643.

Hotfix: Missing jquery.fine-uploader.js build artifacts

Starting with 5.11.0, the jquery.fine-uploader directory in the build/npm output and the fine-uploader.zip file was missing the traditional endpoint jQuery-wrapped Fine Uploader JS files (both minified and unminified). Details in #1639.

Hotfix: Wrong path for /lib/core modules

Described in #1637. This issue would lead to a build error (or possibly even a runtime error) when attempting to import or require a core module using one of the aliases in lib/core.