"This block has encountered an error and cannot be previewed"

This support ticket is created 4 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	-	-
13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	-	-

Supporter timezone: America/New_York (GMT-04:00)

Tagged: Toolset Blocks

This topic contains 3 replies, has 2 voices.

Last updated by Christian Cox 4 years, 10 months ago.

Assisted by: Christian Cox.

Author

Posts

April 3, 2020 at 11:04 pm #1573733

betH-2

I am trying to: edit a post/page using paragraph block

Link to a page where the issue can be seen: any post/page editor in wp-admin, simply click the cursor to start a paragraph block.

We have a number of sites showing the same error over the last several days after we updated to WordPress 5.4.

The error is that when using Gutenberg, trying to open a new paragraph block results in an error message: "This block has encountered an error and cannot be previewed." Other blocks seem to be okay.

After doing a bunch of troubleshooting activating and deactivating plugins, I have found that the error only appears when Toolset Types and All in One SEO are both activated. If I deactivate AIO SEO, leaving Toolset activated, the error disappears. If I deactivate Toolset, leaving AIO SEO activated, the error disappears.

I'm not sure if the error below appears in the console only because AIO loads first, but this is what I see:
Uncaught ReferenceError: wpv_add_conditional_quicktag_function is not defined at post-new.php:3824

We are having this on a number of sites, and help figuring out how to resolve this would be great!

This site uses CloudFlare, and I have tried clearing caches. I have temporarily paused CloudFlare for this site for troubleshooting.

April 5, 2020 at 3:06 pm #1574677

Christian Cox

Hi, thank you for the thorough analysis and details. This issue was reported already at the end of the week last week, and has been escalated to our 2nd tier support team. I suspect it will be escalated to our developers tomorrow morning. I have connected your ticket here with our internal tracking system so I will be prompted to provide updates here for you as work progresses, if a patch is released, etc. Until then, another supporter found that downgrading the AIO SEO plugin to version 3.3.5 fixed the problem enough that they were able to continue development. I'll keep you posted here.

April 6, 2020 at 3:35 pm #1575827

Christian Cox

Please note this issue has been escalated to our developers and an erratum has been posted: https://toolset.com/errata/all-in-one-seo-plugin-conflict-with-types-provokes-errors-on-post-edit-screens/

April 12, 2020 at 9:32 pm #1583435

Christian Cox

Hello, please note this erratum has been updated and our developers have determined this isue should be fixed by the AIO - SEO plugin :
https://toolset.com/errata/all-in-one-seo-plugin-conflict-with-types-provokes-errors-on-post-edit-screens/

This issue is caused by the All In One SEO Pack Plugin which deregisters the wplink scripts. These are native WordPress Core scripts that are often used by other software to add or manipulate the editor experience.

This means, any plugin relying on the script will fail to function if All In One SEO Pack is active.

If you are experiencing this issue, we suggest contacting the developers of the All in One SEO Pack plugin and asking them to fix this problem.