WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 4 years ago

#29679 closed defect (bug) (invalid)

Upgrade Failures Involving class-wp-list-table.php

Reported by: miqrogroove Owned by:
Milestone: Priority: normal
Severity: critical Version: 4.0
Component: Upgrade/Install Keywords:
Focuses: Cc:
PR Number:

Description

I've been seeing a lot of forum postings relating to 4.0 and errors during or after login. In particular, I've seen these two recent threads with error information that points to mismatched file versions:

https://wordpress.org/support/topic/wordpress-40-update-now-i-cant-login

https://wordpress.org/support/topic/after-updating-to-wordpress-40-i-get-some-errors

Change History (8)

#1 @miqrogroove
5 years ago

  • Severity changed from normal to critical

#2 @SergeyBiryukov
5 years ago

  • Version set to 4.0

Both threads look like an incomplete upgrade, not sure what we can do here.

#3 follow-up: @miqrogroove
5 years ago

Just off the top of my head, would it be possible to test some ini values prior to upgrade such as timeout settings, and then stage the new files in a separate directory and move them all at once? Strategies like that usually prevent mismatching files.

#4 @miqrogroove
5 years ago

ignore_user_abort and set_time_limit should be checked for proper usage also.

#5 in reply to: ↑ 3 @nacin
5 years ago

Replying to miqrogroove:

Just off the top of my head, would it be possible to test some ini values prior to upgrade such as timeout settings, and then stage the new files in a separate directory and move them all at once? Strategies like that usually prevent mismatching files.

This is exactly what happens. set_time_limit() is also already used. Not sure about ignore_user_abort(), but that should happen in a ticket proposing that. Four years ago dd32 suggested it should be used. 5:ticket:16066

#6 @miqrogroove
5 years ago

Is there some way to add a cron that could fix a failed upgrade?

#8 @dd32
4 years ago

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

Created #32652 for ignore_user_abort().

I don't think there's anything wrong or fixable here, I expect this was simply the first file in the zip being updated, or it's size was larger than others..

Note: See TracTickets for help on using tickets.