The Block Editor has a White Page.

  • Unknown's avatar

    Hi.

    I have only started using Word Press this month, and I am hoping someone can work with me to help troubleshoot this specific problem. I have tried as much as I can so far by myself and I am willing to try any new suggestions but please bear with me and make them easy to understand because I really don`t know what I am doing. I think it is a browser specific error.

    Since I just started I am using the most basic starter plan – and I initially started creating posts in the Block Editor as the default until all of a sudden it only showed a white page.

    I then found out there was a Classic Editor and I can use that fine, and also the Quick Edit on the All Posts page, but not the Block Editor.

    I manually haven`t changed any settings on this computer or on my blog.

    This computer will not have automatically updated anything but the WordPress site may have.

    I do not have any plug-ins.

    I haven`t changed themes recently or at all. I did change to Twenty-Twenty and back again like suggested but the problem continued.

    I cleared the browser cache.
    I am using Firefox Quantum and Ubuntu
    (Do not take using Ubuntu as a sign that I in any way know what I am doing with computers. I didn’t set it up.)

    I cleared the cookies. This computer has something called Cookie AutoDelete on it, which has whitelisted wordpress, but please let me know if this might be the problem.

    I went on to another Computer.
    This one had Google Chrome and Windows 10.
    I could view and use the Block Editor fine on this one.

    However, I really want to fix things to be able to continue on as I have done on this Computer.

    From reading support articles my best guess was it was a javascript error. I went in to the Web Console as instructed and it lists 17 errors and a lot of code that means nothing to me.

    For example

    This is on the Dashboard.

    Invalid URI. Load of media resource data: failed. wp-admin
    JQMIGRATE: Migrate is installed, version 3.3.2 _static:5:699
    TypeError: Promise.allSettled is not a function[Learn More] _static:1:1179
    Loading failed for the <script> with source “https://stats.wp.com/w.js?61”. wp-admin:1390:1
    Loading failed for the <script> with source “https://www.google-analytics.com/analytics.js”. wp-admin:1:1
    Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://public-api.wordpress.com/rest/v1.1/js-error?_locale=user. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).[Learn More]
    Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://public-api.wordpress.com/rest/v1.1/js-error?_locale=user. (Reason: CORS request did not succeed).[Learn More]
    Error: Unable to record the error in Logstash. _static:1:1003
    Invalid URI. Load of media resource data: failed. index.php
    JQMIGRATE: Migrate is installed, version 3.3.2 _static:5:699
    Invalid URI. Load of media resource data: failed. notifications
    Loading failed for the <script> with source “https://stats.wp.com/w.js?61”. notifications:1:1
    Invalid URI. Load of media resource data: failed. rest-proxy

    This is on the blank white page.

    Invalid URI. Load of media resource data: failed. post-new.php
    Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://stats.wp.com/w.js?ver=202124. (Reason: CORS request did not succeed).[Learn More]
    onmozfullscreenchange is deprecated. index.min.js:1:120222
    onmozfullscreenerror is deprecated. index.min.js:1:120222
    Loading failed for the <script> with source “https://stats.wp.com/w.js?61”. post-new.php:1945:1
    Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://stats.wp.com/w.js?ver=202124. (Reason: CORS request did not succeed).[Learn More]
    <script> source URI is not allowed in this document: “https://stats.wp.com/w.js?ver=202124”. post-new.php:4097:1
    Loading failed for the <script> with source “https://www.google-analytics.com/analytics.js”.

    If someone can help me make sense of this, or even just confirm if this is what is causing the white screen problem or if I should look elsewhere, that would be fantastic.

    Thank you for your time

  • Hi there!

    We have seen quite a few reports of a blank page appearing when adding a new post, or editing an old one.
    It seems to be a browser-related issue, as you said. We still don’t have a fix, but clearing the browser’s cache seems to help in most cases.
    You mentioned that it did not make any change on your end. What version of Ubuntu and Firefox are you using? You can copy the link to your results from https://www.whatismybrowser.com/.

    Also, have you tried another browser on your computer?

  • Unknown's avatar

    Thank you for your reply.

    I have tried clearing the cache and cookies several times over, using two sepearte options, just to make sure. Even when it says they are taking up 0 bytes, still no luck.

    I also started Firefox in safe mode (disabling all add-ons) and also the refresh Firefox option (restoring default settings.)

    As for a new browser on this computer I will have get back to you. It is very old but it runs (mostly) fine with what it has. I will have to ask what version will work.

    As for the settings.

    Firefox is Version 66.0.3 (64-bit)

    The computer is Ubuntu14.04 LTS.

    Now, every time I share this bit of information someone always feels the need to point out that it is pretty old and I should probably update because that will solve everything and then they consider the issue resolved. If possible, please, give me other suggestions before this one.

    Thank you for your time

  • Unknown's avatar

    I keep getting

    ERROR: Duplicate reply detected; it looks as though you’ve already said that!

    But it doesn`t seem that the post is going through

    ****

    Thank you for your reply.

    I have tried clearing the cache and cookies several times over, using two sepearte options, just to make sure. Even when it says they are taking up 0 bytes, still no luck.

    I also started Firefox in safe mode (disabling all add-ons) and also the refresh Firefox option (restoring default settings.)

    As for a new browser on this computer I will have get back to you. It is very old but it runs (mostly) fine with what it has. I will have to ask what version will work.

    As for the settings.

    Firefox is Version 66.0.3 (64-bit)

    The computer is Ubuntu14.04 LTS.

    Now, every time I share this bit of information someone always feels the need to point out that it is pretty old and I should probably update because that will solve everything and then they consider the issue resolved. If possible, please, give me other suggestions before this one.

    Thank you for your time

  • Hi,

    Your replies were caught by our spam filters, that’s why you haven’t seen them after posting.

    As for your issue, I’m afraid I don’t have good news. I know this is now what you want to hear but the browser version matters for any software, like ours. In technology, things are constantly changing, and we can only guarantee that everything will work smoothly on the latest versions (and a couple of the previous ones) of a browser. For Firefox it’s already version 89.

    That said, if you’re unable to upgrade Firefox to a newer version, try if you’re able to install another browser.

  • Unknown's avatar

    Thank you for your kind reply.

    Spam filters! I would have thought my first post was more spammy. Oh well.

    Thank you so much for your patient explanations. I will have a try with browsers and updates.

    The confusing thing for me is it did work completely fine with those settings and then it stopped. It would have made more sense if it was just incompatible to begin with. However, technology is like that.

  • The confusing thing for me is it did work completely fine with those settings and then it stopped. It would have made more sense if it was just incompatible to begin with.

    Well, there has probably been something in the latest WordPress update that is not supported by older browsers anymore, that’s why the change feels so sudden and random, but in fact, it’s not.
    Hopefully, you’ll be able to upgrade your browser, and in the meantime, you can try using our mobile app :).

  • The topic ‘The Block Editor has a White Page.’ is closed to new replies.