#34403 closed defect (bug) (fixed)
Errors during smooth updates not displayed
Reported by: | mordauk | Owned by: | |
---|---|---|---|
Milestone: | 4.4 | Priority: | high |
Severity: | major | Version: | 4.3 |
Component: | Upgrade/Install | Keywords: | needs-patch |
Focuses: | javascript, administration | Cc: |
Description
When a smooth update (introduced in #29820) fails to complete, an error is supposed to be displayed. This, however, does not appear to be the case anymore. Update errors fail to display in trunk and also 4.3.1. It could be be happening in other versions as well but I have not confirmed it.
Instead of displaying a visual error, the updating indicator just spins forever.
I have confirmed this on a local test site and also on a live site running 4.3.1.
This can be easily tested by forcibly returning a WP_Error
at the top of download_package()
in WP_Upgrader
.
Change History (13)
#2
@
9 years ago
- Focuses javascript added
- Milestone changed from Awaiting Review to 4.3.2
- Priority changed from normal to high
#7
@
9 years ago
It's also hard to explain, but most errors are handled, it's just the "lower level" ones which are not filesystem related (connection/cannot write/cannot create folder/etc) which are missed.
#27365 is going to be required to have a non-generic error message, [35371] simply displays Update Failed: Plugin update failed.
when it hits an error condition.
[35371] could be backported to 4.3, but as 4.4 is in beta I think that's not really worth it.
This ticket was mentioned in Slack in #core by helen. View the logs.
9 years ago
#13
@
9 years ago
That doesn't actually catch the errors originally described in this ticket. It doesn't catch WP_Error
instances returned with failed downloads, at least not the last time I tested it after https://core.trac.wordpress.org/changeset/35371 was committed.
It appears to be failing because the
WP_Error
is never passed back towp.updates.updateError
inupdates.js
. It ges a0
response instead.