Hash: SHA1

Wichert Akkerman wrote:
> We are seeing a common GenericSetup related bugreport for Plone 3:
> people migrating to Plone 3 correctly remove products that are not
> yet supported on Plone 3. However those products may have a registered
> GS import or export step which is not removed. The result is that GS
> tries to run import/export code from a product which no longer exists
> and aborts with an ImportError. Since the only way to remove the
> step registration is by manually tweaking internal data structure of
> the setup tool this is somewhat painful.
> To fix this I want to do two things:
> * on GS trunk I want to implement zcml-based import and export step
>   registration (I have a partial implementation but need to finish
>   that)

+1.  In fact, I thought I had done that already (I see that was only
profile registration, and not step registration).

> * on the maintenance branch add a try/except to catch import errors and
>   either ignore those or remove the step if they occur.

+1 for logging / ignoring them (for extra bonus points, indicate somehow
in the UI of the import tab that the step is known to be borked).  My
rationale is that the product supplying the step might be temporarily
broken.  Perhaps the UI which indicates the broken step could allow the
user to remove that step manually?

BTW, I'm assuming that this information is relevant to this issue:


- --
Tres Seaver          +1 540-429-0999          [EMAIL PROTECTED]
Palladion Software   "Excellence by Design"    http://palladion.com
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


Zope-CMF maillist  -  Zope-CMF@lists.zope.org

See http://collector.zope.org/CMF for bug reports and feature requests

Reply via email to