Block error
-
I’m getting the error ‘This block has encountered an error and cannot be previewed’ when I try to create a new post or edit any of my previous posts. How can I fix this?
-
Hey there, could you send a link to an affected post or page? I did a bit of spot checking and couldn’t find it.
Also, if it was working before, can you think of any changes that were made just before things stopped working?
-
All of my posts or pages are affected. They look fine but when I try to create a new post or edit an old one, I get nothing but a block containing that error. I can edit/create in code view, but obviously that’s not ideal.
Classic block worked fine on 4/23, but the next time I tried to create a post, a week later, I got that error and it has persisted.
-
Hi there!
Can you let us know what the URL is of the site where you’re having this problem? Once we have that information, we’ll be better able to advise.
Thank you!
-
Are we both on the same page? If I go here I do not see any errors:
https://wordpress.com/post/missminamurray.wordpress.com/16863 -
-
-
-
I see the error on every post or page I try to edit. This is just one example: https://wordpress.com/page/missminamurray.wordpress.com/14384
And yes, I saw only the error on the link you sent, nothing else only “This block has encountered an error and cannot be previewed”.
-
-
It’s fine in Chrome. I’m getting the error in Safari, my default browser. It happens if I try to create a new post as well as edit an old one.
-
Okay, it works fine for me in Safari as well, so it looks like the problem might be with your installation of Safari.
Please go to this site:
From that page, what is your Safari version?
What does it show under JavaScript and Cookies?
And do you have any browser add-ons installed in Safari?
If you log in using Safari’s private mode, does that make any difference?
-
Every single page I have created prior to the Gutenburg editor is now coming up with “this block has encountered an error and cannot be previewed” in Safari and is blank in the editor – meaning I cant edit it, it still displays content for users correctly.
I was really happy with the old editor, I dont understand why the downgrade to a 1970s block editor was done at all.
-
Many thanks for your replies
The block editor works fine, it is content created in the Classic editor that is not working.
Safari private mode works, normal http: does not.
Big Sur 11.3 – Updated very recently, it did Safari too – possibly the issue (earlier Big Sur broke GIMP for example)
Safari 14.1
It works with Firefox 88.0
Javascript and Cookies enabled.
Google Analytics opt out extension
Check your Safari version as it is a recent problem?
-
It very much sounds like your specific combination of OS/Browser/extensions might be the problem here. Especially since it’s working in other non-Safari browsers and we as Staff can’t replicate the issue.
Just to make sure, I checked some old test posts made in the Classic Editor (on a test, non-Staff account) in Safari 14.1 (16611.1.21.161.3) and Mac OS Big Sur 11.3 (20E232) and they show up just fine – can make edits, preview, etc.
I also don’t have any extensions in Safari and have the default privacy settings enabled.
Please check your extensions and anything else settings-wise related to third party cookies, anti-tracking, etc. to try and rule out a setting that might be causing the problem.
Let us know what you find out!
-
Just checked again – @missminamurray hint helped:
The issue is specifically the disable X-Site tracking option in Safari – I have NOT changed this – I assume therefore that WordPress is trying to use it in new ways?
It reports 8 trackers that were blocked including Google and Facebook that I have NEVER given permission to use from Safari. (Web Page, then black/white shield on left :
https://support.apple.com/en-gb/guide/safari/ibrw35004465/14.0/mac/11.0)
This should NOT stop WordPress from operating – WordPress should not be allowing this.
-
Interesting, I cannot reproduce the issue under Safari 14.1 and macOS 11.3.1.
Are you running any extensions alongside Safari, or just Safari and its built-in blocking?
- The topic ‘Block error’ is closed to new replies.