I answered my question. I installed the WP Rollback plugin and rolled the Gutenberg update back to the stable version.
Hello there!
Sorry to hear that you faced such an issue, but I would like to inform you that I installed the Gutenberg plugin version 16.3.0 and tested it with the latest version of our Getwid plugin (1.9.1). However, I haven’t noticed the same message you have no matter how I open the page editor to edit the page that has a Getwid section. So there’s either something else that needs to be done to reproduce the issue on my side, or there’s something else that causes it on your site. Are there some details or steps to reproduce the conflict? Let me know.
Here is a video link covering what I am seeing…
After recording the video and posting it, I wonder if there aren’t issues with the Webyx plugin I’m running as well? It relies heavily on the “section” element?
https://youtu.be/_MgkN1ra1rM
FYI – The newest Gutenberg version generated that same message for any block from other collections – I like Getwid and Greenshift blocks and both come up as “unsupported” when I create a child theme with template parts that contain blocks that aren’t native wp blocks. It’s like Gutenberg only supports wp native blocks in themes – you can use them in page content and you can add them to template parts but you can’t then use those changes in another site without having to rebuild. It’s really annoying.
I have exactly the same problem with Getwid blocks, after Gutenberg update
-
This reply was modified 2 years, 10 months ago by
fla0it.
-
This reply was modified 2 years, 10 months ago by fla0it.
Hello, guys.
@digital-ninja Thank you very much for recording the video. We haven’t received any complaints on the matter of compatibility issues with the Webyx plugin, but I would like to inform you that I managed to reproduce the compatibility issue with the latest version of the Gutenberg plugin. And I passed on all the info to our developers’ team for them to take a look at the issue and check if a resolution should be applied on our side. Because, as @vytaulla51 said, looks like the issue applies to other plugins that provide Gutenberg blocks too, not just our Getwid plugin. What I noticed when I was running different tests locally is that the installation of the CoBlocks plugin by GoDaddy somehow helps to resolve the issue. Once this plugin is installed and activated, blocks from our Getwig plugin become available and seem to be working fine. So you can use this as a workaround until our devs take a look at the issue. Or, stay on the previous version of the Gutenberg plugin for now.
Hello guys!
I hope y’all doing fine!
I’m delighted to inform you that we have released the Getwid plugin version 2.0.0 where we resolved the Gutenberg plugin compatibility issue.
So feel free to update our plugin to the latest version and let us know in case you have any other questions.
