Brad Clements wrote:
Rather than doing the 2.5 Session upgrade work-around, I thought I'd be smart and delete the session_data_manager before restarting Zope (after changing start to use zope-2.5 pythonhome rather than Zope-2.5b3)
No I keep getting AttributeError on request.SESSION.getSessionData()
Seems the SESSION object doesn't have this method anymore.
However if I create a new session_data_manager lower in the tree, and point that at a new transient object container in /temp_folder, then it works again.
However if I restart zope, the transient object I created disappears.
Seems to be a problem in /temp_folder/session_data, except that even if I create a new transient object /temp_folder/mysession and point the root session_data_manager object at it, I still get attributeError on getSessionData(0
Anyone have any ideas? Or do I need to go to a backup?
I think this is coming from the before traversal hook of the session data manager. What you can do is create a session_data_manager in the old spot (the root) and then change its SESSION attribute name from the management screens to blank (null) -- that will get rid of the traversal hook -- then you can delete it and replace it with a dummy object again. -- Matt Kromer Zope Corporation http://www.zope.com/