Actually, WHMCS is using the library Guzzle 5.3.1. Some new library requires to use Guzzle 6, so it may be useful to upgrade to version 6.
Thanks for your suggestion.
We monitor for updates to our dependencies and include them when security or new funcitonality we wish to leverage requres it. Due to the major version bump in Guzzle indicating backwards incompatible changes, we would likely also need to reserve such a change to a major version change of our own (eg. v6, v7, v8).
Better is the change to HTTPlug...
we have massive problems too, with that. Regarding many Modules....
Which problems are you experiencing and with which modules? We are not currently aware of any Guzzle-related issues in any of the stock modules distributed in WHMCS.
Modules with Guzzle 6 breaks the WHMCS Updates Task from the daily cron job. For example, a module with the cloudflare-sdk composer package.
Thanks for that information. It's the responsibility of the module developer to ensure that their code is compatible with the WHMCS software and its dependencies, not the other way round. The vendor would need to adjust their code to work within our current framework.
Comments have been locked on this page!