-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guzzle 6 throwing fatal error when other plugins are using Guzzle 7 #1
Comments
I know the problem. A lot of plugins are using guzzle. In the next version I will completely remove Guzzle. Thanks for reporting. |
I have scoped all external dependencies. Can you update the plugin and report back if everything is fine? |
I am still getting some conflict with my plugin using Guzzle. It was actually with Google Site Kit that I was requiring with Composer via Wpackagist. I removed Sitekit and all works well now. Thanks for making this update.
|
We are still seeing the same problems with Guzzle conflicts. This time with Simple History and Lara Google Analytics. |
I will try to reproduce this and will report back. |
I have tested this and it's working correctly with SiteKit, lara's analytics and simple history. Can you try to uninstall, delete and reinstall search console plugin? |
We are not seeing this issue anymore. Closing this issue to clean up my dashboard. Feel free to re-open if interested. Thanks for all of the feedback and testing those other plugins as well. :) |
Hi.
This issue was also raised on wordpress.org.
https://wordpress.org/support/topic/guzzle-6-dependency-throwing-fatal-error/
I have some other plugins that are using Guzzle 7 and it is causing a fatal error with your plugin which is running Guzzle 6.
The proposed solution mentioned here.
guzzle/guzzle#2744 (comment)
The text was updated successfully, but these errors were encountered: