[FLOW3-general] Problems updating the current user
Karsten Dambekalns
karsten at typo3.org
Mon Jan 23 10:32:16 CET 2012
Hi Zach.
On 19.01.12 21:56, Zach Davis wrote:
> 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.
That is to be expected. Everything returned from Doctrine will end up
being such a proxy. Which is not a problem, because that proxy
technically *is* an Account instance.
> accessible from the repository. Is there some way to force the
> persistence layer to return a fresh instance of an object from storage?
To me, a fresh instance would be something not yet persisted. What is a
fresh instance to you?
> 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
That could be, but is then more caused by session stuff than
persistence. If someone can whip up some code to reproduce this, I'll
gladly have a look.
Regards,
Karsten
More information about the FLOW3-general
mailing list