Same here - same as 2.2.0b1 - at least my event.log now shows an error message although the time/date stamp is STILL wrong 0-: ------ 2000-08-26T06:03:20 INFO(0) ZServer Monitor Server (V1.8.4.1) started on port 8099 ------ 2000-08-26T06:03:27 ERROR(200) ZODB Couldn't load state for '\000\000\000\000\000\000\016\204' Traceback (innermost last): File /usr/local/zope/zope221/lib/python/ZODB/Connection.py, line 447, in setstate File /usr/local/zope/zope221/lib/python/ZODB/Connection.py, line 213, in _persistent_load (Info: File /usr/local/zope/zope221/lib/python/ZODB/Connection.py, line 154, in __getitem__ (Info: ('\000\000\000\000\000\000*\252', '(cExtensionClass\012ExtensionClass\012q\001(U\006ZDItemq\002(cZClasses.ZClass\012PersistentCl$ Could not load oid --- In zope@egroups.com, Andy Dustman <adustman@c...> wrote:

Sadly, 2.2.1 seems to break all my ZClass objects. The Products themselves look fine, but any object made with them comes up as broken. The Class ID (in the HTML source) looked like it had a * in front of it. I retrograded to 2.2.0 and the problems went away.

-- Dr Ross Lazarus Associate Professor and Sub-Dean for Information Technology Faculty of Medicine, Room 126A, A27, University of Sydney, Camperdown, NSW 2006, Australia Tel: (+61 2) 93514429 Mobile: +61414872482 Fax: (+61 2) 93516646 Email: rossl@med.usyd.edu.au