CMF 1.5's implementation of PortalFolder conflicts with CMFBTreeFolder.

CMF 1.4:
class PortalFolder(DynamicType, CMFCatalogAware, Folder)

CMF 1.5:
class PortalFolder(DynamicType, CMFCatalogAware, OrderedFolder)

class CMFBTreeFolder(BTreeFolder2Base, PortalFolder)

File "/opt/zope/instances/plone21z28cmf15/Products/ATContentTypes/content/", line 312, in processForm
File "/opt/zope/instances/plone21/Products/Archetypes/", line 231, in setId
File "/opt/zope/releases/Zope-2_8-branch/lib/python/OFS/", line 255, in manage_renameObject
    old_position = self.getObjectPosition(id)
File "/opt/zope/releases/Zope-2_8-branch/lib/python/OFS/", line 222, in getObjectPosition
    return ids.index(id)
AttributeError: 'OOBTreeItems' object has no attribute 'index'

As you can see CMFBTreeFolder doesn't work any more because PortalFolder is now subclassed from OrderedFolder. The changes to PortalFolder are *not* backward compatible. IMO they should be reverted and an OrderedPortalFolder class should be created for people how like to have ordered folders in CMF.


Zope-CMF maillist  -

See for bug reports and feature requests

Reply via email to