Uncaught TypeError: strpos() expects parameter 1 to be string, bool given

  • Resolved scottm-ldg

    (@scottm-ldg)


    2 months ago

    Hi,

    Woocommerce seems to be throwing fatal errors. I’m wondering if anyone else is getting these errors, they seemed to start after I updated Woocommerce to 9.6.0.

    Any help on this would be greatly appreciated.

    Here is the crash report I’m getting:

    WordPress version 6.7.1
    Active theme: Goodnow Farms (version 1.0.0)
    Current plugin: WooCommerce (version 9.6.0)
    PHP version 7.4.33



    Error Details
    =============
    An error of type E_ERROR was caused in line 175 of the file .../wp-content/plugins/woocommerce/includes/class-wc-brands.php. Error message: Uncaught TypeError: strpos() expects parameter 1 to be string, bool given in .../wp-content/plugins/woocommerce/includes/class-wc-brands.php:175
    Stack trace:
    #0 .../wp-content/plugins/woocommerce/includes/class-wc-brands.php(175): strpos(false, '%')
    #1 .../wp-includes/class-wp-hook.php(326): WC_Brands->post_type_link(false, Object(WP_Post))
    #2 .../wp-includes/plugin.php(205): WP_Hook->apply_filters(false, Array)
    #3 .../wp-includes/link-template.php(375): apply_filters('post_type_link', 'https://goodnow...', Object(WP_Post), false, false)
    #4 .../wp-includes/link-template.php(201): get_post_permalink(Object(WP_Post), false, false)
    #5 .../wp-admin/includes/class-wp-posts-list-table.php(1553): get_permalink(Obj

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter scottm-ldg

    (@scottm-ldg)

    I read through the changelog for v9.6.0 and noticed there’s a new feature that integrates the Product Brands plugin into Woocommerce’s core files. I think this is where the issue coming from. Briefly viewing the class-wc-brands.php file I can see that file is related to this new feature.

    Thankfully there’s a way to disable this feature. I disabled it last night and I’ve yet to see these fatal errors again. If I do see them again, I’ll update this post.

    • This reply was modified 2 months ago by scottm-ldg.
    Plugin Support Zubair Zahid (woo-hc)

    (@doublezed2)

    Hello scottm-ldg,

    Thank you for contacting WooCommerce support.

    I am glad to know that you have found the cause of the error.
    It is likely a clash between WooCommerce’s new Brand feature with your existing brand configuration on the site.

    Let me know if the error comes back.
    I am here for your assistance.

    Have a great day!

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.