1. WordPress Gutenberg
  2. Gutenberg 10.2 Fatal Error
  3. WordPress and Gutenberg Release Timeline
  4. Gutenberg 10.2 Incompatible with older versions of WordPress

WordPress publishers are finding that Gutenberg 10.2 (released March 17, 2021) is causing "fatal bugs" due to a WordPress incompatibility issue. One editor suggested that Gutenberg auto updates should run a compatibility check and raise an alert if the incompatibility is present.

WordPress Gutenberg

Gutenberg is a visual WordPress site editor that represents a radical departure from the way websites were built natively in the WordPress core.

It enables publishers to build websites using the graphical user interface of blocks. For example, a web page can be represented as blocks that represent the top of the page (header), the content area, the sidebar, and so on.


Read on below

Gutenberg is not finished yet, the complete editing of the website has not yet been completed. As a technology that is not yet fully developed, errors are of course to be expected, if not to be expected.

Gutenberg 10.2 Fatal Error

A member of the Advanced WordPress Facebook Group started a discussion to document a fatal bug that occurred while updating to Gutenberg 10.2.

The post stated that the fatal bug occurred in WordPress version 5.6. It was also noted that a GitHub post about the bug noted that Gutenberg 10.2 is also incompatible with WP 5.5.

WordPress and Gutenberg Release Timeline

WordPress 5.7 was released on March 9, 2021.

The Gutenberg 10.2 site editor was released a little over a week later on March 17, 2021.

Gutenberg site publishers who upgraded to WordPress 5.7 and then to Gutenberg 10.2 shouldn't see this error.


Read on below

Publishers who have updated to Gutenberg 10.2 but not WordPress itself can experience the fatal bug.

The serious error occurs particularly often with publishers who set their Gutenberg installations so that they are updated automatically (autoupdate), but are not set up in such a way that WordPress itself is updated automatically.

A bug was found on the official Gutenberg WordPress support forums, but there was no follow-up at the time of this writing.

The serious bug problem was also documented on the official Gutenberg GitHub page.

From the GitHub report:

"After the update to 10.2.0 I received an email about a technical problem with the plugin:

An E_ERROR error was caused on line 59 of the file. I was able to deactivate the plugin via FTP. Now I don't want to enable it until I know this has been fixed. "

Another person wrote that they noticed the same thing and posted a screenshot:

Fatal WordPress Gutenberg ErrorScreenshot of WordPress Gutenberg fatal error

The user who posted the screenshot followed with:

“I was running WordPress 5.6. After upgrading to 5.7 everything worked as expected. "

The person who initiated the original GitHub post confirmed that this was their problem too.


Read on below

“Thank you for telling me about 5.7. I hadn't updated WP either, now I can reactivate Gutenberg. "

Gutenberg 10.2 Incompatible with older versions of WordPress

Another GitHub Gutenberg report highlighted that Gutenberg 10.2 was causing serious bugs in older versions of WordPress.

A publisher using WordPress version 5.5.3 also reported a fatal bug that caused a crash.

The person reporting the issue confirmed that it was specific to Gutenberg 10.2, stating:

“I deactivated the Gutenberg plug-in 10.2.0. When I tried to re-enable the plugin, the fatal error came back.

Fatal Error: Uncaptured Error: Class & # 39; WP_Block_Supports & # 39; not found in … "

The person made a helpful observation and suggested that Gutenberg 10.2 should not be upgraded (or automatically upgraded) on WordPress versions below WP 5.7.

“It shouldn't be possible to automatically update the Gutenberg plugin on an older WP site. The result appears to be causing a fatal error. As there can be many websites that encounter this problem. "


Read on below

That's a good solution to the problem! If there is a known incompatibility between Gutenberg 10.2 and older versions of WordPress, it makes sense that autoupdates are stopped in these situations and generate a warning of an incompatibility.

Gutenberg site editor users who publish with a version of WordPress older than WP 5.7 may find it advisable to update to the latest version before updating to Gutenberg 10.2.


Gutenberg 10.2.0 Locked caused a fatal bug # 29977

Fatal bug in Gutenberg Plugin 10.2.0 # 29972

Facebook: Extended WordPress Group (group membership required to view)
For your information, the latest update for the Gutenberg plug-in 10.2 causes a fatal error


Please enter your comment!
Please enter your name here