Skip KeyError due to a missing interaction workflow as a workaround. It is...

Skip KeyError due to a missing interaction workflow as a workaround. It is necessary to do a bit differently later, probably using an interactor rather than an interaction workflow.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39433 20353a03-c40f-0410-a6d1-a30d3c3de9de

product/ERP5Type/ERP5Type.py

@@ -439,7 +439,13 @@ class ERP5TypeInformation(XMLObject,
         if init_script and init_script.startswith('add'):
           base = init_script[3:]
           # and of course migrate the property
+          try:
             self.setTypeClass(base)
+          except KeyError:
+            # Unfortunately, the above setter may trigger an interaction,
+            # but the interaction workflow may not be present yet at the
+            # bootstrap time, thus simply ignore such an error for now.
+            pass
       return base
 
     security.declareProtected(Permissions.AccessContentsInformation,