• Resolved ddrapeau

    (@ddrapeau)


    One of my site’s front-end pages stopped working after Meow Lightbox 3.1.8

    i.e. “The White Screen of Death”

    PHP Error log shows:

    fatal 2022-04-12 13:00:32 Allowed memory size of 536870912 bytes exhausted (tried to allocate 155648 bytes) in Unknown on line 0

    wp-admin side works fine.

    Memory was set to 256M when I started getting the error. Increasing to 512M did not help.

    I tried disabling every plugin one by one and found disabling Meow lightbox restored my front-end access.

    Further test showed a rollback to 3.1.6 fixes problem.

    Bizarre FYI: I run two other sites and they work fine with 3.1.8

    The two sites that 3.1.8 works on are:
    Server architecture Linux 4.15.0-175-generic x86_64
    Web server Apache/2.4.53 (Unix) OpenSSL/1.1.1
    PHP version 7.4.28 (Supports 64bit values)
    WordPress Version 5.9.3 en_CA

    The server that 3.1.8 fails on is:
    Server architecture Linux 5.4.0-107-generic x86_64
    Web server Apache/2.4.53 (Unix) OpenSSL/1.1.1f
    PHP version 7.4.28 (Supports 64bit values)
    WordPress Version 5.9.3 en_CA

    I’m going to keep looking for other differences in the sites but I’m reporting it here hoping for some help … and to warn others.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hello @ddrapeau,

    Thank you very much for letting us know and for including the error log!

    We’ve had one similar report yesterday but without the error log, I’ll let @tigroumeow have a closer look at it!

    Cheers,

    Thread Starter ddrapeau

    (@ddrapeau)

    Thanks for letting me know that there are other reports.

    Since you like the error log, here is more:

    fatal 2022-04-12 12:15:16 
    Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0
    
    fatal 2022-04-12 12:15:16 
    Allowed memory size of 536870912 bytes exhausted (tried to allocate 151552 bytes) in /srv/users/sso/apps/sso/public/wp-includes/functions.php on line 5219
    
    fatal 2022-04-12 12:15:16 
    Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /srv/users/sso/apps/sso/public/wp-includes/formatting.php on line 4996

    The functions.php code being referenced is:

    
    /**
     * Flush all output buffers for PHP 5.2.
     *
     * Make sure all output buffers are flushed before our singletons are destroyed.
     *
     * @since 2.2.0
     */
    function wp_ob_end_flush_all() {
    	$levels = ob_get_level();
    	for ( $i = 0; $i < $levels; $i++ ) {
    		ob_end_flush();
    	}
    }
    

    with line 5219 being ob_end_flush();

    the formatting.php code being referenced is:

    /**
     * Maps a function to all non-iterable elements of an array or an object.
     *
     * This is similar to <code>array_walk_recursive()</code> but acts upon objects too.
     *
     * @since 4.4.0
     *
     * @param mixed    $value    The array, object, or scalar.
     * @param callable $callback The function to map onto $value.
     * @return mixed The value with the callback applied to all non-arrays and non-objects inside it.
     */
    function map_deep( $value, $callback ) {
    	if ( is_array( $value ) ) {
    		foreach ( $value as $index => $item ) {
    			$value[ $index ] = map_deep( $item, $callback );
    		}
    	} elseif ( is_object( $value ) ) {
    		$object_vars = get_object_vars( $value );
    		foreach ( $object_vars as $property_name => $property_value ) {
    			$value->$property_name = map_deep( $property_value, $callback );
    		}
    	} else {
    		$value = call_user_func( $callback, $value );
    	}
    
    	return $value;
    }

    with line 4996 being: $object_vars = get_object_vars( $value );

    I hope this helps …

    Plugin Author Jordy Meow

    (@tigroumeow)

    Hi @ddrapeau,

    Can you update to the latest version released today, visit the Performance tab, and try to uncheck the “Output Buffering” option?

    Thread Starter ddrapeau

    (@ddrapeau)

    I have just updated to 3.1.9 as requested.

    unchecking of “Output Buffering” as you requested still gave the blank home screen …. but checking it gives me my site back! Thank you!

    FYI – I checked the other two sites that never had the problem … they were still at 3.1.8 so I updated them to 3.1.9 and they seem to work with “Output Buffering” both on or off.

    That new “Output Buffering” option mentions themes, so I checked them: All sites are using Tempera 1.8.0

    I’m guessing there is a difference in how Lightbox operates with Tempera theme if OS is “Linux 4.15.0-175-generic x86_64” vs “Linux 5.4.0-107-generic x86_64”.

    It looks like enabling “Output Buffering” is needed with Linux 5.4.0-107 and Tempera theme.

    Let me know if you want more info or if there are any tests you want me to try.

    Thanks again for your quick help on this!

    I use the Pro version (Version 3.2.1) and I have to ENABLE the output buffering option. My theme is the Enfold theme

    • This reply was modified 2 years, 11 months ago by flipper1960.

    With the newest version we had the problem, that our lightbox in posts (and not in sites) stopped working. Pictures simply did not open in a lightbox on click without an error message. It workes on sites and it workes before the update.

    Activating “Output buffering” also solved the problem for us. Not sure if this is the same problem.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘front-end stopped working after upgrade to Meow Lightbox 3.1.8’ is closed to new replies.