This is because the database transaction which contained the session write is aborted on an error.. this is "normal" Zope behavior, and unfortunately there's no easy way around it. Why do you want to set a session variable on an error display, maybe there's a better way? ----- Original Message ----- From: "KevinL" <darius@obsidian.com.au> To: <zope@zope.org> Sent: Thursday, August 01, 2002 11:12 AM Subject: [Zope] session within standard_error_message
Can you set values inside the session object from within standard_error_message? I note that doing a request.RESPONSE.redirect requires a "lock=1" arg, I'm wondering if session variable setting suffers similar problems or not.
Reason I ask is, I have an app that tries to set session variables within the standard_error_message, and debug indicates the variables are there within that transaction, but gone on the next request from the browser.
KevinL
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )