Support » Plugin: Google Listings & Ads » Guzzle error

  • Resolved dr

    (@daniel_richard)


    Hi Support,

    I’m getting a weird GuzzleHttp error, although I’ve yet to identify which plugin is conflicting with this.

    Fatal error: Uncaught Error: Call to undefined function Automattic\WooCommerce\GoogleListingsAndAds\Vendor\GuzzleHttp\Psr7\stream_for()

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Niall a11n

    (@wpniall)

    Hi @daniel_richard,

    Thanks for reaching out to us about the GuzzleHttp error and conflict with Google Listings & Ads!

    I suspect the issue here is that your site uses an older version of the plugin. The reason I am suspecting that is because the GuzzleHttp conflict was fixed in the latest 1.1.0 version of the plugin.

    Could you please make sure you have updated to version 1.1.0?

    If you are using version 1.1.0 and are still seeing the same error, please let us know so we can help you further. Thank you!

    Thread Starter dr

    (@daniel_richard)

    Hi Niall,

    It’s already at the 1.1.0 version.

    Tried troubleshooting, where all plugins off and on wasn’t able to solve it (except all plugins off, except for GLA, would then finally connect).

    Tried with 3 stores with similar setups, only 1 of it doesn’t seem to connect at all.

    At step 1, the error would be:
    “There was an error loading Jetpack account info.”

    And the error log would show:

    Fatal error: Uncaught Error: Call to undefined function Automattic\WooCommerce\GoogleListingsAndAds\Vendor\GuzzleHttp\Psr7\stream_for() in /public_html/wp-content/plugins/google-listings-and-ads/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:400

    Context
    URL /wp-json/wc/gla/jetpack/connected?_locale=user
    HTTP Method GET
    Current Filter parse_request

    Would there be any other angle that I may have yet to try to solve this?

    Thanks for following up!

    Plugin Support Austin M – A11n

    (@apmwebdev)

    Hi @daniel_richard. Thanks for the additional information.

    Would there be any other angle that I may have yet to try to solve this?

    Yes, it looks like there might be an issue with Jetpack. Could you try disconnecting and reconnecting Jetpack, as described here: https://jetpack.com/support/reconnecting-reinstalling-jetpack/

    Let us know how that goes and we’ll go from there!

    Thread Starter dr

    (@daniel_richard)

    Hi Austin!

    After troubleshooting the issue again (yeah, went to look for other plugins that may be using GuzzleHttp and cURLFactory) and found the plugin that is causing the conflict.

    I’ve informed the developer of the other plugin about the issue.

    Marking this as resolved. Thanks again for the quick support responses! 🙂

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