Plugin Causes Fatal Error with EasyAzon

  • Resolved monicamatthews7

    (@monicamatthews7)


    6 years, 6 months ago

    EasyAzon (Amazon Affiliate plugin) had a mandatory update (mandated by Amazon) and because of it, my Constant Contact plugin causes this error on my site:

    Fatal error: Uncaught TypeError: Argument 1 passed to GuzzleHttp\Client::send() must be an instance of GuzzleHttp\Message\RequestInterface, instance of GuzzleHttp\Psr7\Request given, called in /home/how2wins/public_html/wp-content/plugins/easyazon/vendor/thewirecutter/paapi5-php-sdk/src/com/amazon/paapi5/v1/api/DefaultApi.php on line 416 and defined in /home/how2wins/public_html/wp-content/plugins/constant-contact-forms/vendor/guzzlehttp/guzzle/src/Client.php:158 Stack trace: #0 /home/how2wins/public_html/wp-content/plugins/easyazon/vendor/thewirecutter/paapi5-php-sdk/src/com/amazon/paapi5/v1/api/DefaultApi.php(416): GuzzleHttp\Client->send(Object(GuzzleHttp\Psr7\Request), Array) #1 /home/how2wins/public_html/wp-content/plugins/easyazon/vendor/thewirecutter/paapi5-php-sdk/src/com/amazon/paapi5/v1/api/DefaultApi.php(395): Amazon\ProductAdvertisingAPI\v1\com\amazon\paapi5\v1\api\DefaultApi->getItemsWithHttpInfo(Object(Amazon\ProductAdvertisingAPI\v1\com\amazon\paapi5\v1\GetItemsRequest)) #2 /home/how2wins/public_html/wp-con in /home/how2wins/public_html/wp-content/plugins/constant-contact-forms/vendor/guzzlehttp/guzzle/src/Client.php on line 158
    The site is experiencing technical difficulties.

    WHAT DO I DO? I had to deactivate my Constant Contact plugin to get rid of this error.

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

    (@monicamatthews7)

    6 years, 6 months ago

    This is what I was told by EasyAzon:

    Hi Monica,

    I had our developer look into this fatal error and there isn’t a workaround for this, unfortunately.
    ​
    The version of Guzzle included with our plugin is 6.4.1 (released on 2019-10-23). The version of Guzzle in the Constant Contact plugin is 5.3.3 (the last non-compatibility release of 5.3 was in 2015). Constant Contact is using a very old version of Guzzle which they should update to the most recent possible version. Guzzle sends network requests to remote APIs (In our case to the PA API 5.0 that we have to use from Amazon)

    The only solution would be for them to update their plugin from the outdated version or to discontinue the use of the Constant Contact plugin or the EasyAzon plugin. The challenge with WordPress is that because there are thousands of plugins it’s impossible for us to guarantee EasyAzon can use with every single plugin out there.

    Plugin Author Constant Contact

    (@constantcontact)

    6 years, 6 months ago

    Your developer has the all in all gist of it. We aren’t quite on one of the newest versions of the Guzzle library yet, and it’s not the first time this has caused conflicts. We’ve also come to the conclusion that it’s very difficult to avoid these conflicts as well.

    That said, it is in our roadmap to work on, but we’re not there yet.

    As an alternative, in the event that you’re absolutely not able to move away from EasyAzon, there’s still the ability to do Constant Contact Form embeds from your dashboard in constantcontact.com, which is a separate thing from the plugin here. Unsure if that’s something you had been using previously and were moving away from, or was perhaps an alternative solution you had in mind.

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

The topic ‘Plugin Causes Fatal Error with EasyAzon’ is closed to new replies.