[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:  needs-patch      |     Focuses:
-----------------------------+------------------------------
Description changed by sabernhardt:

Old description:

> Today we had around 20+ sites go down sporadically across multiple
> servers and hosting providers. All of the sites were on 6.1.7 or 6.2.6
> and had the same errors:
> PHP Fatal error: Uncaught TypeError: call_user_func_array(): Argument #1
> ($callback) must be a valid callback, function “_wp_footnotes_kses_init”
> not found or invalid function name in /wp-includes/class-wp-hook.php:308
>
> After verifying checksums on core we found that the wp-includes/default-
> filters.php file did not match and we had to re-download core on all the
> sites to get rid of the critical error. I imagine this will be happening
> for us most of the day. We checked server and security logs and didn’t
> find anything correlated to the issue and believe it may be something to
> do with the update methods. Not sure but some insight here would be
> helpful.

New description:

 Today we had around 20+ sites go down sporadically across multiple servers
 and hosting providers. All of the sites were on 6.1.7 or 6.2.6 and had the
 same errors:
 `PHP Fatal error: Uncaught TypeError: call_user_func_array(): Argument #1
 ($callback) must be a valid callback, function “_wp_footnotes_kses_init”
 not found or invalid function name in /wp-includes/class-wp-hook.php:308`

 After verifying checksums on core we found that the `wp-includes/default-
 filters.php` file did not match and we had to re-download core on all the
 sites to get rid of the critical error. I imagine this will be happening
 for us most of the day. We checked server and security logs and didn’t
 find anything correlated to the issue and believe it may be something to
 do with the update methods. Not sure but some insight here would be
 helpful.

--

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