Opened 23 months ago

Last modified 4 months ago

#17999 new defect (bug)

Failure to Update Notification Persists After Manual Upgrade

Reported by: Lorelle Owned by:
Priority: normal Milestone: Awaiting Review
Component: Upgrade/Install Version: 3.2
Severity: normal Keywords: needs-patch
Cc:

Description

This has been around for a few versions. When an update fails, if the user updates or upgrades manually and WordPress lists the updated version in the Administration Panels, the failure to update notification persists.

I've sat through four or five updates with the failure notice on every panel, including WordPress 3.2, on several sites.

Change History (6)

This is by design.

.maintenance will stick around after a failed automatic update. It needs to be removed as part of the manual update steps.

It might be a good idea to change .maintenance to a non-hidden file so it would be easier to delete, but that's about it.

Really? Instructions need to be in place on how to remove this as part of the manual update. Are there such instructions? Thanks.

Ah, hadn't noticed that page had been updated.

Still doesn't discount the fact that "I" think this part should be automatic. :D

Thanks,

Lorelle

comment:5 follow-up: ↓ 6   nacin23 months ago

I think we can automate this a little.

We could store the WP version we're trying to get to in .maintenance, then compare it to $wp_version. If they match, then we could probably assume the update was successful.

MD5 verifications of updates (3.3?) would be another nice touch.

comment:6 in reply to: ↑ 5   SergeyBiryukov4 months ago

Replying to nacin:

MD5 verifications of updates (3.3?) would be another nice touch.

Related: #20074

Note: See TracTickets for help on using tickets.