Le 23/06/2011 10:22, François CONSTANT a écrit :
Hi,
the current user can't be serialized apparently.
Changing private $usuario; to protected $usuario should solve that
issue. It must be done on related entities as well.
On Jun 23, 5:45 pm, Michel Salib<michelsa...@gmail.com> wrote:
Most of the time this error appear because of a bad initialization of your
object.
It looks like you do not have any constructor, so you don't seem to
initialize any collection which you should do if you have some. What is your
orm mapping ?
Proxies are not serializables when you use private properties, and can
eventually cause issues in other cases. The good way to go is to
implement the Serializable interface to control the way they are serialized.
--
Christophe | Stof
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
