Skip to content
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

Update from 2.1.0 to 2.1.2 breaks compatibility #1204

Closed
knallcharge opened this issue Aug 26, 2020 · 1 comment
Closed

Update from 2.1.0 to 2.1.2 breaks compatibility #1204

knallcharge opened this issue Aug 26, 2020 · 1 comment

Comments

@knallcharge
Copy link

Hi,

I just updated the DoctrineBundle from version 2.1.0 to 2.1.2 and am getting errors in some external libraries that include classes with changed paths/namescapes. Don't know if this is the bundle itself or the dependencies it pulls (doctrine/persistence 1.3.8 => 2.0.0, doctrine/common 2.13.3 => 3.0.2).

Here are two errors I'm getting for Tetranz\Select2EntityBundle and Sg\DatatablesBundle:
Argument 1 passed to Tetranz\Select2EntityBundle\Form\Type\Select2EntityType::__construct() must be an instance of Doctrine\Common\Persistence\ManagerRegistry, instance of Doctrine\Bundle\DoctrineBundle\Registry given

Argument 1 passed to Sg\DatatablesBundle\Datatable\Column\ColumnBuilder::__construct() must be an instance of Doctrine\Common\Persistence\Mapping\ClassMetadata, instance of Doctrine\ORM\Mapping\ClassMetadata given

Downgrading DoctrineBundle to 2.1.0 resolved the problem.

@ostrolucky
Copy link
Member

There is nothing we can do here unfortunately, this is transitive dependency problem. Please open the bug in the bundle, asking them to support doctrine/persistence. Meanwhile, explicitly require doctrine/persistence:^1 in your project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants