[FLOW3-general] Problems updating the current user

[Zachary Davis]

For the record, our problem with updating the current user was fixed by 
applying this change:

http://git.typo3.org/FLOW3/Packages/TYPO3.FLOW3.git?a=commit;h=d7af18a

Zach

Zach Davis wrote:
> We're working on a FLOW3 app for a client, and we've run into a little
> problem. So far, we've more or less built out the application backend,
> which is mostly composed of basic CRUD operations on Account and Party
> objects as well as authentication. The problem is that authenticated
> users are unable to update their accounts (eg, a password change). On
> doing so, FLOW3 always triggers an error.
>
> The problem seems to be that by the time the execution gets down to
> \TYPO3\FLOW3\Persistence\Doctrine\PersistenceManager, the account object
> is of the class
> "TYPO3\FLOW3\Persistence\Doctrine\Proxies\TYPO3FLOW3SecurityAccountProxy" instead
> of what we'd expect (\TYPO3\FLOW3\Security\Account), and this is
> throwing off the persistence manager. We've tried fetching a fresh
> instance of the object from the repository, but it only returns the same
> proxy object. We ran into a similar problem elsewhere, in which an
> object was being passed to an update method and we wanted to see the
> original object for comparison purposes, only to find that it was not
> accessible from the repository. Is there some way to force the
> persistence layer to return a fresh instance of an object from storage?
>
> This is the only issue we haven't been able to work around yet, and I'm
> happy to debug it further, but I'm kind of at a loss about where to
> begin. Does anyone have any insight or advice on this? Incidentally, I
> think our problem is closely related to (if not the same as) this
> problem: http://forge.typo3.org/issues/32873
>
> best,
> Zach