Incompatibility with Genesis Blocks

Just a note, I was able to replicate this issue (on multiple projects) and while rolling back to 22.6 does “fix” the issue temporarily, there are security updates needed within 22.7

More Details. Seeing this error the console

wp-seo-premium-metabox-2270.min.js?ver=22.7:87 Uncaught TypeError: s.r is not a function
    at 4406 (wp-seo-premium-metabox-2270.min.js?ver=22.7:87:6421)
    at n (blocks.build.js?ver=f0b5f2d2a2d8bdc79f8f:1:286687)
    at 6686 (wp-seo-premium-metabox-2270.min.js?ver=22.7:77:734)
    at n (blocks.build.js?ver=f0b5f2d2a2d8bdc79f8f:1:286687)
    at wp-seo-premium-metabox-2270.min.js?ver=22.7:87:26736
    at t (blocks.build.js?ver=f0b5f2d2a2d8bdc79f8f:1:287656)
    at Array.forEach (<anonymous>)
    at blocks.build.js?ver=f0b5f2d2a2d8bdc79f8f:1:287799
    at blocks.build.js?ver=f0b5f2d2a2d8bdc79f8f:1:287859
    at blocks.build.js?ver=f0b5f2d2a2d8bdc79f8f:1:287910

https://capture.dropbox.com/pMkHo0FYOn1jFdP6

Also just an additional note. This is impacting BOTH the free and the premium versions

• This reply was modified 6 months, 2 weeks ago by Aaron Ware.

I am also receiving the same issue with Genesis Blocks after updating to Yoast version 22.7, this is also impacting the free version as well.

• This reply was modified 6 months, 2 weeks ago by tampham99.

Hi Aaron,

Thank you for bringing this issue to our attention! We apologize?for the trouble you are currently experiencing with our plugin. You are actually not the first to report this issue. That means a bug report has been created and is under review by our product team.

Workaround
At this time, there is no known workaround.

What’s next? 
Our product team will assess the severity of this problem in relation to other open bug reports and new features. Based on their assessment, the bug report will be given a priority level. Our developers work on the highest priority issues first. Unfortunately, this means we cannot give you an estimate of when they’ll start working on your report.

22.7 also completely nuked our site which is completely reliant on Genesis blocks. We rolled back to 22.6. Please fix ur plugin.

@maybellyne I’m hoping you can update us soon – because we can’t really use our sites until this is resolved. Thanks.

I have encountered this as well when going in to change my main homepage page for my Navigation Pro theme. My workaround for this was to briefly disable my Yoast plugin, make my changes, and then after saving reactivate my plugins. Obviously not a useful solution for creating new pages perhaps but it worked for my minor edits. Hope it helps ~ Mike

Having the same issue on my clients’ websites as I’m running Genesis Blocks with Yoast.

I’m hoping that breaking websites that have been running smoothly for years is enough to heighten the priority for the Yoast product team.
…

“What’s next??
Our product team will assess the severity of this problem in relation to other open bug reports and new features. Based on their assessment, the bug report will be given a priority level. Our developers work on the highest priority issues first. Unfortunately, this means we cannot give you an estimate of when they’ll start working on your report.”

Dear All,

Thanks for your patience all the while. An upcoming release, scheduled for next week will include a fix for the issue.

We are also experiencing this issue. Great that it is getting fixed soon.

I was able to ‘convert to HTML’ for some blocks but not others. Others I had to rebuild using native blocks and not use the Genesis blocks. This issue is marked resolved @aware but it looks like it won’t be until the Yoast update next week.

Everything looks fixed now that the update came out. Thanks!