Update to 2.2.0 causes page errors

  • Resolved fwdcar

    (@fwdcar)


    6 years, 10 months ago

    Hi,

    Updating from version 1.8.1 to 2.2.0 produces the following errors on every page:

    ( ! ) Warning: Creating default object from empty value in C:\Apache24\htdocs\wp\wp-content\plugins\wp-multi-network\wp-multi-network\includes\functions.php on line 238

    then

    ( ! ) Fatal error: Uncaught Error: Maximum function nesting level of '256' reached, aborting! in C:\Apache24\htdocs\wp\wp-includes\load.php on line 796
( ! ) Error: Maximum function nesting level of '256' reached, aborting! in C:\Apache24\htdocs\wp\wp-includes\load.php on line 796

    This is a portion of the call stack that just repeats over and over:

    
252 2.6728 52071384 get_network( ) ...\load.php:832
253 2.6728 52071704 WP_Network->__construct( ) ...\ms-blogs.php:1150
254 2.6728 52071672 WP_Network->_set_site_name( ) ...\class-wp-network.php:132
255 2.6728 52071672 get_network_option( ) ...\class-wp-network.php:286
256 2.6728 52071672 get_current_network_id( ) ...\option.php:1186
Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter fwdcar

    (@fwdcar)

    update:

    These are the erros without XDebug loaded:

    Warning: Creating default object from empty value in C:\Apache24\htdocs\wp\wp-content-test\plugins\wp-multi-network\wp-multi-network\includes\functions.php on line 238

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in C:\Apache24\htdocs\wp\wp-includes\class-wp-network.php on line 286

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in C:\Apache24\htdocs\wp\wp-includes\plugin.php on line 453
    Thread Starter fwdcar

    (@fwdcar)

    I found the problem.

    It was data corruption (ref. integrity issues) in the wp_sitemeta table. Somewhere along the way (months?/years?) the sitemeta table had rows with site_id(s) that didn’t actually exist. Version 1.8.1 obviously didn’t have a problem with this, but 2.2.0 did.

    Hope this helps someone else in the future.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Update to 2.2.0 causes page errors’ is closed to new replies.