Blank page when using NGINX with no nginx.conf

  • freshenext

    (@freshenext)


    8 months ago

    I am just writing to report an issue that I have been debugging for the last couple days.

    For some reason, after we updated the version from version 2.3.12 to version 2.7.0 we started to get blank pages in our wordpress website.

    We isolated the issue to the w3-total-cache plugin. It happened after version 2.4.0

    The cause is that the plugin is opening a ob_start inside an ob_callback – causing the page to go blank without notice.

    The file that is doing this is Util_WpFile -> write_to_file -> self::request_filesystem_credentials

    I’ll build the stack trace myself:

    Generic_Plugin.php:53 -> ob_start(callback here) <- IMPORTANT!!!!!!

    Minify_Plugin.php -> $minify_environment->fix_on_wpadmin_request

    Util_Rule.php:332 -> Util_WpFile::write_to_file

    An ob_start there, and, since we are inside an ob_callback already – the site crashes.

    You guys might want to check that, and if you need more context, just let me know. I’ll be more than glad to help.

    The root cause is that we don’t have the nginx.conf in our repository (but we do have it in our nginx config), so when the plugin went ahead and tried to create a file or something like that, it started an ob_start inside the ob_callback that you guys have for the minify plugin, crashing the site.

    The solution is to add the nginx.conf into the repository, even tho, depending on your nginx config, you might just not use it.

Viewing 6 replies - 1 through 6 (of 6 total)
  • vincentf73

    (@vincentf73)

    I’m having a similar problem, might be not exactly the same, but it’s also related to output buffering. The result is the same: some users get a totally blank page when trying to edit a post. There is a logline on my server:

    mod_proxy_fcgi.c(887): [client XXX.XXX.XXX.XXX:0] AH01071: Got error ‘PHP message: PHP Fatal error: str_replace(): Cannot use output buffering in output buffering display handlers in /data/sites/web/…/www/wp-content/plugins/w3-total-cache/UserExperience_LazyLoad_Plugin.php on line 69’

    vincentf73

    (@vincentf73)

    More info regarding my issue: when both The Event Calendar (6.3.5) and W3 Total Cache (2.7.0) are active then an “Editor” can not edit a post or page. They see a totally blank page. Content-length:0. In the logs there is the output buffering entry.

    An admin cán edit any page or post.

    If I disable either W3cache or The Event Calendar, it works again. So these two plugins are not working together at this time in these specific versions.

    vincentf73

    (@vincentf73)

    Even more info. I have two users, both “Editors”. One can edit a post, the other can not. The latter sees a blank page.

    The difference is that the working user has a specific language selected (Nederlands-Belgi?). The non-working user has “site default” selected. Which is “Nederlands”

    When I change the language of the non working to a specific language (can also be “Nederlands”), it works. Hope this helps in debugging this problem. So it’s not a problem with a specific language I think, it’s a problem with the option “site default”.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @freshenext

    Thank you for reaching out and I am happy to help!
    We need to replicate this and see the behavior because nothing has changed for this in the past releases.
    I’ll get back to you with more information once I have the answer.

    @vincentf73 Please open a new topic for this as this is not related to the original post!

    Thanks!

    Thread Starter freshenext

    (@freshenext)

    Hey @vmarko thank you for your reply! Any ETA as to when this will be checked?

    Thank you!

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @freshenext

    Thank you for your feedback.

    This is proccess. I’ll let you know what we find.

    Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Blank page when using NGINX with no nginx.conf’ is closed to new replies.