Thank you for taking the time to inform me about the issue!
I think it irresponsible of WordPress.com running alpha-software on their customer websites, especially when flagging it as ‘business.’
I’ll have this fixed ASAP, although Automattic kindly reached out to me and said this wouldn’t become a widespread issue until December 2021. I’m despondent, albeit not surprised, to learn only three weeks had to pass. I asked them why they did this via email. But that’s neither here nor there.
Look out for version 4.1.5 of The SEO Framework, which will have a compatibility patch for “Gutenberg.” Cheers 🙂
Hi again!
I just talked with Automattic, and it seems they do not run Gutenberg by default on Business sites.
It would be best if you were cautious about using the Gutenberg plugin on production websites because it’s labeled as “Beta” software, albeit not explicitly stated on their plugin page.
Thank you for such a swift reply!
I will be waiting for the updated version of The SEO Framework!
As for Gutenberg, I’m not sure whether I have any choice in this, as the plugin is marked as “This plugin was installed by WordPress.com and provides features offered in your plan subscription.”, current version being 11.3.0, and is kinda there by default. Not sure what I’d lose exactly if I stop using it as I was under the impression that it was a “key” feature…
Hello!
I’m not sure why WordPress.com would install that plugin by default and promote it as a key feature. The Gutenberg plugin is a free beta-plugin meant for developers to test changes: Whatever’s put in there might or might not eventually land in WordPress itself. When anything does, it’ll then be polished up and ready for production use.
Although the Gutenberg project/plugin developers are seasoned at not breaking things (backward compatibility), mistakes can happen.
According to this page, WordPress 5.8 (current) uses a mix of Gutenberg 10.0 to 10.7 internally.
Starting from June 9th, abridging Gutenberg updates:
10.8 included Block Design tools.
10.9 included URL previews, list-view improvements, block manager.
11.0 improved the accessibility of template parts.
11.1 improved the accessibility of the editor’s list-view.
11.2 brought the search block and group block (finally).
11.3 brings a dimensions panel and performance improvements.
If nothing on this list sounds familiar or useful to you, or if you cannot recall implementing something fancy since June 9th, then you can safely deactivate Gutenberg without having to worry about breaking anything. If you do find your content messed up, you can always reactivate Gutenberg without a hassle. The SEO Framework won’t be available to use i.c.w. Gutenberg 11.3.0, however, until we figure out how to resolve the evolving issues.
In the worst case, we’ll have to disable the “Primary Category”-selection feature of TSF to stabilize things, if only temporarily.
Howdy!
I’m happy to announce TSF 4.1.5 is out, which allows you to use Gutenberg together with The SEO Framework again. Thank you for being so patient!
After updating, if you still find the editor crashing, please try any of the following key combinations whilst viewing the crashed editor:
CMD ⌘+OPTION ⌥+R (Safari Mac);CMD ⌘+SHIFT ⇧+R (Chrome/Firefox Mac);- or
CTRL ^+SHIFT ⇧+R (Windows).
These keyboard shortcuts will force-fetch the latest scripts from your server (including the updated script of TSF).
Alternatively, you can hold CMD/CTRL and click the “Refresh” button of your browser.
