On Mon, 2004-05-17 at 13:06, Steve Jibson wrote: > I'm sure 'accountType' should have been in the session. Immediately > after a user logs in we populate his session with a bunch of stuff > (including accountType).
What happens when the session expires and he's still logged in? > What I don't want to do is hide problems with > session/tempstorage by using "get" and a default. In this particular > case, there is no good default and having the application assume an > incorrect accountType will cause me all kids of trouble. I still suspect this is an application error. > Also of note: > > 1 - After having the system run for 45 minutes, I had 8 similar errors. > Some were on different web pages and some had different "keys" that > were causing the error. > 2 - I have also traced through Z2.log and followed the same path through > the web site that produced one of the errors and I did not get an error. > 3 - Since changing this server to use FileStorage (1hr 39min ago), there > has not been a single error. > > Is there anything I can do to help here? A small reproducible test case would help if you still believe this error is not in your own application. - C _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
