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 group 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 help boards and others with the identical downside replied that they had been experiencing the identical factor. Most of these responding reported that that they had not lately completed something to their websites, that that they had crashed swiftly.
The one that initially reported the bug provided a workaround for getting web sites again up and working, an edit of a single line of code within the BlockPatterns.php file, which is a WooCommerce file.
The file is situated right here:
wp-content/plugins/woocommerce/src/Blocks/BlockPatterns.php
Others reported receiving the identical deadly error message:
“Uncaught Error: strpos(): Argument #1 ($haystack) should be of kind string, null given in /var/www/website/knowledge/www/website.com.br/wp-content/plugins/woocommerce/src/Blocks/BlockPatterns.php on line 251”
One of many commenters on the dialogue posted:
“Similar subject 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 current updates. Changing the code at line 251 labored as a short lived workaround.
We’ll must discover a extra steady resolution till the WooCommerce group releases an official patch.”
Others reported that they acquired the error after updating their plugins however that rolling again the replace didn’t remedy the issue, whereas others reported that they hadn’t completed something previous to experiencing the crash.
Somebody from WooCommerce help responded to say that the WooCommerce group is conscious of the issue and are working to handle it:
“Thanks for reporting this. It’s a recognized subject, and a short lived 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 group is conscious and actively addressing it.”
Fast Repair Posted On GitHub Dialogue
Somebody posted a fast repair to the official GitHub repository that may remedy the issue for now:
If Your Web sites Are At present Down – This Is the Fast Repair for You Right now
To get websites that had been bricked by the replace with the error message:
Deadly error: Uncaught TypeError: strpos(): Argument #1 ($haystack) should 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 ) {You’ll want to clear any WordPress caching layers you might need after making use of this alteration.
Could be useful for these coming right here on the lookout for a fast repair to get reside websites working once more at this time, and to purchase a while for the WooCommerce group to get #57759 prepared.
The identical WooCommerce GitHub repository additionally has this notice:
“Some websites would possibly see a deadly error round class BlockPatterns.php, with the web site not loading. This was due a foul response from Woo sample repository. A repair was deployed to the repository however sure websites would possibly nonetheless have a foul cache worth.”
Additionally they wrote:
“The difficulty has been fastened from the cache supply aspect however sure websites had been left with a foul cache worth, we shall be releasing patch updates to repair that.”
Further Downside On WPEngine
Somebody wrote that they continued to battle with their WP Engine website after implementing a repair:
“I’m struggling to implement the repair on WP Engine. I assume it’s a cache subject, however importing the repair, and clearing all caches isn’t working. Is there an extra step that I’m lacking? To date 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 numerous layers you would possibly must clear together with their Web page Cache and Varnish caches. See: https://wpengine.com/help/cache/”
Learn the preliminary report on the WordPress Help discussion board:
Deadly error BlockPatterns.php:251
Learn the GitHub dialogue:
Deadly Error round strpos in BlockPatterns.php #57760
Featured Picture by Shutterstock/Kues
