We've developed a product that, for various reasons, needs to install an 
Image portal type upon install.
The code below, run as part of the Customization policy for a new 
Product-based site, works fine the first time I run it in a Zope instance.

When I run it a second time (in same Zope instance, but a different 
Plone site), it dies with the error shown below. Oddly, if I restart the 
Zope instance, I can run this code again once. So a "restart" somehow 
resets this problem.

What's the right way to add a custom portal type?

Code: (self is the Plone site being created)
[...]

Error on second attempt after Zope restart:
[...]

Uh, the reason it's puking is because you're trying to manually slam 
the factory type information into place without registering the type 
object using the more normal type registration process.

You want to register the factory type information in your __init__ 
scripts (see any Plone or CMF product, they'll all adjust FTI 
information).

Then you want to actually add the type to the types tool, ie, you want 
to invoke the factory based type information type install to the types 
tool.

If you peek at it, the ZMI invokes the manage_addTypeInformation method 
on the types_tool object; thats what you want to do too, e.g. in your 
code, invoke pt.manage_addTypeInformation(id='',typeinfo_name='PRODUCT: 
Type Name')

Usually you run that kind of install code in your Extensions/install.py 
file's install method.


On Aug 11, 2005, at 2:01 PM, Christoph Berendes wrote:
[...][...][...][...][...]

On 8/11/05 2:09 PM, Matthew T.Kromer wrote:
[...]


Thanks.

Checking
    if id not in typesTool.objectIds():

seems to have done the trick. I infer that adding the custom type the 
first time both adds it to Plone site #1, and to the portal_types tool, 
which then automagically adds it to the second site. Interesting.

Well, keep in mind there's the Product information, and then there's  
types tool information.  Product information is global to Zope; its  
handled at the module level and isn't persistent.  Types tool  
information is local to a Plone site, and *is* persistent.  Product  
registration happens only once, at Zope startup.  types_tool type  
registration can happen any time.


On Aug 11, 2005, at 2:53 PM, Christoph Berendes wrote:
[...][...][...]