Upload handler should pass errors on to forms.FileField

[Marti Raudsepp]

As far as I can tell, currently no mechanism exists for file upload handlers to pass errors forward to form fields.

The result is that any upload errors result in "This field is required" or "The submitted file is empty" messages.

Other errors worth handling:

• File upload size limits
• Unicode decode error in filename

Thoughts?

[Gabriel Hurley]

This seems reasonable to me and I don't see any obvious mechanism in place with which to do this currently. Marking accepted.

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[ANUBHAV JOSHI]

There have been some changes since past years. But I am in favour of this.
I hope/intend to do this in GSoC this year. I think the following can also be added along with those suggested above:

File not uploaded completely
Write failure

[ANUBHAV JOSHI]

for upload limit we now have max_length.
We can have a check unicode error in filename and also of possible the two I mentioned above.

EDITS: max_length error is for filename.

[Tim Graham]

In general we should be careful about exposing detailed error messages to users. e.g. I believe the unicode error is a server configuration issue (see #17686). Similarly, "file not uploaded completely" and "write error" are not issues that the user is in a position to resolve so if anything, those errors would need to be surfaced as something like "The file upload was unsuccessful. Contact the site admin if the error persists". The issue of upload size seems like a valid one though. Do you have a proposal for propagating errors from upload handlers to forms?

[ANUBHAV JOSHI]

I think checks for exceeding_upload_size and for encoding_type, we could add a check in ​forms.FileField.to_python(). We already have several checks there, so it seems reasonable enough to add there.
Thought on this?

[ANUBHAV JOSHI]

max_size for FileField

[Tim Graham]

Although the scope of this ticket isn't well defined, I think what you've implemented is somewhat tangential to what the summary describes "Upload handler should pass errors on to forms.FileField" -- although, I'm not sure how/if file size limit errors would be part of the upload handler. Btw, max_upload_size already exists as a third party package: ​django-validated-file. We'd probably want a mailing list thread to figure out if we'd want to bring it into core. I don't feel strongly either way on doing so.

[ANUBHAV JOSHI]

Here: ​https://groups.google.com/forum/#!topic/django-developers/4fbcsPhuuR8

[Tim Graham]

A couple comments on the post:

1. It's better to make a proposal than ask "what to do" or "how to solve a ticket." What do you think should be done? If you don't care, then find I'd find something else to work on.

2. A subject that includes a description of the item instead of "Decision for ticket #14787" is more likely to get interested people to read it.

[ANUBHAV JOSHI]

I did mention what I want to do, i.e. including the new attribute max_size, though I will pay more attention to the subject from next time onwards.
Thanks.

[Tim Graham]

What's the file name encoding issue you mentioned in the mailing list post? Is it different from #17686?

[ANUBHAV JOSHI]

What I wanted to say is we can inform the user about the problem in a better way than just adding in the docs by raising a proper error in to_python() itself as we have file_name there so we could check the encoding.

[Tim Graham]

It's a server configuration issue that should be fixed by the person deploying the site, not something an end user should get an error about.

[ANUBHAV JOSHI]

OK. So we are down to that maximum size issue itself.
Can you please post your replies on both the points on ML, so that when someone sees he knows about these things as well.

[Tim Graham]

After looking into this, Anubhav and I don't see any easy way to pass errors from upload handlers to forms since at the time the handler exception is raised, you aren't inside a form to catch it.

One thing I thought of would be to allow an exception raised during file upload parsing to be stored in request.FILES so it would be re-raised when you accessed the file's key later, but I'm wary of this complexity and not even sure it would work.

Regarding max_size on FileField, it really should be the subject of a separate ticket and given it's possible to implement this yourself and available in 3rd party packages, I don't think there's an urgent need for it.