Using a wildcard-destination in the zcml of an upgradeStep breaks setup_upgrades.zpt.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zope CMF buildout |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
If you use an upgrade-step like this
{{{
<genericsetup
title=
description
source="1"
destination="*"
handler=
sortkey="1"
profile=
}}}
it will break the template "setup_
This is the traceback:
{{{
Time 2010/03/31 16:55:50.024 GMT+2
User Name (User Id) admin (admin)
Request URL http://
Exception Type TypeError
Exception Value sequence expected, NoneType found
Traceback (innermost last):
* Module ZPublisher.Publish, line 119, in publish
* Module ZPublisher.mapply, line 88, in mapply
* Module Products.
* Module ZPublisher.Publish, line 42, in call_object
* Module Shared.
* Module Shared.
* Module Products.
* Module Products.Gloworm, line 28, in pt_render
* Module zope.pagetempla
* Module zope.tal.
* Module zope.tal.
* Module zope.tal.
* Module zope.tal.
* Module zope.tal.
* Module zope.tal.
* Module zope.tal.
* Module zope.tal.
* Module zope.tal.
* Module Products.
* Module zope.tales.tales, line 696, in evaluate
URL: manage_upgrades
Line 32, Column 2
Expression: <PythonExpr test(same_
Names:
{'container': <SetupTool at /plone_
'context': <SetupTool at /plone_
'default': <object object at 0x7ffe07177200>,
'here': <SetupTool at /plone_
'loop': {},
'nothing': None,
'options': {'args': ()},
'repeat': <Products.
'request': <HTTPRequest, URL=http://
'root': <Application at >,
'template': <PageTemplateFile at /plone_
'user': <PropertiedUser 'admin'>}
* Module Products.
_
* Module PythonExpr, line 1, in <expression>
TypeError: sequence expected, NoneType found
}}}
This happens on plone 3.3.5 + GenericSetup 1.4.5
and on Plone4.0b1 + GenericSetup 1.6.0b1
Patch for the template in attachment.
Changed in zope-cmf: | |
status: | Fix Committed → Fix Released |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Wouter Vanden Hove wrote: launchpadlibrar ian.net/ 42788090/ patch.txt
> ** Patch added: "patch.txt"
> http://
status incomplete
Hmm, I can't reproduce the traceback. I'm not opposed to applying the
patch (it looks pretty reasonable to me) but I would like to be sure I
have really fixed the bug you report.
The attached tarball contains an almost empty product, with only the
minimum necessary to get an upgrade step registered. It includes
registering an (empty) profile, as well as an upgrade step for that
profile, lightly modified from the one you posted.
Here is what I tried:
- - I created a Zope 2.12 INSTANCE_HOME with GenericSetup installed
(I tried with both trunk and 1.4 branch)
- - I copied the 'testproduct' into the 'Products' folder of the instance.
- - I started the appserver.
- - In the ZMI root, I created a folder, 'test_lp553338'.
- - In the ZMI for that folder, I added a "Generic Setup Tool."
- - On the ZMI "profiles" tab for the tool, I selected the "Testproduct
Site" profile.
- - I visited the "Upgrades" tab for the tool, and could see the upgrade
step.
Can you try reproducing with my product?
Tres. ======= ======= ======= ======= ======= ======= ======= ======= ==== palladion. com enigmail. mozdev. org
- --
=======
Tres Seaver +1 540-429-0999 <email address hidden>
Palladion Software "Excellence by Design" http://
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAku 0tcAACgkQ+ gerLs4ltQ7JagCa ArNJAn6WziP8JCp mUtm1PjaQ 40F7u2F6QyZajYU Ef
vN0AoK5iDed0eL+
=c9lO
-----END PGP SIGNATURE-----