Command execution error "Cannot find the entity manager"

[jogoool]

after installing the bundle the make:reset-password command could not generate all the files, I got error Cannot find the entity manager for class "App\Entity\ResetPasswordRequest"

P	V
symfony	5.4
doctrine	2.10
PHP	8.1.11

created: src/Controller/ResetPasswordController.php
created: src/Entity/ResetPasswordRequest.php

In DoctrineHelper.php line 91:

Cannot find the entity manager for class "App\Entity\ResetPasswordRequest"

[fundo-moretti]

I had the very same problem and I think it's related to Doctrine. Annotations instead of attributes were used in entities.

I've updated project's code using Rector (see Upgrading & What's New in Symfony 6!), and now it is working as expected.

[jrushlow]

Howdy @jogoool, @fundo-moretti is correct - this is caused by the mapping type (annotation/attribute) that your app is using.

It sounds like you're using attributes for your entities but the ResetPasswordRequest entity does not have the correct attributes. Can you provide your ResetPasswordRequest object here and we can help you sort that out.

[HrjSnz]

Hello, i was just dealing with this today. And somewhere on git in issues I found that there is a problem that should be fixed. As a fix install version 1.x

[spetters]

Do you use annotations or attributes? For me with attributes, the following works:

<?php
declare(strict_types = 1);

namespace App\Entity;

use App\Repository\ResetPasswordRequestRepository;
use Doctrine\ORM\Mapping as ORM;
use SymfonyCasts\Bundle\ResetPassword\Model\ResetPasswordRequestInterface;
use SymfonyCasts\Bundle\ResetPassword\Model\ResetPasswordRequestTrait;

#[ORM\Entity(repositoryClass: ResetPasswordRequestRepository::class)]
class ResetPasswordRequest implements ResetPasswordRequestInterface {

	use ResetPasswordRequestTrait;

	#[ORM\Id]
	#[ORM\GeneratedValue]
	#[ORM\Column(type: 'integer')]
	private int $id;

	#[ORM\ManyToOne(targetEntity: User::class)]
	#[ORM\JoinColumn(nullable: false)]
	private User $user;

...

[jeremyrncp]

I have the same error :

[fundo-moretti]

Well, if you have the same error, you could probably fix it by converting your entity mapping type from annotation to attribute (see above).

[jeremyrncp]

What is the good way for that ?

[fundo-moretti]

As I said, see above. I mean, read chapters 03 Automating Upgrades with Rector and 04 Post-Rector Cleanups & Tweaks of this Symfonycast Upgrading & What's New in Symfony 6!.
This will help you to automate conversion of annotations to attributes.

Here's the rector.php I used (with PHP 8.0 and Symfony 5.4):

<?php

declare(strict_types=1);

use Rector\Config\RectorConfig;
use Rector\Doctrine\Set\DoctrineSetList;
use Rector\Set\ValueObject\LevelSetList;
use Rector\Symfony\Set\SensiolabsSetList;
use Rector\Symfony\Set\SymfonyLevelSetList;
use Rector\Symfony\Set\SymfonySetList;

return static function (RectorConfig $rectorConfig): void {
    $rectorConfig->symfonyContainerXml(__DIR__ . '/var/cache/dev/App_KernelDevDebugContainer.xml');

    $rectorConfig->importNames();
    $rectorConfig->importShortClasses(false);

    $rectorConfig->sets([
        LevelSetList::UP_TO_PHP_80,
        SymfonyLevelSetList::UP_TO_SYMFONY_54,
        SymfonySetList::SYMFONY_CODE_QUALITY,
        SymfonySetList::ANNOTATIONS_TO_ATTRIBUTES,
        DoctrineSetList::ANNOTATIONS_TO_ATTRIBUTES,
        DoctrineSetList::GEDMO_ANNOTATIONS_TO_ATTRIBUTES,
        SymfonySetList::SYMFONY_CONSTRUCTOR_INJECTION,
        SensiolabsSetList::FRAMEWORK_EXTRA_61,
    ]);
};

If you don't want to use Rector, manually change annotations /** @ORM\...*/ to attributes #[ORM\...] in your entity files.

[astronati]

The project totally uses attributes but I face the same issue.
Any suggestion?

[bocharsky-bw]

I see the latest version of MakerBundle has an improved error message: https://github.com/symfony/maker-bundle/blob/a3b7f14d349f8f44ed752d4dde2263f77510cc18/src/Doctrine/DoctrineHelper.php#L92

Cannot find the entity manager for class "%s". Ensure entity uses attribute mapping.

So it hints that you need to use PHP attributes. Not much else we can do here, because annotation support is dropped completely here.

@astronati Could you provide more context, please? All your entities use PHP attributes mapping instead of annotations? How about this config in config/packages/doctrine.yaml?

doctrine:
    orm:
        mappings:
            App:
                type: attribute

Do you have type set to attribute there? Anything specific about your project? A few entity managers, something else?

[astronati]

@bocharsky-bw Thanks for your message, and sorry for the late reply. Unfortunately, the project was abandoned, so I didn’t spend more time investigating it. If I end up working on something similar in the future, I’ll let you know in this thread.

[mr120]

I experienced these errors, not sure its the same issue but here is how i solved it.

The project namespace had been updated to something custom, but I hadn't updated the doctrine.yaml mapping to reflect this, once this was updated I no longer got warnings about attributes or entity managers not found

This:

mappings:
  App:
    type: attribute
    is_bundle: false
    dir: '%kernel.project_dir%/src/Entity'
    prefix: 'App\Entity'
    alias: App

Needed to be:

mappings:
  Custom:
    type: attribute
    is_bundle: false
    dir: '%kernel.project_dir%/src/Entity'
    prefix: 'Custom\Entity'
    alias: Custom