Hey dustingtaylor,
I’ve encountered this once before, and it’s because there’s another plugin also using Guzzle, and unfortunately using an outdated version.
I will try to provide an additional check to make sure that method exists, but you still would require to update the Guzzle on a different plugin/theme in order to use our plugin, unfortunately.
Hi Chris,
I’ve noticed that the only other plugin that uses Guzzle is w3-total-cache. Would that be the culprit?
Hey Dustin,
Possibly. The issue is that Guzzle has been updated, and W3 is loading before our plugin, so it’s loading their version of Guzzle. I’m assuming all of your plugins are up to date?
We do not have any sites that run W3 Total Cache, in preference for other caching solutions (especially ones provided by our host at WPEngine)… so I’ll need to get that plugin installed locally and check for conflicts.
I may look into a “dev-specific” version of our plugin that won’t be updated here, but accomplishes the same thing, that runs an earlier version of Guzzle. I will have to tinker with that. We have another client who has problems due to PHP versioning, and both problems may be solved in the same situation.
