currently, in the TypesTool.manage_addTypeInformation method in CMF 1.6, if a typeinfo_name argument is passed in and the corresponding fti is not found in the results of listDefaultTypeInformation, an error is raised. in CMF 2.0, this argument is ignored completely.

in 1.6, some types will be listed in the listDefaultTypeInformation while others will not, depending on whether those types were defined using a GenericSetup profile or if it was done old-style.

would anyone foresee a problem w/ changing the behaviour of this such that an error isn't raised when the typeinfo_name isn't found?


Zope-CMF maillist  -

See for bug reports and feature requests

Reply via email to