[wp-trac] [WordPress Trac] #61489: 6.1.7 and 6.2.6 Updates Cause Critical Error

[WordPress Trac]

#61489: 6.1.7 and 6.2.6 Updates Cause Critical Error
-------------------------------+------------------------------
 Reporter:  mping001           |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Upgrade/Install    |     Version:  6.1
 Severity:  critical           |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by tomsommer):

 Replying to [comment:40 dd32]:

 > This is my best guess as well. Possibly a host-level security patcher.
 However, that doesn't make much sense to me..
 >
 > The reason it doesn't make much sense,
 [https://core.trac.wordpress.org/browser/trunk/src/wp-admin/includes
 /class-core-upgrader.php?marks=92-97#L85 is that in the event that a core
 file is modified, WordPress doesn't use the "partial" zip files] and
 instead uses the full release ZIP for that version. That would overwrite
 any modified files.

 I see, okay - well then none of this makes any sense, if all files are
 overwritten on upgrade then the timestamp of default-filters.php should be
 recent.

 > My best guess is that the patching software has run immediately
 following the upgrade. That would explain it I guess.

 Doubt that, based on mtime timestamps the modifications are often years
 old.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/61489#comment:41>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform