WordPress publishers are discovering that Gutenberg 10.2 (launched March 17, 2021) is inflicting “deadly errors” because of a WordPress incompatibility concern.  One writer instructed that Gutenberg autoupdates ought to do a compatibility examine and set off a warning if the incompatibility exists.

WordPress Gutenberg

Gutenberg is a visible WordPress website editor that represents a radical departure from how web sites had been constructed natively throughout the WordPress core.

It permits publishers to create websites utilizing graphic consumer interface of blocks. For instance, an internet web page might be visualized as blocks representing the highest of the web page (header), the content material space, sidebar, and many others.


Proceed Studying Beneath

Gutenberg is just not but completed, full website enhancing functionality remains to be on the best way. So naturally as a not but mature expertise bugs are to be anticipated, if not anticipated.

Gutenberg 10.2 Deadly Error

A member of the Superior WordPress Fb Group began a dialogue to doc a deadly error encountered when updating to Gutenberg 10.2.

The publish said that the deadly error manifested in WordPress model 5.6. It was additionally famous {that a} GitHub publish on the error famous that Gutenberg 10.2 is just not appropriate with WP 5.5, both.

WordPress and Gutenberg Launch Timeline

WordPress 5.7 was launched on March 9, 2021.

The Gutenberg 10.2 website editor was launched just a little over every week in a while March 17, 2021.

Gutenberg website publishers who up to date to WordPress 5.7 after which up to date to Gutenberg 10.2 shouldn’t be seeing this error.


Proceed Studying Beneath

Nonetheless publishers who up to date to Gutenberg 10.2 however not WordPress itself might expertise the deadly error.

The deadly error is especially vulnerable to occur to publishers who set their Gutenberg installations to mechanically replace (autoupdate) however aren’t set as much as autoupdate WordPress itself.

An error was famous within the official Gutenberg WordPress support forums however on the time of this writing there was no comply with up.

The deadly flaw concern was additionally documented on the official Gutenberg GitHub page.

From the GitHub report:

“After updating to 10.2.0 I obtained an e mail a few technical concern with the plugin:

An error of kind E_ERROR was induced in line 59 of the file… I used to be in a position to de-activate the plugin through ftp. Now I don’t wish to activate it till I do know this has been addressed.”

One other particular person posted that they seen the identical factor and posted a screenshot:

The consumer who printed the screenshot adopted up with:

“I used to be working WordPress 5.6. After the improve to five.7, all the pieces began working as anticipated.”

The one that initiated the unique GitHub publish affirmed that this was their concern as effectively.


Proceed Studying Beneath

“Thanks for letting me learn about 5.7. I hadn’t up to date WP both, now I can re-activate Gutenberg.”

Gutenberg 10.2 Incompatible with Older Variations of WordPress

One other GitHub Gutenberg report highlighted that Gutenberg 10.2 induced deadly errors in older variations of WordPress.

A writer utilizing WordPress model 5.5.3 additionally reported a deadly error that induced a crash.

The particular person reporting the problem confirmed that it was particular to Gutenberg 10.2, stating:

“I deactivated the Gutenberg plugin 10.2.0. Once I tried to reactivate the plugin the deadly error got here again.

Deadly error: Uncaught Error: Class 'WP_Block_Supports' not present in..."

The particular person made a useful commentary and suggestion that Gutenberg 10.2 shouldn’t be allowed to replace (or autoupdate) on WordPress variations lower than WP 5.7.

“It shouldn’t be attainable for autoupdating Gutenberg plugin on an older WP website. Because the end result appears to create a deadly error. As there might be a variety of websites that can come throughout this drawback.”


Proceed Studying Beneath

That may be a good answer to the issue! If a identified incompatibility exists between Gutenberg 10.2 and older variations of WordPress then it is sensible that autoupdates in these conditions will cease and generate a warning of an incompatibility.

Customers of Gutenberg website editor who’re publishing with a model of WordPress that’s older than WP 5.7 are might think about it prudent to replace to the newest model earlier than updating to Gutenberg 10.2.


Gutenberg 10.2.0 Locked Caused a Fatal Error #29977

Fatal Error in Gutenberg Plugin 10.2.0 #29972

Fb: Superior WordPress Group (group membership required to View)
FYI, the Latest Gutenberg plugin 10.2 Update Will Cause a Fatal Error

!function(f,b,e,v,n,t,s) {if(f.fbq)return;n=f.fbq=function(){n.callMethod? n.callMethod.apply(n,arguments):n.queue.push(arguments)}; if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0'; n.queue=[];t=b.createElement(e);t.async=!0; t.src=v;s=b.getElementsByTagName(e)[0]; s.parentNode.insertBefore(t,s)}(window,document,'script', 'https://connect.facebook.net/en_US/fbevents.js');

if( typeof sopp !== "undefined" && sopp === 'yes' ){ fbq('dataProcessingOptions', ['LDU'], 1, 1000); }else{ fbq('dataProcessingOptions', []); }

fbq('init', '1321385257908563');

fbq('track', 'PageView');

fbq('trackSingle', '1321385257908563', 'ViewContent', { content_name: 'wordpress-gutenberg-10-2-causing-fatal-errors', content_category: 'news wp ' });

}// end of scroll user

Source link

Sharing is caring!

Related Posts

Leave a Reply