From: Petri S. <pet...@ik...> - 2004-08-05 14:08:45
|
Hello, and thanks to the developers of Calendaring for a nice zope component. However, I was a bit surprised to find out Calendaring breaks the existing Event instances by "hijacking" the Event type. This leads to Site error whenever trying to view those old instances, with "AttributeError" as Error Type and "Schema" as Error Value. I took a look at the Calendaring Event source, but could not understand what necessitates the rewrite and the type hijack - it seems just a basic Event to me, apart from being AT-based, having some commonly used event information fields renamed, maybe one or two fields added??? Is this just part of the common trend of all content types becoming AT-based, or is there something significant I missed? Considering Event is being rewritten in ATContentTypes as well, would it make sense to migrate Calendaring to use ATEvent? We could then rely on ATContentTypes migration to migrate the existing CMFCalendar - based Events. I don't have solid information but I presume ATCT will be able to migrate all CMFCalendar Events to ATEvents. Thoughts? Thanks, Petri |