Make WordPress Core

Opened 2 years ago

Last modified 2 years ago

#55380 new defect (bug)

Updating from 5.8.2 to 5.9.2 breaks default website (no additional plugins)

Reported by: rinart73's profile rinart73 Owned by:
Milestone: Awaiting Review Priority: normal
Severity: major Version: 5.9.2
Component: Upgrade/Install Keywords:
Focuses: Cc:


I wanted to test some plugins on my local server. I had old WordPress 5.8.2 archive. I installed it and then it automatically updated. Immediatelly after that my website broke. I didn't install any additional plugins.

Server: Apache 2.4
PHP: 7.4
MySQL: 8.0

Fatal error: Uncaught Error: Call to a member function switch_to_blog() on null in C:\OpenServer\domains\\wp-includes\cache.php:239 Stack trace: #0 C:\OpenServer\domains\\wp-includes\load.php(727): wp_cache_switch_to_blog() #1 C:\OpenServer\domains\\wp-settings.php(131): wp_start_object_cache() #2 C:\OpenServer\domains\\wp-config.php(95): require_once('C:\\OpenServer\\d...') #3 C:\OpenServer\domains\\wp-load.php(50): require_once('C:\\OpenServer\\d...') #4 C:\OpenServer\domains\\wp-admin\admin.php(34): require_once('C:\\OpenServer\\d...') #5 C:\OpenServer\domains\\wp-admin\index.php(10): require_once('C:\\OpenServer\\d...') #6 {main} thrown in C:\OpenServer\domains\\wp-includes\cache.php on line 239

Fatal error: Uncaught Error: Call to undefined function __() in C:\OpenServer\domains\\wp-includes\class-wp-fatal-error-handler.php:188 Stack trace: #0 C:\OpenServer\domains\\wp-includes\class-wp-fatal-error-handler.php(152): WP_Fatal_Error_Handler->display_default_error_template() #1 C:\OpenServer\domains\\wp-includes\class-wp-fatal-error-handler.php(57): WP_Fatal_Error_Handler->display_error_template() #2 [internal function]: WP_Fatal_Error_Handler->handle() #3 {main} thrown in C:\OpenServer\domains\\wp-includes\class-wp-fatal-error-handler.php on line 188

Change History (1)

#1 @costdev
2 years ago

Hi @rinart73, welcome to Trac!

Sorry to hear you had trouble upgrading to WordPress 5.9.

The switch_to_blog() fatal error was reported in ticket #54969 and may have been caused by a failed installation.

If possible, please try the installation again and let us know whether it was successful.

Note: See TracTickets for help on using tickets.