• lena3223

    (@lena3223)


    Hi, we have updated plugin to 2.8.9 and after this we started getting errors in our log:
    Call to undefined method GuzzleHttp\Utils::chooseHandler() in /public/wp-content/plugins/svea-checkout-for-woocommerce/vendor/guzzlehttp/guzzle/src/functions.php:61
    The files users upload on the cart page don’t appear on the order page.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author The Generation

    (@thegeneration)

    Hi,

    There is probably a plugin or theme that depends on the package “Guzzle” but is using a version below 7.0. The Svea-connection depends on Guzzle 7.8.0. Since the package (Guzzle) will only be loaded once, this other plugin/theme is probably initialized before our module and creating issues with the Svea connection.

    See if you can find which other package is using Guzzle and if they have an updated version that depends on Guzzle >7.0.

    Are there issues with payments that you’ve seen together with this error message?

    Kind regards,
    The Generation

    Thread Starter lena3223

    (@lena3223)

    Thank you, we didn’t notice the other issues except this one.
    I will update all plugins and let you know.

    Plugin Author The Generation

    (@thegeneration)

    Okay that’s good to know. Great!

    Thread Starter lena3223

    (@lena3223)

    I found two plugins that use Guzzle (Yoast Seo and SMTP Mailer), updated them but the problem remains. Both these plugins use for Guzzle ‘vendor_prefixed’ folder, so it shouldn’t be the reason?

    Thread Starter lena3223

    (@lena3223)

    Sorry, I found the other plugin which use Guzzle, when I update it I will let you know.

    Thread Starter lena3223

    (@lena3223)

    Hi, I have updated the last plugin which use Guzzle, and from now on I get new error:
    PHP Fatal error: Uncaught Error: Undefined constant GuzzleHttp\ClientInterface::MAJOR_VERSION in /www/expofyse_725/public/wp-content/plugins/svea-checkout-for-woocommerce/vendor/guzzlehttp/guzzle/src/Utils.php:116

    Plugin Author The Generation

    (@thegeneration)

    Hi,

    There’s likely still a conflict somewhere causing this error. You can try disabling plugins one by one to identify where the issue is.

    Best regards

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