-
Notifications
You must be signed in to change notification settings - Fork 380
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
Incompatible with symfony v7.0.3 #477
Comments
Is your composer.json have this line :
|
@ph-il, thank you for the response. Unfortunately, the alteration didn't resolve the issue either. The problem stems from DoctrineExtensions, which is one of the dependencies. It appears that DoctrineExtensions is not compatible with doctrine/orm 3.0. This incompatibility has been acknowledged as conflicts on the following page: https://github.com/doctrine-extensions/DoctrineExtensions/blob/f5b6385b3c0131c022f91a74ca15214fe3007be8/composer.json#L76. It appears so.
|
Unfortunately I have to confirm this as well. Whilst setting up a brand new Symfony 7 installation I came across the same troubles with ORM 3.0 in conjunction with Hopefully these will be resolved soon as my platform heavily depends on this functionality. |
You can solve it with this line in userland code. Maybe restrict dbal to v3 as well. |
the Gedmo extensions that are configured by this bundle are not yet compatible with doctrine/orm 3.0 (the maintainers are working on it, but they are doing that on their free time). So you would need to downgrade the ORM to 2.x for now. As Symfony 7.0 supports the ORM 3.0, composer probably selected that version during your dependency resolution done without the bundle. |
I chose to skip @stof's bundle and gedmo's all together. When the packages are up to spec (mainly gedmo) I will upgrade. Patiently we wait. :D |
yup, patiently we wait. The only option for now is to downgrade to the latest 2.x.x version. |
You can help with testing, contributing or sponsor the maintainers, instead of just patiently waiting. |
@ReSpawN it says And regarding the support for doctrine/orm 3.0, as I said above, the maintainer is working on it (and it seems to be almost there based on the discussion in doctrine-extensions/DoctrineExtensions#2708). But he's doing that work on his free time, with nobody in the community helping that effort AFAICT. See the answer of @Chris53897 (btw, the maintainer to sponsor in priority for that topic is not me but the maintainer of the extensions) |
@stof It seems to work fine with doctrine/orm v2.28.1 atleast for me. |
@stof Since the is a PR compatible with ORM 3, can you add a beta version with that PR in composer.json? |
gedmo/doctrine-extensions 3.16.0 has been released, with support for doctrine/orm 3.0 |
The problem arises when attempting to install version 1.11.0 of the bundle or the latest version without specifying a version explicitly on Symfony v7.03 and PHP v8.3.2.
The error message indicates that the requirements cannot be resolved to an installable set of packages due to conflicts in dependencies.
The issue likely stems from the incompatibility between the version constraints specified by gedmo/doctrine-extensions and those required by doctrine/orm.
Can anyone take a look into this ?
The text was updated successfully, but these errors were encountered: