• Resolved televators

    (@televators)


    I work at an agency that manages a client’s site and over the past couple of weeks it has been randomly crashing. I just finished updating all plugins and WP core to 5.2.4 and it’s still randomly and intermittently killing the site either with a WSOD or fatal PHP error. All coming from Guzzle. Client’s site has the plugin running all of the important forms so disabling until the next general release is a no-go.

    This is happening with the previous version we had, 1.5.x, and the latest. I’ve been checking error logs and the only issue is this plugin’s Guzzle killing everything seemingly at random.

    Really in a tough spot here and need some help as soon as possible.

    The page I need help with: [log in to see the link]

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

    (@constantcontact)

    Are you able to provide exact errors for the logs? Chances are that there are multiple plugins that all utilize Guzzle for their own purposes, but are on different versions. That version difference, and the nature of autoloading can cause say Plugin X’s code to make a request and our incompatible copy of Guzzle is loaded and tried to be used or vice versa.

    I know I’ve personally looked into it in the past, and it’s regrettably not the easiest thing to get around or prevent, though I still hope to find a way someday. We also have internal notes about getting our version of Guzzle updated to a newer version, but we’re not there yet.

    Thread Starter televators

    (@televators)

    Sure. Here’s one from the past hour. I can provide the whole log if it would be useful.
    [php7:error] [pid 9763] PHP Fatal error: Uncaught Symfony\\Component\\Debug\\Exception\\FatalThrowableError: Type error: Argument 3 passed to GuzzleHttp\\Client::request() must be of the type array, string given, called in /nas/content/live/embracefam/vendor/guzzlehttp/guzzle/src/Client.php on line 89 in /nas/content/live/embracefam/vendor/guzzlehttp/guzzle/src/Client.php:128\nStack trace:\n#0 /nas/content/live/embracefam/vendor/guzzlehttp/guzzle/src/Client.php(89): GuzzleHttp\\Client->request('createRequest', 'GET', 'https://api.con...')\n#1 /nas/content/live/embracefam/wp-content/plugins/constant-contact-forms/vendor/constantcontact/constantcontact/src/Ctct/Services/BaseService.php(65): GuzzleHttp\\Client->__call('createRequest', Array)\n#2 /nas/content/live/embracefam/wp-content/plugins/constant-contact-forms/vendor/constantcontact/constantcontact/src/Ctct/Services/AccountService.php(94): Ctct\\Services\\BaseService->createBaseRequest('5f5cef16-7a09-4...', 'GET', 'https://api.con...')\n#3 /nas/content/live/embracefam/wp-content/plugins/constant-contact-forms/i in /nas/content/live/embracefam/vendor/guzzlehttp/guzzle/src/Client.php on line 128

    I was digging through the other plugins we have installed and couldn’t find any Guzzle stuff, though I haven’t grep’d through yet. I’m going to do that in the morning. I have a feeling it might be one of the core MU-plugins from the host, WP Engine.

    Plugin Author Constant Contact

    (@constantcontact)

    Based on the error log above, there’s a /vendor/ folder in your /embracefam/ folder and that one has a copy of Guzzle in it.

    #0 /nas/content/live/embracefam/vendor/guzzlehttp/guzzle/src/Client.php(89): GuzzleHttp\\Client->request(‘createRequest’, ‘GET’, ‘https://api.con…’)
    #1 /nas/content/live/embracefam/wp-content/plugins/constant-contact-forms/vendor/constantcontact/constantcontact/src/Ctct/Services/BaseService.php(65):

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Plugin randomly crashing site, even after latest core and plugin updates. Guzzle’ is closed to new replies.