If you want to upgrade from Zope 2.7 to Zope 2.8 in this transition, we advice you to stay with Zope 2.7 until you have completed the Plone part of the migration, then upgrade to 2.8. Zope 2.8 includes major changes and improvements, and trying to upgrade both Zope and Plone in the same operation is not recommended. Both Zope 2.7 and Zope 2.8 are supported platforms for Plone 2.1.x, though. As a rule of thumb, always start at the top with upgrades, and work your way down — upgrade Products, then Plone, then Zope, then Python.
On 1/6/06, R G <[EMAIL PROTECTED]> wrote:
Hi all.
I'm posting this error once again since I'm yet to get it solved!
I need to upgrade a plone 2.0.5 site to 2.1.1.
The source system specs are:
The destination system specs are:
Either exporting (zexp method) or copying the Data.fs results in the same error.
My steps were:
- Installed zope 2.8.4-final, and created the instance
- Unpacked plone 2.1.1 to the instance products dir
- Added the products needed by the site (but did not replace any of the products from 2.1.1)
- Imported the site (wich was ok)
Now, after reading several how-to's regarding migration 2.0 -> 2.1, all of them insisted on some step envolving portal_atct (prior to running the portal_migration "thing"). I do not have any portal_atct before I run the migration, so I cannot do anything besides the migration!
Checking the products (several are broken, of course, before the migration) I see that ATContentTypes is NOT broken, but it is a different version (actual 1.0.1, source 0.2.0-rc4).
At this point I tried to run the migration, wich was ok, no errors reported. I also tried to run the migration with ATCT 0.2.0, but I get this.
(Starting the migration from version: 2.0.5
- Attempting to upgrade from: 2.0.5
- Upgrade aborted
- Error type: exceptions.AttributeError
- Error value: portal_atct
- File "/home/rg/zope_2.8_instance_alinex/Products/CMFPlone/MigrationTool.py", line 265, in upgrade newv, msgs = self._upgrade(newv)
- File "/home/rg/zope_2.8_instance_alinex/Products/CMFPlone/MigrationTool.py", line 362, in _upgrade res = function(self.aq_parent)
- File "/home/rg/zope_2.8_instance_alinex/Products/CMFPlone/migrations/v2_1/alphas.py", line 67, in two05_alpha1 migrateToATCT10(portal, out)
- File "/home/rg/zope_2.8_instance_alinex/Products/CMFPlone/migrations/v2_1/alphas.py", line 295, in migrateToATCT10 tool = portal.portal_atct
- End of upgrade path, migration has finished
- The upgrade path did NOT reach current version
- Migration has failed )
After the portal_migration, I do indeed have portal_atct. I can then recatalog cmf and at types (on the recatalog tab) and i can run fix (on the type_migration tab). Although, I cannot run migrate (in the same tab), cause I get this:
Couldn't migrate src_portal_type due to missing FTITrying to view the portal results in the ever so enjoyable "recursion error".
Couldn't migrate src_portal_type due to missing FTI
Couldn't migrate src_portal_type due to missing FTI
Couldn't migrate src_portal_type due to missing FT
I
.....
Any pointers, you guys?
_______________________________________________
Setup mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/setup
--
Nikos Papagrigoriou
* personal email: [EMAIL PROTECTED]
* personal website: http://www.papagrigoriou.gr
_______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
