-
Notifications
You must be signed in to change notification settings - Fork 112
Won't install with Laravel 5.3.4 #77
Comments
Waiting on my buddies with LaravelCollective to do a release that works with 5.3 but thank for putting up an issue. |
Thanks for the update. I just didn't expect the failure as the site indicates 5.3+ and makes no mention of this issue that I could find. Thanks for the speedy response. |
lol for what it counts I didnt anticipate on the issue. I messaged the guys at LaravelCollective to help move the support forward and they simply said they've got it, should be good to go by Monday ~ish feel free to promote Laracogs to your friends too I'm always looking for new voices in the community :) |
Matt, Just got around to trying out Laracogs again, everything seemed to go php artisan vendor:publish --provider="Yab\Laracogs\LaracogsProvider" when I commented out that route from the api routes file then the command Thanks, Craig On Sat, Aug 27, 2016 at 6:44 PM, Matt Lantz notifications@github.com
|
I just created a new laravel project and it's version 5.3.4, trying to install laracogs results in a failure. Here is what happens:
Using version ^2.0 for yab/laracogs
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for yab/laracogs ^2.0 -> satisfiable by yab/laracogs[v2.0.0].
- Conclusion: remove laravel/framework v5.3.4
- Conclusion: don't install laravel/framework v5.3.4
- yab/laracogs v2.0.0 requires illuminate/support 5.3 -> satisfiable by laravel/framework[v5.3.0], illuminate/support[v5.3.0].
- Can only install one of: laravel/framework[v5.3.0, v5.3.4].
- don't install illuminate/support v5.3.0|don't install laravel/framework v5.3.4
- Installation request for laravel/framework (locked at v5.3.4, required as 5.3.*) -> satisfiable by laravel/framework[v5.3.4].
Installation failed, reverting ./composer.json to its original content.
The text was updated successfully, but these errors were encountered: