Installing 4.1 on Laravel 8
See original GitHub issueBug report
What I did
Ran
composer require backpack/crud:"4.1.*
to install on Laravel 8
What I expected to happen
It to install
What happened
Received the following error.
Your requirements could not be resolved to an installable set of packages.
Problem 1
- backpack/crud[4.1.22, ..., 4.1.x-dev] require doctrine/dbal ^2.5 -> found doctrine/dbal[v2.5.0-BETA2, ..., 2.12.x-dev] but it conflicts with your root composer.json require (^3.0).
- backpack/crud[4.1.0, ..., 4.1.21] require laravel/framework ^7.0|^6.0 -> found laravel/framework[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev] but it conflicts with your root composer.json require (^8.12).
- Root composer.json requires backpack/crud 4.1.* -> satisfiable by backpack/crud[4.1.0, ..., 4.1.x-dev].
What I’ve already tried to fix it
I have tried to google for a solution but not found one.
Backpack, Laravel, PHP, DB version
Laravel 8.17 PHP 7.3.24
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Installing Laravel Backpack 4.1 into Laravel 8 - Stack Overflow
I am trying to install Backpack 4.1 into Laravel 8. I ran composer require backpack/crud:"4.1.*". But I received the following error.
Read more >Installation - Laravel - The PHP Framework For Web Artisans
The first thing you should do after installing Laravel is set your application key to a random string. If you installed Laravel via...
Read more >Installation | Laravel Mix Documentation
Laravel Project · Install Laravel · Run npm install · Visit your webpack.mix.js file, and get started!
Read more >Chatify Not Installing - Laracasts
0.0, ..., v1.0.1] require pusher/pusher-php-server ^3.4@dev -> found pusher/pusher-php-server[v3.4.0, v3.4.1] but the package is fixed to v5.0.1 (lock file ...
Read more >Installation :: 5.x Docs - Backpack for Laravel
RequirementsIf you can run Laravel 8 or 9, you can install Backpack. Backpack does not have additional requirements. For the following process, we...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have fixed this by removing doctrine/dbal and installing
Hi guys,
Indeed, Laravel 8 supports PHP 8, but it also supports both DBAL v2.5+ and DBAL v3.x. Backpack does support PHP 8 in the latest version, but it does not yet support DBAL v3 (see https://github.com/Laravel-Backpack/CRUD/pull/3517). We do plan to add DBAL v3 support but it could take a few days - and depending on what we find it’s possible that it’ll be a breaking change.
If you don’t have a reason to explicitly ask for DBAL v3 (you don’t use DBAL v3 features in your code), I recommend you remove the
doctrine/dbal
composer dependency in your project and runcomposer update
- that should have the same result as @lotarbo and @MikePageDev 's solution. Doctrine/dbal v2.12.x does support PHP 8, so it should work just fine.If you have a dependency that needs DBAL v3, however, since Backpack doesn’t yet support DBAL v3… that’s where you have a problem. The only thing to do in that case is to wait from upgrading that dependency, until we manage to add DBAL v3 support in Backpack. Hopefully we’ll be able to do so in a non-breaking manner 🤞
Cheers!