-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle 413 gracefully when reporting a bug #994
Milestone
Comments
I just hit this again, so I want to fix it ASAP. Right now you get a flash message that says something went wrong (which you probably wont' see, see #1010) and then the spinner never goes away. So, we should have a useful flash message, and the spinner should go away. |
And maybe #996 isn't working for the add-on screenshot use case. To investigate. |
miketaylr
pushed a commit
that referenced
this issue
Apr 22, 2016
miketaylr
pushed a commit
that referenced
this issue
Apr 22, 2016
miketaylr
pushed a commit
that referenced
this issue
Apr 22, 2016
Also test that img_too_big isn't true before re-enabling submits.
(Just some related frontend tweaks for now) |
miketaylr
pushed a commit
that referenced
this issue
Apr 23, 2016
miketaylr
pushed a commit
that referenced
this issue
Apr 23, 2016
Also, make sure z-index is higher than the image preview.
miketaylr
pushed a commit
that referenced
this issue
Apr 23, 2016
Also, make sure z-index is higher than the image preview.
miketaylr
pushed a commit
that referenced
this issue
Apr 23, 2016
Also, make sure z-index is higher than the image preview.
miketaylr
pushed a commit
that referenced
this issue
Apr 27, 2016
miketaylr
pushed a commit
that referenced
this issue
Apr 27, 2016
Also test that img_too_big isn't true before re-enabling submits.
miketaylr
pushed a commit
that referenced
this issue
Apr 27, 2016
Also, make sure z-index is higher than the image preview.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now if you try to upload a massive image, you get redirected to an ugly default NGINX 413 request entity too large page.
We need to instead of redirecting to that page, display a flash error and let the user select a smaller image.
#993 is related, but this bug is what happens in case that fails (maybe not possible, but we should cover both the front and back end experiences).
The text was updated successfully, but these errors were encountered: