A WordPress bug is inflicting WooCommerce websites to show a deadly error, crashing ecommerce websites. The issue originates from a single line of code. A workaround has been created. The WooCommerce workforce is conscious of the problem and is engaged on issuing a everlasting repair within the type of a patch.
WooCommerce Websites Crashing
Somebody posted concerning the error on the WordPress.org assist boards and others with the identical drawback replied that they have been experiencing the identical factor. Most of these responding reported that that they had not not too long ago carried out something to their websites, that that they had crashed abruptly.
The one that initially reported the bug provided a workaround for getting web sites again up and operating, an edit of a single line of code within the BlockPatterns.php file, which is a WooCommerce file.
The file is positioned right here:
wp-content/plugins/woocommerce/src/Blocks/BlockPatterns.php
Others reported receiving the identical deadly error message:
“Uncaught Error: strpos(): Argument #1 ($haystack) have to be of kind string, null given in /var/www/web site/knowledge/www/web site.com.br/wp-content/plugins/woocommerce/src/Blocks/BlockPatterns.php on line 251”
One of many commenters on the dialogue posted:
“Similar situation right here.
It occurred in model 9.8.2, and upgrading to 9.8.3 didn’t resolve it. Downgrading to 9.7.1 didn’t assist both.
The issue occurred with none interplay with plugins or latest updates. Changing the code at line 251 labored as a brief workaround.
We’ll must discover a extra secure answer till the WooCommerce workforce releases an official patch.”
Others reported that they obtained the error after updating their plugins however that rolling again the replace didn’t resolve the issue, whereas others reported that they hadn’t carried out something previous to experiencing the crash.
Somebody from WooCommerce assist responded to say that the WooCommerce workforce is conscious of the issue and are working to handle it:
“Thanks for reporting this. It’s a recognized situation, and a brief workaround has been shared right here: https://github.com/woocommerce/woocommerce/points/57760#issuecomment-2854510504
You possibly can observe progress and updates on the GitHub thread: https://github.com/woocommerce/woocommerce/points/57760, because the workforce is conscious and actively addressing it.”
Fast Repair Posted On GitHub Dialogue
Somebody posted a fast repair to the official GitHub repository that may resolve the issue for now:
If Your Web sites Are At the moment Down – This Is the Fast Repair for You Right this moment
To get websites that have been bricked by the replace with the error message:
Deadly error: Uncaught TypeError: strpos(): Argument #1 ($haystack) have to be of kind string, null given in /var/www/html/wp-content/plugins/woocommerce/src/Blocks/BlockPatterns.php:251is so as to add ?? ” into the road 251:
if ( strpos( $class['title'] ?? '', $prefix ) !== false ) {Remember to clear any WordPress caching layers you may need after making use of this variation.
Could be useful for these coming right here in search of a fast repair to get dwell websites working once more at this time, and to purchase a while for the WooCommerce workforce to get #57759 prepared.
The identical WooCommerce GitHub repository additionally has this observe:
“Some websites may see a deadly error round class BlockPatterns.php, with the web site not loading. This was due a nasty response from Woo sample repository. A repair was deployed to the repository however sure websites may nonetheless have a nasty cache worth.”
Additionally they wrote:
“The problem has been fastened from the cache supply facet however sure websites have been left with a nasty cache worth, we will probably be releasing patch updates to repair that.”
Additional Drawback On WPEngine
Somebody wrote that they continued to wrestle with their WP Engine web site after implementing a repair:
“I’m struggling to implement the repair on WP Engine. I assume it’s a cache situation, however importing the repair, and clearing all caches isn’t working. Is there a further step that I’m lacking? To this point solely restoring a backup fastened it.”
The reply was that WP Engine has a number of caches that have to be up to date:
“Thats as a result of WPEngine is a platform, not a standard internet server – There are lots of layers you may must clear together with their Web page Cache and Varnish caches. See: https://wpengine.com/assist/cache/”
Learn the preliminary report on the WordPress Assist discussion board:
Deadly error BlockPatterns.php:251
Learn the GitHub dialogue:
Deadly Error round strpos in BlockPatterns.php #57760
Featured Picture by Shutterstock/Kues
