Thread Starter
Carin
(@sparksfreebies)
I just realized the plugin had been renamed on the last break with OLD on the end of folder name , but somehow I was able to activate it even with the OLD on folder name (and it never got removed) , I just went in through file manage and removed the OLD, do you think that was the problem?
Good morning @sparksfreebies
The folder name shouldn’t make any difference for functionality of the plugin.
Is the error still happening, or did that part resolve itself?
Any news or changes here Carin?
Thread Starter
Carin
(@sparksfreebies)
Hi thanks for asking! I have not reactivated the plugin yet because owner was collecting signups for a retreat, I will do so soon, but with the error above, did you see anything important I should be aware of?
The biggest thing going with the error is that it simply timed out trying to connect from your hosting server to our Constant Contact servers.
Will need to be re-tested when you’re able to, after the retreat signup window has closed. However, there’s not going to be much we can do from the standpoint of our plugin’s code to resolve that part. What we would be able to do, and are aiming to with 1.6.0, is better handling of errors like this where we at least don’t take the entirety of the website down.
We are having the same issue and it takes down our site when people try to register for an account:
[10-Jul-2019 15:31:38 UTC] PHP Fatal error: Uncaught TypeError: Argument 3 passed to GuzzleHttp\Client::request() must be of the type array, string given, called in /home/leoadventures/public_html/wp-content/plugins/backwpup/vendor/guzzlehttp/guzzle/src/Client.php on line 89 and defined in /home/leoadventures/public_html/wp-content/plugins/backwpup/vendor/guzzlehttp/guzzle/src/Client.php:128
Stack trace:
#0 /home/leoadventures/public_html/wp-content/plugins/backwpup/vendor/guzzlehttp/guzzle/src/Client.php(89): GuzzleHttp\Client->request(‘createRequest’, ‘GET’, ‘https://api.con…’)
#1 /home/leoadventures/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/constantcontact/src/Ctct/Services/BaseService.php(65): GuzzleHttp\Client->__call(‘createRequest’, Array)
#2 /home/leoadventures/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/constantcontact/src/Ctct/Services/ContactService.php(36): Ctct\Services\BaseService->createBaseRequest(‘c8fdb5dd-634f-4…’, ‘GET’, ‘https://api.con…’)
#3 /home/leoadventur in /home/leoadventures/public_html/wp-content/plugins/backwpup/vendor/guzzlehttp/guzzle/src/Client.php on line 128
Ok actually it looks like the issue is your plugin conflicts with the new version of BackWPup
@contemplate yours is similar in that there are errors occurring, but the source of your errors are different than that of Carin’s
Ultimately, both BackWPup and our plugin are both using a library named Guzzle, but they’re on different versions. Ours is very likely the older one because we’re still technically supporting some older versions of PHP that necessitate the older Guzzle.
The issue is that BackWPup starts its work, but due to things in the proverbial backend, our copy is getting found and loaded first. At that point is when the conflict comes into play. We sadly don’t have a solution for this readily available, but we are looking into bumping our minimum supported PHP that would allow us to consequently upgrade our Guzzle as well. It’s our hope that at that point, errors like yours and some other peoples’ will go away.
Is there any possibility to add a check first if the Guzzle library exists elsewhere OR if the backWPup plugin is installed to not load your library?
We had to disable the backwpup plugin to stop our site from crashing.
We wish it were as easy as that, but the two still need to use their own and there’s no great way to direct them to the right spots, even with checks for existing loaded libraries.
