Closed jmichaelterenin closed 4 years ago
Hello there! Thanks for opening your first issue on this repo!
Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.
Backpack communication mediums:
backpack-for-laravel
tag;Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.
Thank you!
-- Justin Case The Backpack Robot
Hello @jmichaelterenin
Thanks for interest in Backpack. The problem is clearly stated: you are using an unsuported version of cviebrock/eloquent-sluggable
Can you update cviebrock/eloquent-sluggable
to version 6.0^
or completely delete it from composer so backpack news will require the correct version to work with.
Best, Pedro
Thanks for replying @pxpm,
But version 6.0 of cviebrock/eloquent-sluggable is for Laravel 6, and says so in its documentation. I am using Laravel 5.8. I cannot currently upgrade to 6 because this is an existing project that is using packages not yet available for Laravel 6.
I bring this up here because the NewCrud documentation states that it's available for Laravel 5.8.
@tabacitu, can you please provide some insight? Is this NEWSCrud package really available for Laravel 5.8, and if so, what version should I be pulling so that there's no dependency issue with cviebrock/eloquent-sluggable?
@jmichaelterenin we're on it.
@pxpm came up with a possible solution: for us to require version 6.0|5.8
in our composer.json
. He'll be working on draft fix ASAP, and get back to you to test it. If it works for you, we'll merge it for everyone.
Cheers!
Hello @jmichaelterenin !
Just created a fresh laravel 5.8 project and added NewsCRUD. Could you please test if it's working on your side ?
I will need you to do:
composer require backpack/newscrud:dev-dev-version
Instead of the require that is presented in intallation instructions.
Please let me know if it works for you so we can push this fix to everybody :)
Best, Pedro
@pxpm, @tabacitu I apologize for the delay, I had some personal things to attend to. I was able to complete installation (Installation type (B) - package) ,and although I haven't had the time just yet to add any dummy/test data to see it in action, I have to assume we got past the issue that presented itself originally.
Thank you for your assistance, and taking the time to adjust things for Laravel 5.8. I want to be able to eventually move our existing Admin to Backpack, and once I've done so, we'll upgrade to 6.0. That will take a couple of months though, so again, I appreciate your efforts.
I will let either one of you close out this thread.
Great. Thank you @jmichaelterenin . Made PR https://github.com/Laravel-Backpack/NewsCRUD/pull/40 out of @pxpm 's branch, and merged it into master
. The fix should now be available to everyone as NewsCRUD 3.0.1.
Cheers!
Bug report
What I did:
I've purchased a commercial licensed version of Laravel Backpack 4.0.23. I have an existing project where I've been using cviebrock\eloquent-sluggable for some time now. I recently upgraded it to v4.8
What I expected to happen:
I wanted to install the NewsCRUD package, and assumed it would install as Laravel Backpack did, without any problems.
What happened:
What I've already tried to fix it:
I've searched in Issues for anyone experiencing this problem, but nothing came up.
Backpack, Laravel, PHP, DB version:
Backpack 4.0.23, Laravel 5.8, PHP 7.2.24