Strange PHP error when upgrading to 4.7.6

  • Resolved KevinPlusPlus

    (@kevinplusplus)


    7 years, 11 months ago

    After upgrading to 4.7.6 from 4.7.5, I start getting a stream of errors:

    E_ERROR: ob_end_flush(): Cannot use output buffering in output buffering display handlers

    New Relic reports the following trace:

    in ob_end_flush called at /public_html/wp-includes/functions.php (3598)
    in wp_ob_end_flush_all called at ? (?)
    in call_user_func_array called at /public_html/wp-includes/plugin.php (524)
    in do_action called at /public_html/wp-includes/load.php (671)
    in shutdown_action_hook called at ? (?)

    When I downgrade back to 4.7.5, the errors stop.

    I did a diff between 4.7.5 and 4.7.6 and the changes are really minimal so it seems odd to me, but I did see the handling of the debugging log changed.

    I do have Pro, but logging is not enabled. Any ideas? Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)

  • I’m having a similar issue with 4.7.6. I am also a Pro user, but came here to see if anyone else is having the same problem.

    On my site, the issue occurs when I have WP Retina 2x and WP Rocket activated at the same time. On posts or pages that contain images in the content area or sidebar, only part of the HTML is sent to the browser so only a blank white page is displayed. On pages without images in the content area or sidebar, everything works fine. This includes featured images, for example both archive pages and posts with featured images work as long as they do not have images in the content area or sidebar.

    Here is an example from the PHP error log:

    [Tue Dec 27 12:49:38.910114 2016] [proxy_fcgi:error] [pid 24285] [client 127.0.0.1:53723] AH01071: Got error ‘PHP message: PHP Fatal error: Call to undefined function wr2x_getoption() in [removed]/wp-content/plugins/wp-rocket/inc/front/plugin-compatibility.php on line 169\nPHP message: PHP Fatal error: ob_end_flush(): Cannot use output buffering in output buffering display handlers in [removed]/wp-includes/functions.php on line 3673\n’

    When I deactivate either WP Retina 2x or WP Rocket, the problem goes away.

    Hope this additional info helps. If this is totally unrelated to the original poster’s issue, then my apologies for jumping into the thread.

    Thread Starter KevinPlusPlus

    (@kevinplusplus)

    Hi,

    I had not checked my PHP error log, but I do have the same error there as well that flyingpylon reported:

    [26-Dec-2016 14:58:55 UTC] PHP Fatal error: Call to undefined function wr2x_getoption() in /public_html/wp-content/plugins/wp-rocket/inc/front/plugin-compatibility.php on line 169

    So it is also connected to WP Rocket for me as well.

    Thanks,

    Kevin

    Good news… an update to WP Rocket (v2.9.1) fixes the problem.

    https://wp-rocket.me/changelog/

    I can verify that it works for me.

    Plugin Author Jordy Meow

    (@tigroumeow)

    Awesome! Super! I am really glad to hear that. Big thanks to @wprocket too ??

    Thread Starter KevinPlusPlus

    (@kevinplusplus)

    Hi all, the WP Rocket update seems to have solved it for me as well. Thanks for the notification.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Strange PHP error when upgrading to 4.7.6’ is closed to new replies.