I just installed the Gutenberg plugin on a staging site, where I use SiteOrigin Premium and SiteOrigin Widgets Bundle, and opened the page editor on one of the pages I created using SiteOrigin. I’m sorry to say… complete fail.
With the Gutenberg Plugin still installed, I then installed the WordPress “Classic Editor v0.2” WYSIWYG editor. When I went to choose a page to edit and moused over the page link, I was shown the standard “Edit | Quick Edit” etc. options, but a new option was there called “Edit (Classic)” and when I chose that option, the SiteOrigin page editor was back to normal. I do hope you guys get a solution up soon. After the WordPress 5.0 upgrade, if you don’t want to have to install the “Classic Editor,” the only other option I can see is to rebuild the page with the Gutenberg Blocks… unless SiteOrigin has a fix.
Hi Arlee_carson,
We really should have been already compatible with the classic editor and for that, we’re very sorry! This will be corrected in the next update.
As for Gutenberg support, at the moment, Page Builder will remain Page Builder (as in, separate to Gutenberg – the interface won’t change and everything will continue to work as normal). With that said, we’ll be looking at integrating more deeply with Gutenberg closer to WordPress 5.0. Does that make sense? Once again, we’re very sorry about this whole situation and we’ll be correcting it asap!