This block has encountered an error and cannot be previewed.

hi @eventide0

I’ve tried to reproduce this issue on my dev site, but have not yet had any success. We’ve also not received any reports of similar issues from other users recently. I suspect there may be something unique to your setup that is causing this.

It would be helpful to test to see if anything on your site is interfering with Formidable and causing the issue. Could you please go through the following steps?
https://formidableforms.com/knowledgebase/what-plugins-are-known-to-cause-conflicts/#kb-how-to-find-a-conflict

If the issue doesn’t show up while your website is running under these default conditions, you can reactivate your plugins, one at a time, and test after each activation to see when the issue reappears. When it does, the last plugin activated is the likely source of your problems.
———-

We understand that testing like this on a live site isn’t always possible, so we recommend doing this testing on a copy of the site (a staging site) instead. If you put the staging site on staging.yoursite.com or dev.yoursite.com, you won’t need an extra Formidable license to activate it.

Some hosts have an easy way to create a staging site. If yours doesn’t, you can copy your site using free plugins like
All in One WP Migration, Duplicator, or any other plugin or system you like. Your host may also be willing to create a staging site for you if you ask.

Let me know if you have any questions about this.

Best,

Went through the steps again. Looks like it displays the error with the Gutenberg plugin.

Hi @eventide0

I’ve tested and this works correctly with core WordPress blocks.

Can you please reach out to the Gutenberg support team about this since it seems to be caused by an issue with their plugin?

Best,

Hi @njones35,

This issue was brought to my attention as I am one of the Editor Triage Leads for WordPress 6.2. I am able to reliably replicate the issue using WordPress 6.2 Beta 4, which you can test here.

While the issue also occurs with Gutenberg active, the issue remains without Gutenberg in 6.2 which will be released at the end of the month.

If you and your team are able to test with Beta 4, that would be great. I want to ensure there is not a broader backward compatibility issue that has been introduced, but it’s very hard for us to tell on our end.

Thanks for your help!

Best,
Nick

Thanks for the heads up @ndiego

Our lead developer has logged this now and our team will work on a compatibility fix