Critical Error Plugin Conflict

  • Resolved Pi Programs

    (@piprograms)


    3 years, 10 months ago

    Hello,

    I am trying to use a new plugin on my site, this one: https://1teamsoftware.com/product/woocommerce-easypost-shipping-pro/

    And every time I activate it I get this critical error. It has something to do with your plugin as stated in the error:

    2022-07-21T13:27:03+00:00 CRITICAL Uncaught TypeError: Argument 3 passed to GuzzleHttp\Client::request() must be of the type array, string given, called in /home/u754089127/domains/franklymydear.tv/public_html/wp-content/plugins/wc-easypost-shipping-pro/vendor/guzzlehttp/guzzle/src/Client.php on line 92 and defined in /home/u754089127/domains/franklymydear.tv/public_html/wp-content/plugins/wc-easypost-shipping-pro/vendor/guzzlehttp/guzzle/src/Client.php:184
Stack trace:
#0 /home/u754089127/domains/franklymydear.tv/public_html/wp-content/plugins/wc-easypost-shipping-pro/vendor/guzzlehttp/guzzle/src/Client.php(92): GuzzleHttp\Client->request('createRequest', 'GET', 'https://api.con...')
#1 /home/u754089127/domains/franklymydear.tv/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/constantcontact/src/Ctct/Services/BaseService.php(65): GuzzleHttp\Client->__call('createRequest', Array)
#2 /home/u754089127/domains/franklymydear.tv/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/constantcontact/ in /home/u754089127/domains/franklymydear.tv/public_html/wp-content/plugins/wc-easypost-shipping-pro/vendor/guzzlehttp/guzzle/src/Client.php on line 184

    Any ideas on how to fix this? Please and thank you.

Viewing 1 replies (of 1 total)
  • Plugin Author Constant Contact

    (@constantcontact)

    3 years, 10 months ago

    Hi @piprograms

    Hmm. Looks like both our plugin and the wc-easypost-shipping-pro plugin use a library called GuzzleHTTP but they’re different incompatible versions, and one plugin is inadvertantly trying to use the version bundled with the other plugin.

    I know we’ve experienced this in the past with some plugins, but never managed to find a solution that we were ready to ship either. I believe longer term, we’re aiming to move away from using Guzzle ourselves, but we’re not at that point yet.

    Sadly I also don’t have a great solution for this right now, outside of deactivating ours temporarily.

Viewing 1 replies (of 1 total)

The topic ‘Critical Error Plugin Conflict’ is closed to new replies.