Problem Adding an Update Image greater than ~1MB

[adriancollier]

When you try to upload an image to an Update where the image is larger than 1MB, you are provided with a bad error message:

If we have a fixed requirement for an image size below 1MB then this needs to be confirmed.

We advise Partners for less than 2MB, so we may need to change our messaging.

If a user tries to upload an image that is too big, we should validate this and present the user with the following message:

"The image you have chosen is too large. Please choose a smaller version or resize your image so that it is less than 2MB in size.

The best results are achieved with Images with an aspect ratio of 4:5."

[carlio]

You can now upload larger files, however there is no easy way to give a nice error message. The server just stops the connection if more than 3mb is uploaded - it will never get to Django. In order for Django to understand enough to give a nice error message, we have to let all of the data through, which sort of makes the limit a moot point.

What's the largest image file size someone would reasonable expect to upload?

[carlio]

Note that we can replace the 413 page with a nice Akvo-styled 'oops that's too big', but it can only be a static HTML page and therefore the user would lose all of the other form information the submitted along with the big image.

[carlio]

I suggest that we have a Javascript check on the client which refuses to upload files which are too big, something like:
http://stackoverflow.com/questions/7497404/find-out-file-size-before-uploading-using-jquery-ajax/7497439#7497439

[adriancollier]

To be covered in #219