Skip to content
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

BackWPup – conflicting with Backblaze storage save #235

Open
jimiero opened this issue Aug 11, 2022 · 1 comment
Open

BackWPup – conflicting with Backblaze storage save #235

jimiero opened this issue Aug 11, 2022 · 1 comment
Assignees
Labels

Comments

@jimiero
Copy link
Collaborator

jimiero commented Aug 11, 2022

If you have this plugin installed on the website: BackWPup – WordPress Backup Plugin ( https://wordpress.org/plugins/backwpup/ ) when you try to setup Backblaze storage, it throws a critical error

I've reproduced and also a customer reported it

#0 /home/*******/public_html/wp-content/plugins/backwpup/vendor/guzzlehttp/guzzle/src/HandlerStack.php(42): GuzzleHttp\choose_handler() #1 /home/*******/public_html/wp-content/plugins/backwpup/vendor/guzzlehttp/guzzle/src/Client.php(65): GuzzleHttp\HandlerStack::create()

@Ars92 Ars92 removed the enhancement label Aug 12, 2022
@Ars92 Ars92 changed the title BackWPup – WordPress Backup Plugin - conflicting with Backblaze storage save BackWPup – conflicting with Backblaze storage save Oct 13, 2022
@Ars92
Copy link
Collaborator

Ars92 commented Oct 13, 2022

This issue is due to the fact that both XCloner and BackWPup are using different versions of Backblaze libraries.
To fix that, we should use different namespaces for vendor libraries.
mozart or php-scoper should be integrated in our deploy script to solve this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants