Make WordPress Core

Opened 4 years ago

Last modified 7 months ago

#19781 new defect (bug)

All update processes should be within an iframe — at Version 3

Reported by: dd32 Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: Upgrade/Install Keywords: has-patch needs-refresh
Focuses: Cc:

Description (last modified by dd32)

Currently some of the update processes run within iframes, others don't.

We should standardise on all within an iframe.

Running inside the iframe has the advantage that the footer of the page is loaded, and therefor, the Toolbar will load, rather than the page appearing half-loaded for certain upgrade/install processes.

Currently, Processes which run inside iframes are Bulk updates, Singular updates load directly.

We should also investigate a iframe overlay that contains a "Working.. please wait" graphic that clears once the content of the iframe starts loading, This should help ease the pain of not being sure if the update process has started on servers that force gzip (and as a result, provide no user feedback until the process is complete) - See #18525 and #18239 for examlples of that see #19783

Change History (3)

#1 @dd32
4 years ago

  • Description modified (diff)

#2 @DrewAPicture
4 years ago

  • Cc xoodrew@… added

+1 for this. I've experienced the "updates hang" issue on many installs. I wasn't aware that some were iframed and others weren't.

#3 @dd32
4 years ago

  • Description modified (diff)
Note: See TracTickets for help on using tickets.