Editor settings (CoBlocks) are broken

[filipanoscampos]

Quick summary

On an Atomic website using the CoBlocks plugin, when we open Editor settings from the page or post editor, they look visibly broken.
Here is how it looks now:

And here is how this is supposed to work:

Steps to reproduce

1. Confirm the website is using CoBlocks
2. Navigate to a page or post and open it in the Editor
3. Click on the ... (three dots) in the top right corner
4. proceed to select Editor Settings from the listed options (notice this is different from Preferences)
5. The options aren't showing and the content in the modal window looks visibly broken

What you expected to happen

The options to be listed and working as usual:

What actually happened

The options aren't listed and are instead broken.

Context

p1665566214014569-slack-C03TY6J1A

Platform (Simple, Atomic, or both?)

Atomic

Theme-specific issue?

No response

Browser, operating system and other notes

No response

Reproducibility

Consistent

Severity

Some (< 50%)

Available workarounds?

No response

Workaround details

No response

[jamiepalatnik]

📌 SCRUBBING : RESULT

• Tested on AT - Replicated
• Tested on Self-hosted - Could Not Replicate
• Replicable on Core - No

📌 FINDINGS/SCREENSHOTS/VIDEO

• I was able to replicate this on my AT site with CoBlocks plugin active. These Editor settings options come from the CoBlocks plugin, so it's not possible to test this when the plugin is deactivated.
• I was not able to replicate this on my self-hosted site.
• Noting that CoBlocks has not been installed by default on WordPress.com sites since about a year ago, but I'm moving this forward since this seems to impact all sites that do have CoBlocks installed.

📌 ACTIONS

• Marked as Triaged for Quality Squad review

[filipanoscampos]

Another one I believe is related to this: 5818652-zd-woothemes
Because we can't access the plugin settings, we can't set the gallery carousel as the user would like us to.

[github-actions]

Support References

This comment is automatically generated. Please do not edit it.

• 5818652-zen
• 5903258-zen

[cometgrrl]

@Automattic/team-calypso Is this something you can look into, or should we file an issue with CoBlocks/GoDaddy? Since it's Atomic specific, seems like it might be on our side.

[tyxla]

Sounds like this might be a matter of upgrading CoBlocks on Atomic, cc @fullofcaffeine for opinion.

[WunderBart]

https://github.com/orgs/Automattic/teams/team-calypso Is this something you can look into, or should we file an issue with CoBlocks/GoDaddy? Since it's Atomic specific, seems like it might be on our side.

I can take a look in a bit. It does look like it's on our side, so let's not file an upstream issue yet.

Sounds like this might be a matter of upgrading CoBlocks on Atomic, cc @fullofcaffeine for opinion.

Since we keep CoBlocks up to date on AT sites, I'd say it's the upgrade that broke the plugin. I'll see what changed with the last one and check if it doesn't collide with our CoBlock AT mods (in wpcomsh). 🤞

[WunderBart]

Turned out to be an upstream problem after all. I've already created an issue for it: godaddy-wordpress/coblocks#2474.
I've also prepared a bugfix, so hopefully, we'll be able to land it in WPCOM soon: godaddy-wordpress/coblocks#2473.

This breaking change was introduced at WordPress/gutenberg#44642 (cc @youknowriad).

[zdenys]

If we can, let's follow up with the user here 5903258-zd-woothemes once it's fixed.

[WunderBart]

Turned out to be an upstream problem after all. I've already created an issue for it: godaddy-wordpress/coblocks#2474. I've also prepared a bugfix, so hopefully, we'll be able to land it in WPCOM soon: godaddy-wordpress/coblocks#2473.

The fix has just been merged, so hopefully, it will land in a patch release soon! 🎉

[tyxla]

Thank you @WunderBart 🙌

[WunderBart]

The v2.26 containing the fix has been released. Do we know when the next Atomic CoBlocks upgrade is scheduled, @jmdodd?