Issue with "symfony/serializer" component on a clean Symfony installation #57294
Comments
|
see #57297 |
nicolas-grekas
added a commit
that referenced
this issue
Jun 3, 2024
…odified (xabbuh) This PR was merged into the 5.4 branch. Discussion ---------- [FrameworkBundle] not registered definitions must not be modified | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Issues | Fix #57294 | License | MIT Commits ------- c9b117c not registered definitions must not be modified
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Symfony version(s) affected
7.1, 7.0, 6.4
Description
I have encountered an issue with the "symfony/serializer" component on a clean Symfony installation. After installing the component via Composer, an error is generated when clearing the cache. The error message is "You have requested a non-existent service "serializer.normalizer.object"."
Interestingly, this error does not occur when the "symfony/security-bundle" package is installed.
I am currently working on WSL with Ubuntu and Docker php:8.2-fpm.
How to reproduce
I just installed Symfony using Composer and then the serializer component:
composer create-project symfony/skeleton:"7.1.*" my_project_directoryFollowed by:
composer require symfony/serializerPossible Solution
No response
Additional Context
The text was updated successfully, but these errors were encountered: