[Setup] Re: portal_atct CMF Topic missing FTI error migrating from Plone 2.0.5 to Plone 2.1.2

Jon.Lim at hawaii.gov Jon.Lim at hawaii.gov
Mon May 8 18:40:58 UTC 2006


Hi Nick,

Ah, apologies for not replying to your email on the plone-user list. Thank 
you for the reply to my question....  My inbox got filled when I signed up 
for the plone-users mailing list so I unsubscribed to keep my inbox from 
filling up.  I did see the email you sent on that other list, however. Is 
the plone-setup list the appropriate place for this question?

Anyway, your  email was a great to providing a systematic approach to the 
migration.  From there, I had to do more mailing list searching to find 
the necessary details. 

As you have suggested, I started by migrating the 3rd party products first 
before migrating Plone to 2.1.2.   I believe I have successfully upgraded 
the Plone plugins listed in portal_quickinstaller.   I have also tried to 
delete out some bad content such as CMFPhoto and CMFPhotoAlbum objects in 
my Plone instance.  I deleted and added a new portal_catalog but am stuck 
with rebuilding the content using portal_atct.   This is currently where 
I'm stuck.

PORTAL_ATCT ERROR:

Running a types migration in portal_atct shows the following error:
--> Migrating CMF Document to Document with CatalogWalker
--> Migrating CMF Event to Event with CatalogWalker
--> Migrating CMF Favorite to Favorite with CatalogWalker
--> Migrating CMF File to File with CatalogWalker
--> Migrating CMF Image to Image with CatalogWalker
--> Migrating CMF Link to Link with CatalogWalker
--> Migrating CMF News Item to News Item with CatalogWalker
--> Migrating CMF Folder to Folder with CatalogWalkerWithLevel
Couldn't migrate src_portal_type due to missing FTI
--> Migrating CMF Topic to Topic with CatalogWalker

The event.log file does not show anything when doing the portal_atct type 
migration.   :(


PORTAL_MIGRATION FAILURE:

It was a bit useful when failing with the portal_migration tool though. 

ZMI Error:
Starting the migration from version: 2.0.5 
Attempting to upgrade from: 2.0.5 
Upgrade aborted 
Error type: exceptions.AttributeError 
Error value: getAvailableLayouts 
File 
"/usr/local/zope/instances/01_zope278/Products/CMFPlone/MigrationTool.py", 
line 274, in upgrade newv, msgs = self._upgrade(newv) 
File 
"/usr/local/zope/instances/01_zope278/Products/CMFPlone/MigrationTool.py", 
line 371, in _upgrade res = function(self.aq_parent) 
File 
"/usr/local/zope/instances/01_zope278/Products/CMFPlone/migrations/v2_1/alphas.py", 
line 29, in two05_alpha1 convertPloneFTIToCMFDynamicViewFTI(portal, out) 
File 
"/usr/local/zope/instances/01_zope278/Products/CMFPlone/migrations/v2_1/alphas.py", 
line 1276, in convertPloneFTIToCMFDynamicViewFTI if 'folder_listing' not 
in portal.getAvailableLayouts(): 
End of upgrade path, migration has finished 
The upgrade path did NOT reach current version 
Migration has failed 

Event.Log error:

------
2006-05-08T08:35:31 INFO(0) Plone
Starting the migration from version: 2.0.5
------
2006-05-08T08:35:31 INFO(0) Plone
Attempting to upgrade from: 2.0.5
------
2006-05-08T08:35:31 ERROR(200) Plone
Upgrade aborted
------
2006-05-08T08:35:31 ERROR(200) Plone
Error type: exceptions.AttributeError
------
2006-05-08T08:35:31 ERROR(200) Plone
Error value: getAvailableLayouts
------
2006-05-08T08:35:31 ERROR(200) Plone
  File 
"/usr/local/zope/instances/01_zope278/Products/CMFPlone/MigrationTool.py", 
line 274, in upgrade
    newv, msgs = self._upgrade(newv)

------
2006-05-08T08:35:31 ERROR(200) Plone
  File 
"/usr/local/zope/instances/01_zope278/Products/CMFPlone/MigrationTool.py", 
line 371, in _upgrade
    res = function(self.aq_parent)

------
2006-05-08T08:35:31 ERROR(200) Plone
  File 
"/usr/local/zope/instances/01_zope278/Products/CMFPlone/migrations/v2_1/alphas.py", 
line 29, in two05_alpha1
    convertPloneFTIToCMFDynamicViewFTI(portal, out)

------
2006-05-08T08:35:31 ERROR(200) Plone
  File 
"/usr/local/zope/instances/01_zope278/Products/CMFPlone/migrations/v2_1/alphas.py", 
line 1276, in convertPloneFTIToCMFDynamicViewFTI
    if 'folder_listing' not in portal.getAvailableLayouts():

------
2006-05-08T08:35:31 INFO(0) Plone
End of upgrade path, migration has finished
------
2006-05-08T08:35:31 PROBLEM(100) Plone
The upgrade path did NOT reach current version
------
2006-05-08T08:35:31 PROBLEM(100) Plone
Migration has failed


Does any of this make sense to you?  I am currently not sure where to go 
from here.

Thanks,
Jon
-------------------------------------
Jonagustine Lim
eGovernment Team Specialist
State of Hawaii, DAGS/ICSD
jon dot lim at hawaii dot gov
808-586-1920 x325



Nick Davis <nd51 at le.ac.uk> 
Sent by: setup-bounces at lists.plone.org
05/07/2006 11:04 PM

To
setup at lists.plone.org
cc

Subject
[Setup] Re: portal_atct CMF Topic missing FTI error migrating from Plone 
2.0.5 to Plone 2.1.2






Jon.Lim at hawaii.gov wrote:
> 
> Hello,
> 
> I am currently trying to migrate my Plone 2.0.5 instance to Plone 2.1.2 
> but am having some trouble with portal_atct migration when I do a Type 
> Migration.  The error I am getting is below:
> 
> Couldn't migrate src_portal_type due to missing FTI
> --> Migrating CMF Topic to Topic with CatalogWalker
> 
I replied to a related question of yours on the plone users list.
A copy is here:

http://www.nabble.com/2.0.5-to-2.1.2-migration-error%3A-exceptions.AttributeError-getAvailableLayouts-t1546813.html



Was that any help? I made one typo - meant to say look in the event.log, 
not the error.log.

The things I suggested would apply to solving this problem too.

It would be nice sometimes to hear back from people.

I have answered a number of posts regarding migration and cannot know if 
my advice is any use / should be rephrased, unless the recipient 
actually tells me. ;-)

Nick

_______________________________________________
Setup mailing list
Setup at lists.plone.org
http://lists.plone.org/mailman/listinfo/setup

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plone.org/pipermail/plone-setup/attachments/20060508/7d741d70/attachment-0002.html>


More information about the Setup mailing list