在文件系统中移动类之后，“ Class XXX 不是一个有效的实体或映射的超类”

我在 Aib PlatformBundle Entity User.php 中有一个实体类

通过以下方法创建它的表单类没有任何问题

Php 应用程序/控制台原则: create: form AibPlatformBundle: User

现在我已经将名称空间更改为 Aib PlatformBundle Entity Identity User，但是当我尝试用前面提到的任务生成表单时 它说:

”Class Aib PlatformBundle 实体用户不是有效实体或映射 超级高级”

这是文件内容:

<?php
namespace Aib\PlatformBundle\Entity\Identity;


use Doctrine\ORM\Mapping as ORM;


/**
* Aib\PlatformBundle\Entity\Identity\User
*
* @ORM\Table()
* @ORM\Entity(repositoryClass="Aib\PlatformBundle\Entity\Identity
\UserRepository")
*/
class User
{
...

知道吗？

Symfony2.0.4

90413 次浏览
小开

Had this problem - don't forget the annotation * @ORM\Entity like below:

/**
* Powma\ServiceBundle\Entity\User
*
* @ORM\Entity
* @ORM\Table(name="users")
*/
小开

Do check your config.yml file, should be containing something like this:

# Doctrine Configuration
doctrine:
dbal:
driver:   %database_driver%
host:     %database_host%
port:     %database_port%
dbname:   %database_name%
user:     %database_user%
password: %database_password%
charset:  UTF8
types:
json: Sonata\Doctrine\Types\JsonType


orm:
auto_generate_proxy_classes: %kernel.debug%
# auto_mapping: true
entity_managers:
default:
mappings:
FOSUserBundle: ~
# ApplicationSonataUserBundle: ~
YourUserBundle: ~
SonataUserBundle: ~

Add your own bundle to the mappings list.

小开

In my case the problem was solved by changing my servers cache from eAccelerator to APC. Apparently eAccelerator strips all the comments from files which breaks your annotations.

小开

I got rid of the same error message as in your case by using app/console_dev instead of just app/console

小开

Had this problem yesterday and found this thread. I created the entity with the mapping in a new bundle (e.g. MyFooBundle/Entity/User.php), did all the configuration according to the docs but got the same error from above when trying to load the app.

In the end I realized that I wasn't loading MyFooBundle in AppKernel:

new My\FooBundle\MyFooBundle()

A great way to debug this is to run this command:

app/console doctrine:mapping:info
小开

Very high possibility that you have PHP 5.3.16 (Symfony 2.x will not work with it). Anyway you should load check page on http://you.site.name/config.php If you had project not worked on hosting server, next lines must be removed in "config.php":

if (!in_array(@$_SERVER['REMOTE_ADDR'], array(
'127.0.0.1',
'::1',
))) {
header('HTTP/1.0 403 Forbidden');
exit('This script is only accessible from localhost.');
}

Goodluck!

小开

I resolved the same exception by deleting a conflicting autogenerated orm.php file in the bundle's Resources/config/doctrine folder; according to the documentation: "A bundle can accept only one metadata definition format. For example, it's not possible to mix YAML metadata definitions with annotated PHP entity class definitions."

小开

big thx to Mark Fu and mogoman

I knew it had to be somewhere in the config.yml... and being able to test it against the

app/console doctrine:mapping:info

really helped!

In fact, this command just simply stops at an error... no feedback, but when everything is fine you should be able to see all your entities listed.

小开

I solved this by passing false as the second parameter to Doctrine\ORM\Configuration::newDefaultAnnotationDriver.

It took me a while of digging through Google and source code.

My case was sort of special since I was using a mapping pointing to another directory unrelated to the Symfony installation as I also had to use legacy code.

I had refactored legacy entities and they stopped working. They used to use @Annotation instead of @ORM\Annotation, so after refactoring it simply failed to read the metadata. By not using a simple annotation reader, everything seems to be okayish.

小开

I resolved this issue by setting $useSimpleAnnotationReader=false when creating the MetaDataConfiguration.

小开

In my case, I was too zealous during a refactor and had deleted a doctrine yml file!

小开

In my case on my mac I was using src/MainBundle/Resource/Config/Doctrine, of course it worked on Mac but it didn't work on production Ubuntu server. Once renamed Config to config and Doctrine to doctrine, the mapping files were found and it started working.

小开
  1. Entity must have proper Entity and Table annotations (order may matter so try both)
  2. If there is custom repository it MUST be accessed via Entity class itself ($entityManager->getRepository('your ENTITY class name')), as calling it via Repository class name will trick Doctrine into thinking Repo class must be an entity itself. Silly, but Doctrine does not make hard distinction.
小开

My mistake was I was doing

$em->getRepository(EntityRepository::class)

instead of

$em->getRepository(Entity::class)
小开

In my case after making make:entity i tried the following command

php bin/console doctrine:mapping:import "App\Entity" annotation --path=src/Entity which generates the entity from the database However, this Command don t provide the getters and setters that will cause you unknown method error (getId for example) if you are using it inside a controller or you ll use it later So i decided to go back to the generated entity from the

php bin/console make:entity

so i can bring back the missing methods but unfortunately this caused me the error class is not a valid entity or mapped superclass. next to prevent this error i haven 't patience to read this documentation

[1]: https://www.doctrine-project.org/projects/doctrine-orm/en/2.11/tutorials/override-field-association-mappings-in-subclasses.html#override-field-association-mappings-in-subclasses especially i m using attributes in the place of annotation, therefore i brought back the generated entity and just adding the following command which generates getters and setters $ php bin/console make:entity --regenerate App saved my life ,though this solved my problem but i didn t figure out why in the first case it caused me the error of this topic


提交答案