Tres Seaver, on 2007-07-31:
> That is by design.  Once an import step is grafted into the baseline, it
> is part of the site's configuration for ever.  Resetting the baseline
> profile (a drastic step) is the only way to wipe it out.

Which is unfortunate as it means that any Product that defines its own
import step (be it via import_steps.xml or e.g. in the case of CacheFu
cache.xml) needs to stay in the Products directory forever.  If you
remove it (even after uninstalling it and restarting Zope and removing
it from Control_Panel/Products) the step is still in the registry.  So
it will give an error when you explicitly run it or when you run all
available steps, like this:

2007-07-31 19:43:34 ERROR Zope.SiteErrorLog 
Traceback (innermost last):
  Module ZPublisher.Publish, line 115, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 41, in call_object
  Module Products.GenericSetup.tool, line 414, in manage_importSelectedSteps
  Module Products.GenericSetup.tool, line 235, in runImportStep
  Module Products.GenericSetup.tool, line 727, in _doRunImportStep
   - __traceback_info__: kantoorsetup_various
  Module Products.GenericSetup.registry, line 146, in getStep
  Module Products.GenericSetup.utils, line 103, in _resolveDottedName
   - __traceback_info__: Products.kantoorsetup.setuphandlers.importVarious
AttributeError: 'module' object has no attribute 'kantoorsetup'

I went in with a zopectl debug session a few weeks ago to remove such
a step manually from the registry.  That worked, but having a method
that you can call in an uninstall method that does this for you, would
be better.

Maurits van Rees | [NL]
            Work |
"Do not worry about your difficulties in computers,
 I can assure you mine are still greater."

Zope-CMF maillist  -

See for bug reports and feature requests

Reply via email to