not compatible with other plugins that use newer Guzzle
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 95
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
the plugin breaks in admin settings when there's another plugin that uses GuzzleHttp and composer vendor autoloader.
the plugin would probably work if both guzzlehttp versions were the same, but in most cases all plugin providers use their own.
their guzzleClient:
6.4.1
your guzzleClient
6.3.3
Please do not load classes that other plugins can provide with different versions or only load yours when in scope of backwpup.
Probably wrapping it within something like or whatever works for within-plugin scope
if( stristr($_SERVER['REQUEST_URI'],'backwpup')) {
require_once $autoloader;
}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the admin-settings failure with another plugin using GuzzleHttp 6.4.1 and BackWPup's composer vendor autoloader loading its 6.3.3 client. Inspect where the autoloader is required and verify that both plugins can coexist without class conflicts. Done means BackWPup still works in its admin scope while the other plugin's Guzzle classes remain usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100