Previously Tres Seaver wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> 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?
It could, but I'ld rather spend more time on doing zcml-based
registration than doing a full UI which will no longer be needed once we
switch to the zcml-approach.
> BTW, I'm assuming that this information is relevant to this issue:
Indeed it is.
Wichert Akkerman <[EMAIL PROTECTED]> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests