White Screen on Post / Page

  • Resolved idowebwork

    (@mannweb)


    6 years, 6 months ago

    It appears, as others here have posted, the screen appears completely white (no admin bar or anything) with 3.8.0 activated. Running through Firefox’s Console, I get this, which shows one of the javascript files are not loading properly.

    Loading failed for the <script> with source “/wp-content/plugins/gutenberg/vendor/wp-polyfill-ecmascript.min.2ae96136.js”. post-new.php:108
[Show/hide message details.] ReferenceError: regeneratorRuntime is not defined[Learn More] index.js:12:86582
[Show/hide message details.] TypeError: Object(...) is not a function[Learn More] index.js:12:8067
[Show/hide message details.] TypeError: Object(...)(...) is undefined[Learn More] index.js:12:15977
[Show/hide message details.] TypeError: wp.editPost is undefined[Learn More]

    Since the javascript file fails to load, it breaks everything. Hope this can be fixed in the next update.

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

  • Hi, I am not anything to do with Gutenberg but …
    this is very likely a clash between Gutenberg and the Apache ModSecurity ruleset provided by Atomicorp.
    The most recent version of Gutenberg will trigger Atomicorps ModSecurity rules and they will 403 that polyfill.js file, causing Gutenberg to whitescreen.Atomicorp ruleset is detecting that file as an XSS attempt because of the JS insertion of an iFrame (is my guess based on my own ModSecurity logs)

    If you are on a Plesk server it’s very likely this ruleset is operational as these rules are the standard.
    If you have access to your hosting VPS and feel comfortable editing the ruleset you can add a manual exception, the simplest method being to enter the ID of the rule that will get your Gutenberg operational at the cost of a lower security to XSS in general. I am unfamiliar with methods of making more elegant exceptions.

    I have reported this bug on the Gutenberg GitHub but I was ignored and my results flagged as a “help request”. So it will probably not get fixed.
    https://github.com/WordPress/gutenberg/issues/10075

    Thread Starter idowebwork

    (@mannweb)

    I will pass this along to my host, as I am in fact using Plesk. Will follow up once I have worked with them.

    Wow, Steve, that is a pretty cool discovery. Is this something that maybe they will change to be the standard in Plesk? I had seen a discussion in GitHub about Cloudflare and Gutenbug and it looked to me like the Cloudflare people were willing to change their standard for the sake of Gutenberg, but I might not be understanding it.

    Moderator Marius L. J.

    (@clorith)

    Hi,

    Following up here, did you hear back on what was blocking your requests?

    Thread Starter idowebwork

    (@mannweb)

    As it turns out it was in fact something within the Web Application Firewall under Plesk blocking Gutenberg. Apparently something cause what appears to be an XSS, so the WAF blocked it. Setting a rule to whitelist it allows Gutenberg to work. Not at all a perfect solution, though.

    Hi mannweb, did you set this rule to whitelist and or did your provider by himself? I have the same error ad would try to fix it on the server I use.
    Thanks for feedback.

    Thread Starter idowebwork

    (@mannweb)

    If you have access to the Web Application Firewall for the domain under Plesk, you can whitelist the id you get from the error log right inside the WAF. That’s what I did at the domain level.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘White Screen on Post / Page’ is closed to new replies.