I have more details. As stated before, I erased all sessions. That didn't fix the problem.
I then did a session.forget() from within my main routine. That got past the pickle problem temporarily, but created a lot of other problems. After that, I removed the session.forget() operation from the main routine and things got back to normal. BUT only for my session. If I open another session in a different browser. I'm back to square one with that browser session. Same TypeError: can't pickle instancemethod objects. If I go through the session.forget() and then remove session.forget() procedure again, it starts to work in the new browser session. But it seems to be a one shot deal with each new session. I don't see that it's tenable to go through this every time someone first surfs to the site. On Monday, December 23, 2013 7:33:56 PM UTC+8, weheh wrote: > > Yes, I already did that. It didn't fix it. > > On Monday, December 23, 2013 6:38:57 PM UTC+8, Leonel Câmara wrote: >> >> Delete all session files. >> >> I have also found that in windows boxes running apache + mod_wsgi, you >> will constantly run into session errors if you're running more than one >> web2py instalation as WSGIDaemonProcess doesn't work on windows so you >> can't have a dedicated wsgi process for each of them. >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
