Conditional block breaks when switching to Raw code editor and back

This support ticket is created 4 years, 1 month 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 1 reply, has 2 voices.

Last updated by Christian Cox 4 years, 1 month ago.

Assisted by: Christian Cox.

Author

Posts

November 22, 2020 at 8:02 am #1852435

Alexander Rothschild

As the title describes - sometimes I switch to the raw mode in Gutenberg (Ctrl-shift-alt-M) to do some search and replace. And when I switch to the designer mode - each conditional block shows "This block has been corrupted" message. Clicking "Attempt recovery" does fix it though, but it is a hassle, when there are many blocks.

November 22, 2020 at 2:22 pm #1852585

Christian Cox

Hi, in a quick test in my local environment I set up 3 conditional blocks with conditionals based on a single custom field value, but when I switched between raw and designer modes I was not able to replicate the same problem. It might be fastest if I log in and see how your post's block editor design is set up so I can try to recreate the same scenario locally. Then I can troubleshoot further to see if this is a problem with Toolset's blocks or some other system conflict. If that's okay with you, please provide login credentials in the private reply fields and let me know where I can test the scenario you described.

The topic ‘[Closed] Conditional block breaks when switching to Raw code editor and back’ is closed to new replies.