WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 9 months ago

#38581 closed defect (bug) (invalid)

Media uploads fail after session expiration

Reported by: avcascade Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Upload Keywords:
Focuses: Cc:
PR Number:

Description

On occasion, I write fairly long blog posts in WordPress that can take some time to research and put together. I've noticed that after a session expiration, I am not able to use the media uploader to add images/files to my post unless I refresh the editor, either by using my browser's Refresh functionality or by clicking the Save Draft button. I could see how a novice user could get very frustrated in this sort of situation, not knowing how to get beyond the error.

Steps to reproduce

  • On a WordPress site (for testing purposes) use a plugin like Login Security Solution to decrease the idle timeout to something short, like two minutes. (This negates having to wait for hours for the default inactivity limit to be reached).
  • Open the post editor and begin creating a post.
  • After logging back in when prompted, try to upload an image or other file using either the "Add Media" button or the Set featured image link.
  • Watch the upload fail with the cryptic message "HTTP Error". (Uploading ... Filename.png ... HTTP error.) The user cannot ascertain from this error why the upload failed.

Trying the upload again will result in the same error every time. The media uploader will not work until the editor screen has been reloaded in the browser.

Change History (1)

#1 @desrosj
9 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed
  • Version 4.6.1 deleted

Hi @avcascade,

Sorry that it took so long to receive a response to this ticket.

Since this ticket was opened, the new block editor has been shipped in WordPress Core. With this comes a ground up redesign of how content is created. It's possible that this was fixed in that process. If this was not fixed, it should be explored within the context of the new block editor, and this should take place on the Gutenberg GitHub repository.

After exploring, if there are changes required to Core outside of the Gutenberg packages, we can open a new ticket.

Note: See TracTickets for help on using tickets.