-
Notifications
You must be signed in to change notification settings - Fork 14
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
Class Not found #20
Comments
I got the same problem. Does anyone know any solution? |
I had the same issue, but managed to get it working by installing the ClickSend SDK in a fresh project (rather than adding it to a Laravel one). So there seems to be some sort of clash with the autoload / namespacing? |
After further investigation I noticed that my fresh project was installing v5.0.64 of I tried to manually force my laravel project to install v5.0.64, but I received a guzzle clash:
|
I can get it working on laravel by removing the following
It then successfully makes the API call to ClickSend - although not sure which parts of Laravel need guzzle v7 |
Okay, think I've found the best solution:
|
@jacksegal Thank You , works like a charm !! |
@jacksegal rather than suggesting people use your fork, you can PR your change to the upstream repo for me (not using Laravel, so I don't have the same deps as you), the fix was:
While the version bump might fix your composer issue, you may or may not find that ClickSend is fully compatible with v7 of Guzzle. The requirement really only wants to be changed if it's required. If ClickSend is compatible with multiple releases of Guzzle then Composer supports multiple versions eg |
Thanks @xurizaemon - there is actually already an issue open for them to update their dependencies: #23. I was just letting people know there was a manual workaround to their problem 👍 |
I get that, but it's no small task taking on maintenance of a fork; you really should consider
Best of luck! 😁 |
When I install the package through composer and tried for a test call, it says,
Class ClickSend\Configuration' not found
The text was updated successfully, but these errors were encountered: