Ticket #12255 (confirmed Bug)
Plone 3 sites upgraded to Plone 4 contain troublesome ATBTreeFolder objects
Reported by: | dpc22 | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 4.x |
Component: | Upgrade/Migration | Version: | 4.1 |
Keywords: | ATBTreeFolder | Cc: | dpc22 |
Description
If I create a completely vanilla site using Plone 3.3.5, I end up with three ATBTreeFolder objects at the root of the site as follows:
<ATBTreeFolder at Members> <ATBTreeFolder at news> <ATBTreeFolder at events>
If this site is then upgraded to Plone 4, these are left as ATBTreeFolder (marked as deprecated, to be removed in Plone 5) rather than being replaced by ATFolder. All well and good, but ATBTreeFolder is no longer listed in portal_types, which means that the reordering icons no longer work when viewing @@folder_contents on the root of the site.
More detailed explanation:
ATBTreeFolder get filtered out by Products/Archetypes/OrderedBaseFolder.py
getCMFObjectsSubsetIds()
which means that
moveObjectsByDelta()
no longer works on ATBTreeFolder objects.
Change History
comment:1 Changed 4 years ago by kleist
- Keywords plone4 removed
- Status changed from new to confirmed
- Version set to 4.1
comment:3 Changed 3 years ago by mmax
Have there been any new developments on this?
We've recently migrated a large Plone site from 3.3 to 4.2.4 and a couple of ATBTreeFolders are still in the system. As described above, since ATBTreeFolders are no longer listed in portal_types we've run into some problems. E.g. the folders are not showing up in our navigation portlet etc...
I'm trying to figure out if the problem lies with our Plone site and code or if this can be traced to an issue with the migration process. I'd be thankful for any hints/pointers!