WordPress.org

Make WordPress Core

Opened 8 months ago

Last modified 3 months ago

#39647 new defect (bug)

Make media upload "HTTP error." more user-helpful

Reported by: mikeschroder Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 3.4
Component: Media Keywords:
Focuses: ui, administration Cc:

Description

Since the introduction of the Media Gallery in WordPress 3.4, the error messages when users attempt to upload media have been reduced to a detail-less “HTTP error.”, without any suggestion as to how users can move forward, and limited information for users to be able to contact their hosts to get help.

This is user hostile, and not in line with many of the assertions in WordPress Philosophy.

There’s no doubt that error messages must exist, but they should be useful, providing next steps for users.

A few possible parts/steps of this:

  • Retry
  • Auto Retry
  • Better error messages where possible (Timeout, Out of Memory, in user terms)
  • Expand for Exact Details to give to host (or WP_DEBUG enables this?)
  • Troubleshooting Steps, or link to troubleshooting steps

This should be possible to accomplish in stages, which will likely each need their own tickets.

One of the first steps for "Retry" is to make image upload/thumbnail creation able to be resumed, rather than only adding the meta after all sizes are created.

Attachments (1)

Screen Shot 2017-01-19 at 10.53.10 PM.png (13.7 KB) - added by mikeschroder 8 months ago.
"HTTP error." -- This one was after a timeout.

Download all attachments as: .zip

Change History (17)

@mikeschroder
8 months ago

"HTTP error." -- This one was after a timeout.

#1 @SergeyBiryukov
8 months ago

Since the introduction of the Media Gallery in WordPress 3.4, the error messages when users attempt to upload media have been reduced to a detail-less “HTTP error.”

FWIW, that message wasn't new in 3.5 media overhaul, it existed since the introduction of SWFUpload in 2.5, see [6659]:
http://geek.thinkunique.org/2008/03/30/fix-wordpress-25-upload-error-http-error/

This ticket was mentioned in Slack in #core-media by mike. View the logs.


8 months ago

#3 @SergeyBiryukov
7 months ago

#39810 was marked as a duplicate.

This ticket was mentioned in Slack in #core-media by mike. View the logs.


7 months ago

#5 @mikeschroder
7 months ago

As noted in the Slack mention above, @joemcgill and I met about this ticket a bit at Loopconf regarding what would be necessary for the first steps here.

They look something like:

  • Improve JS handling of http error codes and body, to provide more detailed error messages
  • Save progress of meta/multi_resize during creation of the intermediate images (with save basic meta before starting resizing process)
  • Resume multi_resize without re-uploading the file

I've got a pretty good idea of what the latter two will look like, but any insights of the JS handling -- in particular, why we're not surfacing any error details -- would be appreciated. I remember that there were technical challenges (rather than deciding the information was not helpful) involved in resolving this, but do not remember all of the background.

I don't think it necessarily needs to happen in this order, as making it so that thumbnail resizing resumes in any form will help more users be successful in getting their images uploaded (and eventually not having the HTTP Error show up).

This ticket was mentioned in Slack in #core-media by mike. View the logs.


7 months ago

#7 @zodiac1978
7 months ago

It seems that the JSON Response sometimes contains some useful information which could (should?) be used.
https://sebastian.expert/fix-wordpress-an-error-occurred-in-the-upload-please-try-again-later/

As a moderator in the German support forums this is often a problem for beginner. They just get this "HTTP error" and they do not know what to do.

They don't know too, that specials characters (or combining characters) are not a good idea for file names. See: #24661, #22363, #35951, #30130

This ticket was mentioned in Slack in #core-media by joemcgill. View the logs.


6 months ago

This ticket was mentioned in Slack in #core-media by mike. View the logs.


6 months ago

This ticket was mentioned in Slack in #core-media by joemcgill. View the logs.


5 months ago

#11 @mikeschroder
5 months ago

See #40439 for the "Save progress in meta" part noted above.

This ticket was mentioned in Slack in #core-media by mike. View the logs.


4 months ago

This ticket was mentioned in Slack in #core-media by mike. View the logs.


3 months ago

#14 follow-up: @pengriffix
3 months ago

I got this when i tried uploading an image of 2mb. How can i fix this. http://rapbible.me/wp-content/uploads/2017/06/screenmunch.png

#15 in reply to: ↑ 14 @mikeschroder
3 months ago

Replying to pengriffix:

I got this when i tried uploading an image of 2mb. How can i fix this. http://rapbible.me/wp-content/uploads/2017/06/screenmunch.png

This ticket is about making this error show what the actual problem is -- as in, just seeing that it is an HTTP error could mean many things at this point (which is frustrating, I agree!).

I'd suggest asking in the support forums, since usually seeing "HTTP Error" does not indicate a bug in WordPress core.

This ticket was mentioned in Slack in #core-media by desrosj. View the logs.


3 months ago

Note: See TracTickets for help on using tickets.