April 28, 2023 at 7:15 am
I haven’t updated to Kadence 3.0 yet on a few sites, since it nuked my home page when I tested it in Beta. I’ve been busy working on other things, and was pushing it off. I foolishly neglected to turn off automatic updates for WordPress itself, and it auto-updated to WordPress 6.2 upon release. Nothing was broken from what I could see, so I didn’t do anything about it besides switching to maintenance/security auto updates only.
I went to queue up my monthly blog posts today, and I started getting this error in the editor only for Advanced Text blocks, saying “This block has encountered an error and cannot be previewed.” (or edited…)
I had been doing a bunch of plug-in updates all month for Kadence – besides the 3.XXX update for the main extension – and was dreading figuring out what the cause was & how much work it’d be to fix. Luckily it became very apparent it was WordPress 6.2, as when I rolled back to the last backup where I was still able to edit Advanced Text Blocks, it still had the auto-update WP thing enabled, and so it immediately updated to 6.2 again. When I went to check on the editor, it was doing the “This block has encountered an error and cannot be previewed.” thing again, so it 100% is WordPress 6.2 that is causing it. Everything else was successfully rolled back, since I disabled automatic updates for everything, so the only difference was WordPress 6.0 -> 6.2
What is causing this, and what is the work-around? I can’t find any way to roll back to 6.0 in the admin panel natively, and my backup has the auto-update enabled so I can’t roll back anything to fix it either. Really need to queue up my blog posts for the next month, so any help is appreciated ;_;