Closed doits closed 1 year ago
Is your server running php 8.x?
Thanks for your help. It is indeed running v7.4.3. Can this be the cause of the error?
Yes, that is probably the reason. Composer will install a newer version of DBAL when PHP is upgraded
Make sure to run composer update
after you update the PHP version on the server
I run composer update
before running the migrations, so it should be up to date.
I just checked it installs doctrine/dbal
3.6.3
(latest version) even with my php 7
version, and with this version the migration failed.
According to https://stackoverflow.com/a/65075035 the downgrade fixes the error about the missing class (which it did for me). Looks like the class does not exist in dbal
3
, see https://github.com/doctrine/dbal/issues/4439? For me it looks like there might be an error using Doctrine\DBAL\Driver\PDOMySql\Driver
with dbal
3
, but this is just a guess.
I will update to php 8
soon to be on the supported version – for now everything seems to work even with php 7
after the migration completed with the old dbal
2
version.
Aah probably it is because illumniate/database
is incompatible with dbal
3
... it installs v7.30.6
for me, probably the later versions are not compatible with php 7
.
Seems to be only supported from v8.15.0
onwards, see https://github.com/laravel/framework/releases/tag/v8.15.0
Added Support DBAL v3.0 (https://github.com/laravel/framework/pull/35236)
I don't think we want to keep supporting EOL versions of PHP, so I'm closing this issue. I think we need to update the docs so it's clear that PHP 7 is not supported anymore in MunkiReport 5.8
When upgrading I git this error running the migrations:
Changing
composer.json
to require an olderdoctrine/dbal
fixes it:Looks like the migration is not compatible with newer
dbal
?I reverted the change after the migrations completed, but I'm not sure what should be the correct version in the end.