Opened 10 years ago
Closed 9 years ago
#32473 closed defect (bug) (fixed)
New plugin update feature doesn't always recognize errors
Reported by: | viktorix | Owned by: | dd32 |
---|---|---|---|
Milestone: | 4.2.3 | Priority: | normal |
Severity: | normal | Version: | 4.2.2 |
Component: | Upgrade/Install | Keywords: | fixed-major |
Focuses: | Cc: |
Description
The new same page plugin update feature introduced in 4.2 seems to not always recognize an error that prevents plugin from being updated, showing that it was updated successfully. Once plugin page is reloaded, it shows the same plugin with an available update again.
When I go through the process of using bulk update, it uses the older method of updating plugins with page being reloaded and statuses showed - here you do see errors and that plugin was not updated.
Attachments (1)
Change History (18)
#5
@
10 years ago
It now detects the failure, but still doesn't actually tell the end user what went wrong.
#6
follow-up:
↓ 7
@
10 years ago
@dd32 Is someone scheduled to work on the returned ajax error messages in the next incremental or major release?
#7
in reply to:
↑ 6
@
10 years ago
Replying to toddlahman:
@dd32 Is someone scheduled to work on the returned ajax error messages in the next incremental or major release?
@toddlahman, I've recently started taking a look.
#8
@
9 years ago
- Owner set to dd32
- Resolution set to fixed
- Status changed from new to closed
In 32779:
#9
@
9 years ago
- Keywords fixed-major added
- Resolution fixed deleted
- Status changed from closed to reopened
re-opening for 4.2.x, the fix there will need to be a subset of the 4.3 changes
In 32571: