-
Notifications
You must be signed in to change notification settings - Fork 81
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
in laravel 5.5 not working, can you update plz #24
Comments
+1 |
Thanks, @sanjaylive. There's already a commit that solves this error... I will create a release soon. If you are still under development, you can try |
I've the same issue in laravel 5.5. |
check update, already solved
…On Fri, Jan 26, 2018 at 8:38 PM, Siarhei Pashkevich < ***@***.***> wrote:
I've the same issue in laravel 5.5.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AdTxi0M51yz-Jc53-WGsswUQXh-PaRjXks5tOep0gaJpZM4Q4Ozl>
.
|
I've switched to |
Please see to this issue (if you're not using |
You can try my package oanhnn/laravel-pricing-plans |
@oanhnn You could have forked this package from @gerardojbaez rather than claiming it as your own. |
@josteph Yes, it is a fork, but the license of @gerardojbaez 's package is MIT and i did refactor it 😄 |
@oanhnn, Having the MIT license doesn't mean you can claim it as yours; it clearly says that you have to preserve the Copyright along with the provided License. Please make the necessary adjustments to your repository. Refactoring someone else code doesn't make it yours. |
@gerardojbaez |
@oanhnn, Thanks for the adjustments. Your project is base on Laraplans, it doesn't matter if you have refactored it or built on top of it, the original Copyright must be included (and you already did). More information here. This is how I would do it (it is more explicit):
|
The release is out! v2.2.0 |
in laravel 5.5 not working, can you update plz
The text was updated successfully, but these errors were encountered: