Constant Contact Forms is not working

I have found issue now the plugin is conflict with wp smtp pro plugin.

we are getting below error

PHP Fatal error: Uncaught TypeError: Argument 3 passed to GuzzleHttp\Client::request() must be of the type array, string given, called in /home/.cloudwaysapps.com/eptnkcmecv/public_html/wp-content/plugins/wp-mail-smtp-pro/vendor/guzzlehttp/guzzle/src/Client.php on line 95 and defined in /home/.cloudwaysapps.com/eptnkcmecv/public_html/wp-content/plugins/wp-mail-smtp-pro/vendor/guzzlehttp/guzzle/src/Client.php:179

Uncaught TypeError: Argument 3 passed to GuzzleHttp\\Client::request() must be of the type array, string given, called in /home/.cloudwaysapps.com/eptnkcmecv/public_html/wp-content/plugins/wp-mail-smtp-pro/vendor/guzzlehttp/guzzle/src/Client.php on line 95 and defined in /home/.cloudwaysapps.com/eptnkcmecv/public_html/wp-content/plugins/wp-mail-smtp-pro/vendor/guzzlehttp/guzzle/src/Client.php:179\nStack trace:\n#0 /home/.cloudwaysapps.com/eptnkcmecv/public_html/wp-content/plugins/wp-mail-smtp-pro/vendor/guzzlehttp/guzzle/src/Client.php(95): GuzzleHttp\\Client->request(‘createRequest’, ‘GET’, ‘https://api.con…’)\n#1 /home/.cloudwaysapps.com/eptnkcmecv/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/constantcontact/src/Ctct/Services/BaseService.php(65): GuzzleHttp\\Client->__call(‘createRequest’, Array)\n#2 /home/.cloudwaysapps.com/eptnkcmecv/public_html/wp-content/plugins/constant-contact-forms/vendor/constantconta…’,

Hi @saruncloudspring

These are actually completely separate issues.

For the reCAPTCHA issue, you’ll need to make sure that the site domain that you have the plugin on is in the allowed domains list inside your reCAPTCHA settings. As is, it seems like you may be experiencing a number of various validation issues.

Are you able to share the domain for your site?

Regarding the send issue, looks like a new case of conflicts between our plugin and a different that are both using a library named Guzzle, and on different versions of it. I suspect ours is the older of the two at the moment. We haven’t found a great way to handle these conflicts yet.

Is it persistently happening for you? or was it perhaps a one time issue thus far?

@constantcontact To avoid conflicts, you should use php-scoper to rename your dependencies to something unique.

https://github.com/humbug/php-scoper
https://deliciousbrains.com/php-scoper-namespace-composer-depencies/
https://developer.yoast.com/blog/safely-using-php-dependencies-in-the-wordpress-ecosystem/

@jtree5757 noted and passing this along for consideration. Thanks.

I already contacted the WP SMTP plugin regarding the issue their reply is following

“it looks like the Constant Contact Forms plugin is using an older version of the Guzzle library (v5.3.1), while we are using v6.5.5. That’s why the error occurs.

We are working on a solution to these 3rd party library conflicts and it should be available in the next plugin update. We currently don’t have an exact date of when that will be.

Right now, the only solution is to disable one of the plugins. Or maybe contact the support of that plugin and ask them if they are able to update the Guzzle library in their plugin.

”

So we cant disable both plugins now, Both are essentials plugins for us.
So, please provide a solution to avoid these conflicts.

Thanks

We’ll be in a similar situation regarding not being able to provide an exact date for when a compatible version would be available. That said, if and as needed, we do wholly support making use of the embed forms generated in your constantcontact.com dashboard as well, when other things like this arise. Both are valid ways to get your marketing handled and contacts collected.

I have raised the awareness of the conflict internally so that we can continue evaluating and making some decisions around this.