c.roper
February 16, 2022, 3:09pm
#1
I am not sure any maintainers are monitoring the WordPress APO plugin’s support forum so dropping a link to the post I’ve just made in here:
Old Guzzle package causing conflicts with other plugins | WordPress.org
It looks from the forum like quite a few others are experiencing this issue.
1 Like
cbrandt
February 16, 2022, 3:36pm
#2
I see there’s already an issue and 2 pull requests on this topic at GitHub. Perhaps @yevgen could shed a light on an ETA for a solution?
opened 11:37AM - 28 Oct 21 UTC
### Confirmation
- [X] My issue isn't already found on the issue tracker.
- … [X] I have replicated my issue using the latest version of the plugin and it is still present.
### WordPress version
5.7.3
### Cloudflare-WordPress version
4.7.0
### PHP version
7.4.22
### Expected result
Guzzle versions shouldn't collide when using Composer to manage PHP dependencies. If a site is using guzzle, maybe Cloudflare should suggest that its plugin requires it and let the user install the dependency on his own.
### Actual result
Due to the way autoloading is done, the guzzle version from Cloudlare's plugin is the one that is left available for all code to use, leading to issues on how other plugins use it.
### Steps to reproduce
1. Add a custom dependency to Composer that requires Guzzle
2. Use something in the dependency that requires code not present in version ~5.0 (~7.0, for example)
2. Require Cloudflare's plugin
3. Check if the feature dependency in 1. is working
### Additional factoids
It's already mentioned, but it might be important to point out again. We're using Composer to manage our dependencies, both internal/custom and external (packgist and wpackagist).
### References
_No response_
1 Like
c.roper
February 16, 2022, 3:57pm
#3
Ah, great, thanks. Probably worth adding a link to the git repo to the plugin pages on Wordpress.org somewhere (in the development section perhaps?) - I couldn’t find it and gave up assuming there was only a SVN repo.
1 Like
yevgen
February 16, 2022, 5:31pm
#4
I shared it with API team (responsible for WordPress plugin), I hope we will sort it out, thanks for pinging.
2 Likes
system
March 3, 2022, 5:32pm
#5
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
firat
March 15, 2022, 5:06pm
#6
Hi folks, the fix should be out now. Thank you for your patience.
2 Likes