Ticket #4330 (closed Bug: fixed)
Inter-version ATCT migration fails to migrate types to CMFDynamicViewFTI
| Reported by: | optilude | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 2.1 |
| Component: | Templates/CSS | Keywords: | |
| Cc: |
Description
The ATCT setup code does the migrateFTIs() call that migrated standard CMF FTIs to CMFDynamciViewFTIs in Install.py. This means that if someone has an older version, they'll get SiteErrors when they migrate Plone, because their ATCT FTIs will remain the old version.
I'm unsure why the FTI migration can't be in Version Migration. Reinstalling ATCT should in theory fix, but mnemonic got:
Traceback (most recent call last):
File "/srv/conosur/conosur.0/intranet/Products/CMFQuickInstallerTool/QuickInstallerT ool.py", line 304, in installProduct res=install(portal, reinstall=reinstall)
File "/opt/zope/lib/python/Products/ExternalMethod/ExternalMethod.py", line 225, in call try: return f(*args, kw)
File "/srv/conosur/conosur.0/intranet/Products/ATContentTypes/Extensions/Install.py ", line 86, in install assert not tool.isCMFdisabled()
AssertionError
I'm unsure why this can't be part of ordinary Version Migration, though.

DynView FTI migration was added to the version migration