Version 2.3.1 update causes “Cannot use output buffering”

  • Resolved dbhoff90

    (@dbhoff90)


    6 years, 7 months ago

    Updated to 2.3.1 this morning and now receive a white screen alongside this error in Chrome:

    Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0

    There are similar topics out there for this exact issue with other caching plugins (e.g. W3TC), and the errors seem to be tied to the minification settings, but I am unsure of how to correct this issue in WPSoL. Any help would be greatly appreciated!

    Side note: 2.3.0 had no issues on this end, and the issue goes away when the plugin is deactivated (it is deactivated on the site currently)

    • This topic was modified 6 years, 7 months ago by dbhoff90.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author JoomUnited

    (@joomunited)

    Hi,

    Thanks for contacting us.
    It can be indeed the minification, you can try to disable it and see how it goes. As a method I recommend this one for testing, please report here when your encounter the problem, thanks!

    – Activate the plugin but disable all the optimization features > Clean browser cache > Test on your live website

    – Activate Cache only with specific cache for each device > Clean browser cache > Test on your live website

    – Activate Cache + Expire headers > Clean browser cache > Test on your live website

    – Activate Cache + Expire headers + Remove query strings > Test on your live website

    – Activate Cache + Expire headers + Remove query strings + Group CSS > Clean browser cache > Test on your live website

    – Activate Cache + Expire headers + Remove query strings + Group CSS + Group JS > Clean browser cache > Test on your live website

    – Activate Cache + Expire headers + Remove query strings+ Group CSS + Group JS + HTML minification > Clean browser cache > Test on your live website

    – Activate Cache + Expire headers + Remove query strings + Group CSS + Group JS + HTML minification + CSS minification > Clean browser cache > Test on your live website

    -Activate Cache + Expire headers + Remove query strings + Group CSS + Group JS + HTML minification + CSS minification + JS Minification > Clean browser cache > Test on your live website

    Let me know.

    Cheers,

    Thread Starter dbhoff90

    (@dbhoff90)

    Thank you for the quick and detailed response!

    I did manage to solve the issue – What I had to do was disable all of the minification/group settings, delete the cache and minified CSS/JS, and then re-enable those settings (plus a browser cache clear). No other settings appeared to be affecting the error message as I went through.

    Plugin Author JoomUnited

    (@joomunited)

    looks like some old cache was served with the new plugin version, we’ve made a lot of changes in this version.

    Thanks for reporting, cheers,

    Thread Starter dbhoff90

    (@dbhoff90)

    Wanted to post another update to this in case anyone is experiencing similar issues. The issue was “fixed” the last time I posted, but resurfaced shortly after. The issue kept occurring while viewing any page on our site while I was logged in to wp-admin, regardless of browser, and could only be fixed with a cache clear until logging in again. I finally identified that it was a plugin conflict between WP SOL and Autoptimize. Both plugins were trying to minify and group my HTML, CSS and JS. Autoptimize was installed after WP SOL, and must have overridden the SOL minification settings, but when SOL was updated, perhaps it did the reverse.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Version 2.3.1 update causes “Cannot use output buffering”’ is closed to new replies.