Property "roles" in "UserBundle\Entity\User" was already declared, but it must be declared only once

[oste]

During a recent update I started getting this error. If I revert back to "friendsofsymfony/user-bundle": "dev-master#2c3b05b52c96b91255afc6d0d03dd97b03d17c4d" things work as before.

Here is a quick outline of what I am doing.

I have my UserClass that looks like this

<?php
namespace UserBundle\Entity;

use FOS\UserBundle\Model\User as BaseUser;
use Doctrine\Common\Collections\ArrayCollection;
use Doctrine\Common\Collections\Collection;
use Doctrine\ORM\Mapping as ORM;

use UserBundle\Entity\Role;

/**
 * @ORM\Table(name="users")
 * @ORM\Entity()
 */
class User extends BaseUser
{

    /**
    * @ORM\ManyToMany(targetEntity="UserBundle\Entity\Role")
    * @ORM\JoinTable(name="users_roles_rel")
    */
    protected $roles;

    public function __construct()
    {
        parent::__construct();
        $this->roles = new ArrayCollection();
    }
}

So I am re-declaring the roles property, but I am extending it to be a many to many relationship. Should I be doing this in a new way to adhere to the recent changes to the bundle?

[romeugodoi]

I have the same problem.
I noticed that the model entities were changed, so what is the new implementation for this?

[sstok]

@dbu any idea?

[dbu]

is it still working at 8be0c33 but broken at 33271c9 ? then it would be related to the change i did. what definitely should work is using an xml mapping instead of the annoatation, as then you do not need to re-declare the property on the class. though i think i did that before as well with doctrine, and it did work.

btw, if you go to before 33271c9 then you won't inherit any mapping at all and your user class will only have the role mapped in the db. then you would need to extend the user entity from the Entity folder.

[oste]

I ended up going with the alternative approach @dbu mentions here #1081 (comment)

I think this is a good approach, especially when making heavy changes to the user model. This approach does break the fos.user_provider service but that can be easily replaced, with your own or extended version.

I will go ahead and close this ticket, thanks.

[dbu]

glad you found a solution.

though i am still not sure if this was not some bug in doctrine orm you
encountered. if somebody can provide an isolated failing test in the orm
about this, i can investigate that.