-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2 Mar 2007, at 13:36, yuppie wrote:

I can't seem to replicate this in a script. Changing the import context to "CMFDefault:default" does not seem to update the available import steps - however, using the ZMI and the "Properties" tab on the setup tool does. Both ways call the very same code (setImportContext) under the hood. Would anyone know why this does update the available steps from the ZMI, but not in the script? I've already tried a few things, like committing a transaction or calling _updateImportStepsRegistry manually, it just doesn't do anything...

Just a wild guess:

Does this now depend on looking up local utilities? Maybe you have to use setSite() explicitly?

No, the code path here is very short and does not involve any utility lookups. Matter of fact no code in GenericSetup.tool.SetupTool does any lookups. Adding setSite right before manipulating the portal diesn't help, either.

To be more precise about the symptoms, the change in import context is successful. It turns into CMFDefault:default. It just seems to retain the (shorter) list of import steps that CMF 1.6 offered, so the actual failure stems from the inability to locate a "componentregistry" import step in the profile. When I use the ZMI to change contexts instead the step registry is reloaded correctly.

jens



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFF6B/fRAx5nvEhZLIRAoplAJ9WhBH+HZrzgiHZgb1SHADGxlEOFgCgldHO
+6L8pIDon/TgNbE3YScLAhQ=
=eiDn
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

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

Reply via email to