You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This generally happens because the form's Javascript assets were not loaded properly, likely because either:
The developer forgot to include {{ form.media }} in the template for the form
The end user blocked Javascript
The current fallback is generally undesirable for case 1, since it disguises an important programming error.
For case 2, the behavior may or may not be desirable. The fallback does allow such end users to sometimes succeed in uploading a file, but at the cost of tying up a request thread on the server and bypassing all the functionality of S3FF.
The text was updated successfully, but these errors were encountered:
Currently, if a file is uploaded directly via a
multipart/form-data
request to a server-rendered form (the traditional behavior ofFileField
), it will trigger a fallback behavior to be accepted and stored: https://github.com/girder/django-s3-file-field/blob/f4c48d42bfdf765550271cdb7f908bbc616c78e9/s3_file_field/widgets.py#L77This generally happens because the form's Javascript assets were not loaded properly, likely because either:
{{ form.media }}
in the template for the formThe current fallback is generally undesirable for case 1, since it disguises an important programming error.
For case 2, the behavior may or may not be desirable. The fallback does allow such end users to sometimes succeed in uploading a file, but at the cost of tying up a request thread on the server and bypassing all the functionality of S3FF.
The text was updated successfully, but these errors were encountered: