@gbell12 Thanks for the report. Yes, bizarre indeed.
The only idea I can think of at the moment is that BackupBuddy might use Font Awesome itself, and there’s an incompatibility between what it’s trying to do and what our plugin is trying to do. I don’t know how that would effect Amazon S3 interaction, specifically. But if an exception is being thrown somewhere on the server side (in the PHP code), perhaps it undermines all subsequent code, one symptom of which happens to be S3 interaction.
I’m curious to investigate it further, but I’d need some more information to do so. If you want to help track this down and can run WordPress in debug mode, maybe we can find a little more information:
https://codex.wordpress.org/Debugging_in_WordPress
I’d also like to look at the source code for BackupBuddy to see if I can spot any such interactions. Is that plugin available for public download somewhere?
See followup research on this subsequent topic.
“PHP message: PHP Fatal error: Cannot redeclare GuzzleHttp\uri_template() (previously declared in /srv/website/public_html/wp-content/plugins/font-awesome/vendor/guzzlehttp/guzzle/src/functions.php:17) in /srv/website/public_html/wp-content/plugins/backupbuddy/destinations/_s3lib3/GuzzleHttp/functions.php on line 31
@gbell12 I’m just consolidating your follow up topic here on this original topic.
Thanks for tracking down this helpful diagnostic info. I suspected that the problem had to do with a conflict over GuzzleHttp–that PHP error message confirms it. And I agree with the feedback from iThemes support: our plugin shouldn’t be re-declaring GuzzleHttp. I hadn’t intended to create that conflict, but I’ll fix it and re-release the plugin.
Thanks again for digging this out for us.
Update: after looking at this more closely, we’ve concluded that we’d like to take greater measures to avoid conflicts like this now and in the future. I’m working on a set of changes that I hope to release soon.
Hi @gbell12, thanks again for reporting this. I’ve just released version 4.0.0-rc8 that solves this problem by eliminating this whole class of potential conflicts with other plugins.
Could you give it another try?
