I wrote it before your post:
I need also not to inactivate neither BackWpUp because I need it to maintain a DR copy of the site, nor Simply Calendar. Then, until the developer of Simply Calendar solves the issue you can downgrade Simply Calendar to the previous version 3.1.32:
In the main WordPress plugin page:
On the right side, where “version, last update …. and Tags for the plugin” are located.
Under the Tags you will see a link labeled “Advanced view” press it or follow this:
Now on the new page go down under statistics graphs and you will find a drop down box or select box labeled Development Version. If you press the arrow button you will find among others: the development version, and several previous versions from 3.1.32 to 0.1 … select one that works for you.
I could survive now with the 3.1.32
Yes, the internal upgrade inside SImplyCalendar of some vendor plugins to last version, in particular “guzzlehttp” to last version available conflicts with the version used by other pluggins like BackWpUIp [in my case and others] or with “WP File Download Cloud Addon” in your case.
I solved my issue like yours with a downgrade of SimnplyCalendar to 3.1.32.
I encourage the developer to solve this issue as soon as possible.
Thanks in advance
Fix: Trimmed overall size of the plugin to reduce errors from installation failing.
Dev: Updated minimum PHP requirement to 7.3
Dev: Updated all vendor packages to latest versions.
Dev: Tested up to WordPress 5.5.1
Thanks very much for the clear directions for us all.
Downgraded and awaiting the fix.
Just FYI, the issue come from the fact that the plugin author now uses a third party package Guzzle Version 7 – which is seems there is a clash when another plugin has loaded Guzzle Version 6.
I haven’t investigated exactly why there is clash between 6 & 7 but the obvious fix would be to revert to version 6, or detect if the V6 is loaded before loading
I’m researching hoe to circumnavigate this issue, because I’ve other developments that use this type of inconveniences. If I can find a solution I will propose the developer to test it and incorporate on a future release
@ignaciojesus …. well done! Thanks for helping the dev with this. We’re all hoping for a solution in the near future 🙂
Just chiming in to say we have the same issue. Rolling back a version fixes it.
The issue with the conflict with backwpup comes from the usage of unscoped dependencies / vendor folders.
Please scope (composer) dependencies / vendor folders to prevent such issues when multiple plugins use the same classes but with different interfaces and implementations.
See also https://github.com/wp-media/wp-rocket/issues/3005 for proposed solutions.
Going to report the same to the backwup developers.
I have the same issue: wp-content/plugins/google-calendar-events/vendor/guzzlehttp/guzzle/src/Utils.php on line 121
I rolled back Simple Calendar one version, and it’s working again.
Doesn’t seem that any updates have been made by Simple Calendar. They are sticking with 3.1.33
- This reply was modified 2 years, 3 months ago by mkornegay2.
Also stuck on 3.1.32 because of the Guzzle bug. Any ETA on a fix?
Echoing the above, and subscribed to this thread. Can provide system info export if needed.
PHP Fatal error: Uncaught Error: Call to undefined method GuzzleHttp\Utils::chooseHandler() in /wp-content/plugins/google-calendar-events/vendor/guzzlehttp/guzzle/src/functions.php:61
+1 here as well.
It would be nice if the dev would pipe in. He/She created such a fantastic plugin.
We understand these volunteer projects can be time consuming to maintain.
Could the dev lean on some of the generous offers made by other gurus here to help fix the issue?
We’d all be very grateful.
- The topic ‘Update to 3.1.33 Broke My Site’ is closed to new replies.