Missing userManager property (when updating user) about sonatauserbundle HOT 9 CLOSED

This is not an issue with the SonataAdminBundle. You need to define an userManager property and inject the related service into the Admin.

from sonatauserbundle.

Ok, I see. Thanks for your reply!

from sonatauserbundle.

Sorry to bump this up after 2 years, but i had the same issue today.

Since the $userManager property is used in the code of Sonata\UserBundle\Admin\Model\UserAdmin (there is a getter and a setter for this property), the property itself should be declared too, as pointed by mattsches:

protected $userManager;

Then, the question is: should we force the user to configure the service injection (http://sonata-project.org/bundles/admin/master/doc/reference/saving_hooks.html) like this:

<service id="fos.user.admin.user" class="%fos.user.admin.user.class%">
    <tag name="sonata.admin" manager_type="orm" group="fos_user" />
    <argument />
    <argument>%fos.user.admin.user.entity%</argument>
    <argument />

    <call method="setUserManager">
        <argument type='service' id='fos_user.user_manager' />
    </call>
</service>

...or should the UserAdmin class choose the fos_user.user_manager by default in the getter with mattsches' code ?

I think mattsches solution is much simpler.

from sonatauserbundle.

Ping

from sonatauserbundle.

@rande ^

from sonatauserbundle.

@Bladrak I actually sent the ping from @DerekRoth account ;)

from sonatauserbundle.

fixed

from sonatauserbundle.

@rande I ran into this bug today, and I'm using the ORM for managing users, while using the ODM to manage everything else. If you can point out which piece of code is in charge of this, I could have a look at it. I worked around my problem by injecting the manager.

from sonatauserbundle.

👍

from sonatauserbundle.