ok finally I made inroads with the help of several people thank you guys! and now I got the notices gone on real browser test however they are failing for testing forms apparently? I was told the form_login needs to be switched to http_basic as shown in here http://www.dobervich.com/2011/03/28/symfony2-blog-application-tutorial-part-v-2-testing-secure-pages/
so basically now I am trying to get the settings right for the FOS UserBundle to test on http_basic mode so if you are a FOS UserBundle developer please let me know about that info, I would greatly appreciate it. nonetheless i still continue to wonder why serialize and unserialize methods were needed, and what parameters are really required in terms of my design, I was told the needed to rebuild your object, however hmm, in what situation this rebuilding is happening for me to figure that out? Any clarifications are welcome, thanks! On Mon, Apr 18, 2011 at 2:08 PM, Luis Cordova <cordo...@gmail.com> wrote: > please somebody help me, > all my code is in https://github.com/cordoval/Memorize-Scripture-2 > I have tried several things, not even serializing the errors would go away > rather they will get worse > > can someone take a look at this please? appreciate it > >>>> Notice: serialize(): "sessionverses" returned as member variable from >>>> __sleep() but does not exist in >>>> /home/cordoval/sites-2/memorizescripture/vendor/symfony/src/Symfony/Compone >>>> nt/Security/Core/Authentication/Token/AbstractToken.php >>>> on line 136 > > check below > > On Mon, Apr 18, 2011 at 8:01 AM, Luis Cordova <cordo...@gmail.com> wrote: >> hi Fabien, all >> >> thanks for the suggestion, but this speaks about a class on the >> Security/Core/Authentication/Token/AbstractToken.php symfony code >> or on my class? and if my class i guess the one that has member that >> variable? >> >> I will try but was not really sure since there is AbstractToken.php I >> have no control on that... >> >> I feel like I am doing this to find where the error really is right? >> since it is going to serialize probably a stack trace as your post >> here suggest, but I am not using sf1.x but rather sf2. >> http://fabien.potencier.org/article/9/php-serialization-stack-traces-and-exceptions >> >> On Mon, Apr 18, 2011 at 1:46 AM, Fabien Potencier >> <fabien.potenc...@gmail.com> wrote: >>> >>> >>> On Apr 16, 4:46 am, Luis Cordova <cordo...@gmail.com> wrote: >>>> I am getting a notice: >>>> >>>> Notice: serialize(): "sessionverses" returned as member variable from >>>> __sleep() but does not exist in >>>> /home/cordoval/sites-2/memorizescripture/vendor/symfony/src/Symfony/Compone >>>> nt/Security/Core/Authentication/Token/AbstractToken.php >>>> on line 136 Notice: serialize(): "chapter" returned as member variable >>>> from __sleep() but does not exist in >>>> /home/cordoval/sites-2/memorizescripture/vendor/symfony/src/Symfony/Compone >>>> nt/Security/Core/Authentication/Token/AbstractToken.php >>>> on line 136 >>>> >>>> I found : >>>> To summerize: in a given class hierarchy in which parent classes >>>> contain private member variables, those variables are serialized when >>>> __sleep() is not defined. However, once __sleep() is defined, there is >>>> no way to make those private member variables serialized as well. From >>>> that point on, serialization is performed from the visibility scope of >>>> the subclass. It is particularly important to note this little quirk >>>> when designing base classes that their derivables may be serialized, >>>> or when subclassing an external library class. >>>> >>>> However my question is how do i avoid this, since this is in twig that >>>> I am doing lazy loading with user then user.sessions, then >>>> session.sessionverses, then sessionverse.verse.Chapter etc >>>> >>>> Can someone please hint? thanks >>> >>> Have you tried to use the Serialize interface instead. In the >>> serialize()/unserialize() methods, you can do pretty much what you >>> need >>> to serialize/unserialize your objects. >>> >>> Fabien >>> >>> >>>> Luis >>> >>> -- >>> 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 >>> >> > -- 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
