22 Mar
2004
22 Mar
'04
4:16 p.m.
Kevin Carlson wrote:
I removed all of the code in the particular page that used sessions and avoided any pages in the site that would create a session variable by traversing directly to the page in question.
I'd only believe it if you hack or Zope so the sessioning machinery raises an error whenenver something tries to write to the temp storage...
about one other item that may cause this. I am using a SiteAccessRule that is checking the domain name in the URL and calling setupSkin. Could that be causing this strange behavior?
setupSkin or something in that area may well be writing to the session :-S Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk