Viewing 1 replies (of 1 total)
  • Plugin Author Chris Lagasse

    (@soben)

    Hey mebishwak,

    The issue actually stems from another plugin using an older version of Guzzle, not an issue with other HubSpot plugins.

    I am going to try to push up a new version this week that will check for that function (Client::request) when activating, in order to throw a conflict warning and keep this plugin deactivated, because you are not the first to encounter this.

    As for solutions to the problem… there aren’t many on my end. There is a conflicting plugin that’s also using Guzzle. A cursory glimpse of your plugin list has shown no known outliers that I’ve dealt with previously, but a file search can turn up the culprit.

    There isn’t many solutions on my end because my only real option is to prevent you from using the plugin at all with a proper warning (instead of crashing)… The other “option” is to downgrade my version of Guzzle, but that introduces security concerns (it’s better to be on newer versions).

    Let me know if you have any luck finding the culprit?

Viewing 1 replies (of 1 total)
  • The topic ‘Fatal error: Call to undefined method GuzzleHttp\Client::request()’ is closed to new replies.