hi anybody successfully imported old 2.5-Objectmanager-ZClasses into the new Zope 2.6.0? with not-folderisch ones it's no problem, but it looks to me that the Folderisch Typs need the module Interface.iclass in it, and that's gone in 2.6. (a thread last week discussed that) until now it tried the following solutions: - edit the xml-export, remove the item with the bad module. but there are references to the removed item, and they don't like that. i tried to remove the references, but then the import fails because the datastructure of my XML-File ist now ...... Ralph had success with that. congratulations, i failed :-( - copy the iclass.py and supporting classes into the new instance well, that didn't succeed either. i guess that these old things don't play well with the new classes. - refactor the ZClasses into Python Products right, that i can do, but that will take time and probably break my old contents. an other ideas? somebody with an idea how to replace the references to Interface.iclass in the xml-export? gidon
i'm writing the answer to my own question to the list for the records: the Interface.iclass reference is in the meta_types section of the ZClasses. meta_types defines a list of dictionaries that discribe the allowed objects of the folderish ZClass. so you just have to delete the meta_types tuple. this is easy to accomplish with the Subobjects-Tab of the ZClass, submitting an empty list. Then export the ZClasses, import them in the new site and then recreate the meta_types again by hand. et voila, your old ZClasses-Zombies are back to live. But then you remember sombody told you to use Python Base Class for the ZClasses, don't you? ;-) take care gidon Gidon Friedman schrieb:
hi
anybody successfully imported old 2.5-Objectmanager-ZClasses into the new Zope 2.6.0? with not-folderisch ones it's no problem, but it looks to me that the Folderisch Typs need the module Interface.iclass in it, and that's gone in 2.6. (a thread last week discussed that)
until now it tried the following solutions:
- edit the xml-export, remove the item with the bad module. but there are references to the removed item, and they don't like that. i tried to remove the references, but then the import fails because the datastructure of my XML-File ist now ...... Ralph had success with that. congratulations, i failed :-(
- copy the iclass.py and supporting classes into the new instance well, that didn't succeed either. i guess that these old things don't play well with the new classes.
- refactor the ZClasses into Python Products right, that i can do, but that will take time and probably break my old contents.
an other ideas? somebody with an idea how to replace the references to Interface.iclass in the xml-export?
gidon
_______________________________________________ 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 )
Gidon Friedman wrote:
i'm writing the answer to my own question to the list for the records:
the Interface.iclass reference is in the meta_types section of the ZClasses. meta_types defines a list of dictionaries that discribe the allowed objects of the folderish ZClass. so you just have to delete the meta_types tuple. this is easy to accomplish with the Subobjects-Tab of the ZClass, submitting an empty list.
Then export the ZClasses, import them in the new site and then recreate the meta_types again by hand. et voila, your old ZClasses-Zombies are back to live.
But then you remember sombody told you to use Python Base Class for the ZClasses, don't you? ;-)
Many thanks. QSurvey was affected, and this procedure works, if anyone is still using the product. I was worried about maybe having to actually do the Python Product I have been threatening to do for so long. -- Jim Washington
participants (2)
-
Gidon Friedman -
Jim Washington