3.2.25 creates errors in wordpress editor

Hi @asocialnomad,

Thanks for the screenshot.

If you have website cache, please clear it after updating a plugin or theme.

If you’re still having an issue, please do the troubleshooting steps outlined in this article to rule out the usual causes: https://www.kadencewp.com/how-to-troubleshoot-your-website/

Please let us know how it goes.

Best,
Chito

Thanks. I’ve tried that, the ONLY thing that was updated was Kadence blocks. I’ve now tried this on two separate sites and the issue is the same. Kadence blocks is the only update that’s been made and the error is the same on both sites. It disappears when I roll back to 3.2.23. And all caches are cleared and I’ve tried this via two different computers too.

Hello @asocialnomad,

The screenshot looks like you’ve added a synced pattern to your content, is that correct? If so, can you try creating a design using standard Gutenberg blocks, turn it into a synced pattern, and add the content to see if the problem can be recreated.

A similar problem was reported with the Genesis theme and synced patterns. Are you using the Genesis theme by chance?

Hello @asocialnomad

I’ve obtained new information. The problem is due to CSS included from Kadence blocks that affect Gutenberg patterns. I’ve reported the issue to the developers for review.

thanks Gilbert, look forward to the next plugin update.

Hi Gilbert

Just to let you know that this issue is still present in 3.2.26. It was introduced in 3.2.24

Hello @asocialnomad,

It is scheduled to be addressed in the developer’s next sprint. However, a fix has not yet been released for this issue. We will update this thread when we have more information about a fix.

Thanks Gilbert.

Hi Gilbert, just checking in. the issue with synced patterns is still present in the 3.2.27 release, which makes working in wordpress editor impossible. I see also that Wordfence have issued a vulnerability alert for 3.2.23 which is the latest version not to have introduced the synced patterns issue.

Do you have a date for fixing this issue? It’s concerning that to continue using the plugin means living with a documented vulnerability.

• This reply was modified 1 year ago by ASocialNomad.

Hello @asocialnomad,

I checked the status of the ticket, and I saw that a fix hasn’t been released. It is in the current developer sprint and there is progress. The fix may likely be in the next update, but it isn’t released yet.

I apologize for the inconvenience and appreciate your patience.

Thanks for posting about this, we will get this fix out today!

Ben

Thanks @britner @ghernkadence – have tested and all resolved now. Thanks for your help!