• Plugin Support Sandip Mondal – a11n

    (@sandipmondal)


    Some WooCommerce stores are currently experiencing fatal errors due to an issue with how WooCommerce receives block pattern data from a remote service. We’ve deployed a fix, but it may take some time to fully propagate to all sites.

    How do I know if this affects my site?

    If your store admin panel or store frontend are displaying Uncaught Error: strpos(): Argument #1 ($haystack) must be of type string, null given or you’re unable to access your store or admin area completely, you may be impacted by this issue.

    What action should I take?

    If your store is experiencing this issue, there are several things you can do to fix it while our fix propagates to all sites (we have deployed a fix, but it will take some time to reach all sites).

    • If possible, clear the ptk_patterns transient, which can be done with WP CLI:
      wp transient delete ptk_patterns --skip-themes --skip-plugins
    • Directly delete _transient_ptk_patterns from the DB (update the wp_ prefix to your db prefix)
      DELETE FROM wp_options WHERE option_name = '_transient_ptk_patterns';
    • Deactivate and reactivate WooCommerce: This can also clear the transient and resolve the error for many sites.
    • If you are unable to use the previous methods, modify the plugins/woocommerce/src/Blocks/BlockPatterns.php file and add this code block inside of the parse_categories() function.

    You can read more about this here: https://developer.woocommerce.com/2025/05/06/woocommerce-fatal-error-immediate-action-required/

    We appreciate your patience as we work to ensure all sites are updated. If you need further help, please don’t hesitate to reach out!

Viewing 4 replies - 1 through 4 (of 4 total)
Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘WooCommerce Fatal Error Alert (BlockPatterns.php)’ is closed to new replies.