[wp-trac] [WordPress Trac] #59057: Critical error after update to 6.3 due to WP_Metadata_Lazyloader

[WordPress Trac]

#59057: Critical error after update to 6.3 due to WP_Metadata_Lazyloader
-------------------------------+------------------------------
 Reporter:  alexpaterson       |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  General            |     Version:  6.3
 Severity:  critical           |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by joemcgill):

 Thanks @alexpaterson. If you could set the `WP_DEBUG` constant to `true`
 in your `wp-config.php` file, that might display more info. Is it possible
 that you have any plugins in your mu-plugins folder that is trying to load
 this file directly?


 Here's a full stack trace that was shared by someone experiencing this
 same issue on the support forum:

 {{{
 PHP Fatal error: Cannot declare class WP_Metadata_Lazyloader, because the
 name is already in use in /var/www/html/wp-includes/class-wp-metadata-
 lazyloader.php on line 32
 PHP Fatal error: Uncaught Error: Call to a member function set() on null
 in /var/www/html/wp-includes/l10n.php:806\nStack trace:\n#0 /var/www/html
 /wp-includes/l10n.php(900): load_textdomain()\n#1 /var/www/html/wp-
 includes/class-wp-fatal-error-handler.php(47):
 load_default_textdomain()\n#2 [internal function]:
 WP_Fatal_Error_Handler->handle()\n#3 {main}\n thrown in /var/www/html/wp-
 includes/l10n.php on line 806
 }}}

 Not much more help, I'm afraid, and am not sure that the issue with I10n
 is related to the `WP_Metadata_Lazyloader` problem.

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