Hi @alanhericvoro,
Which WordPress plugin using the AWS PHP SDK is causing the errors? Can then look to plan a way forward.
Appreciate the feedback
Hi Mark,
It is a custom solution incorporated into theme files. It is using AWS SDK for PHP as a dependency via Composer. Latest version.
My troubleshooting led me to your plugin and older version of Guzzle. If I deactivate your plugin the code works just fine.
From what I can see you are using 7.3.0 – 2021-03-23 and AWS SDK requires 7.8.1 – 2023-12-03
Thanks @alanhericvoro
We were hoping to avoid this situation by re-namespacing Guzzle like
namespace SMTP2GOWPPlugin\GuzzleHttp;
I think generally this solution had stopped Guzzle conflicts, however in your custom setup it looks like it isn’t sorting this. We will look to update Guzzle in an upcoming release of the plugin: will probably be a couple of weeks away as we have an interim release planned for next week just updating WordPress version compatibility and our pre-release testing process
Really appreciate the feedback, thank you
Hi, Sorry for the lack of updates here. We have been focusing on our testing / automated testing of upcoming plugin releases. We have a version nearly ready to go with the Guzzle client updates, but are really focusing on our testing procedure right now and getting this right
Hi @alanhericvoro , just confirming the latest release from a week ago went out with an updated Guzzle version which should sort your issue
I am also having issues with the Guzzle version and the backup plugin BackWPup
Hi gsts47
Thanks for the feedback, could I get you to submit a support request to SMTP2GO here https://support.smtp2go.com/hc/en-gb/requests/new please and include a copy of the Sitehealth info for your installation /wp-admin/site-health.php?tab=debug
Then I can check versions and debug further
Thanks
