1. Zuhause
  2. Frage und Antwort
  3. Upgrade fehlgeschlagen - Plone 4.3.7 zu Plone 5.0

Upgrade fehlgeschlagen - Plone 4.3.7 zu Plone 5.0

2015-10-09 6 views
7

Ich versuche, Plone 4.3.7 auf Plone 5.0 über das portal_migration-Tool zu aktualisieren, und den folgenden Fehler zu finden. Irgendwelche Gedanken? Dies ist eine einfache Site (keine Add-Ons), aber sie stammt aus Plone 2.x, also könnte es noch ein paar alte Fehler geben, die ich vergessen habe.Upgrade fehlgeschlagen - Plone 4.3.7 zu Plone 5.0

Ausgabe der UPGRADE-Tool:

Dry run selected. 
Starting the migration from version: 4311 
Ran upgrade step: Miscellaneous 
Role/permission map imported. 
Archetype tool imported. 
Step languagetool has an invalid import handler 
Step kupu-setup has an invalid import handler 
Ran upgrade step: Run to50alpha3 upgrade profile 
Ran upgrade step: Upgrade editing control panel settings 
Ran upgrade step: Upgrade maintenance control panel settings 
Ran upgrade step: Upgrade navigation control panel settings 
Ran upgrade step: Upgrade search control panel settings 
Ran upgrade step: Upgrade site control panel settings 
Role/permission map imported. 
Skins tool imported. 
Archetype tool imported. 
Step languagetool has an invalid import handler 
Step kupu-setup has an invalid import handler 
Ran upgrade step: Run to50beta1 upgrade profile 
Ran upgrade step: Upgrade markup control panel settings 
Ran upgrade step: Upgrade mail control panel settings 
Ran upgrade step: Upgrade security control panel settings 
Upgrade aborted. Error: 
Traceback (most recent call last): 
    File "/usr/local/Plone/buildout-cache/eggs/Products.CMFPlone-5.0-py2.7.egg/Products/CMFPlone/MigrationTool.py", line 257, in upgrade 
    step['step'].doStep(setup) 
    File "/usr/local/Plone/buildout-cache/eggs/Products.GenericSetup-1.8.0-py2.7.egg/Products/GenericSetup/upgrade.py", line 166, in doStep 
    self.handler(tool) 
    File "/usr/local/Plone/buildout-cache/eggs/plone.app.upgrade-1.3.18-py2.7.egg/plone/app/upgrade/v50/betas.py", line 63, in upgrade_portal_language 
    lang_settings.use_content_negotiation = portal_languages.use_content_negotiation 
AttributeError: use_content_negotiation 
Starting upgrade of core addons. 
Done upgrading core addons. 
End of upgrade path, migration has finished 
The upgrade path did NOT reach current version 
Migration has failed 
Dry run selected, transaction aborted

Wenn ich nur versuchen, die Website selbst zu sehen, habe ich eine leere Seite mit dieser Fehlermeldung finden Sie unter:

KeyError('Interface `Products.CMFPlone.interfaces.controlpanel.ILanguageSchema` 
defines a field `available_languages`, for which there is no record.',) 
(Also, the following error occurred while attempting to render the 
standard error message, please see the event log for full details: 
Interface `Products.CMFPlone.interfaces.controlpanel.ILanguageSchema` 
defines a field `available_languages`, for which there is no record.)

In der Debug-Modus-Konsole I Siehe wiederholte Fehlermeldungen wie folgt:

2015-10-09 13:52:28 INFO plone.app.upgrade Dry run selected. 
2015-10-09 13:52:28 INFO plone.app.upgrade Starting the migration from version: 4311 
2015-10-09 13:52:28 INFO plone.app.upgrade Ran upgrade step: Miscellaneous 
2015-10-09 13:52:28 INFO Products.GenericSetup.tool Importing profile profile-plone.app.upgrade.v50:to50alpha3 with dependency strategy upgrade. 
2015-10-09 13:52:28 INFO Products.GenericSetup.tool Applying main profile profile-plone.app.upgrade.v50:to50alpha3 
2015-10-09 13:52:29 INFO GenericSetup.rolemap Role/permission map imported. 
/usr/local/Plone/buildout-cache/eggs/Products.CMFCore-2.2.10-py2.7.egg/Products/CMFCore/DirectoryView.py:493: UserWarning: DirectoryView plone_deprecated refers to a non-existing path 'Products.CMFPlone:skins/plone_deprecated' 
    (self.id, reg_key), UserWarning) 
/usr/local/Plone/buildout-cache/eggs/Products.CMFCore-2.2.10-py2.7.egg/Products/CMFCore/DirectoryView.py:493: UserWarning: DirectoryView plone_styles refers to a non-existing path 'Products.CMFPlone:skins/plone_styles' 
    (self.id, reg_key), UserWarning) 
/usr/local/Plone/buildout-cache/eggs/Products.CMFCore-2.2.10-py2.7.egg/Products/CMFCore/DirectoryView.py:493: UserWarning: DirectoryView classic_ecmascript refers to a non-existing path 'plonetheme.classic:skins/classic_ecmascript' 
    (self.id, reg_key), UserWarning) 
2015-10-09 13:52:29 INFO GenericSetup.archetypetool Archetype tool imported. 
2015-10-09 13:52:29 ERROR GenericSetup Step languagetool has an invalid import handler 
2015-10-09 13:52:29 ERROR GenericSetup Step kupu-setup has an invalid import handler 
2015-10-09 13:52:29 INFO plone.app.upgrade Ran upgrade step: Run to50alpha3 upgrade profile 
2015-10-09 13:52:29 INFO plone.app.upgrade Ran upgrade step: Upgrade editing control panel settings 
2015-10-09 13:52:29 INFO plone.app.upgrade Ran upgrade step: Upgrade maintenance control panel settings 
2015-10-09 13:52:29 INFO plone.app.upgrade Ran upgrade step: Upgrade navigation control panel settings 
2015-10-09 13:52:29 INFO plone.app.upgrade Ran upgrade step: Upgrade search control panel settings 
2015-10-09 13:52:29 INFO plone.app.upgrade Ran upgrade step: Upgrade site control panel settings 
2015-10-09 13:52:29 INFO Products.GenericSetup.tool Importing profile profile-plone.app.upgrade.v50:to50beta1 with dependency strategy upgrade. 
2015-10-09 13:52:29 INFO Products.GenericSetup.tool Applying main profile profile-plone.app.upgrade.v50:to50beta1 
2015-10-09 13:52:29 INFO GenericSetup.rolemap Role/permission map imported. 
2015-10-09 13:52:29 INFO GenericSetup.skins Skins tool imported. 
2015-10-09 13:52:29 INFO GenericSetup.archetypetool Archetype tool imported. 
2015-10-09 13:52:29 ERROR GenericSetup Step languagetool has an invalid import handler 
2015-10-09 13:52:29 ERROR GenericSetup Step kupu-setup has an invalid import handler 
2015-10-09 13:52:29 INFO plone.app.upgrade Ran upgrade step: Run to50beta1 upgrade profile 
2015-10-09 13:52:29 ERROR PortalTransforms Cannot register transform html-to-captioned (ImportError), using BrokenTransform: Error 
No module named html2captioned 
2015-10-09 13:52:29 INFO plone.app.upgrade Ran upgrade step: Upgrade markup control panel settings 
2015-10-09 13:52:29 INFO plone.app.upgrade Ran upgrade step: Upgrade mail control panel settings 
2015-10-09 13:52:29 INFO plone.app.upgrade Ran upgrade step: Upgrade security control panel settings 
2015-10-09 13:52:29 ERROR plone.app.upgrade Upgrade aborted. Error: 
Traceback (most recent call last): 
    File "/usr/local/Plone/buildout-cache/eggs/Products.CMFPlone-5.0-py2.7.egg/Products/CMFPlone/MigrationTool.py", line 257, in upgrade 
    step['step'].doStep(setup) 
    File "/usr/local/Plone/buildout-cache/eggs/Products.GenericSetup-1.8.0-py2.7.egg/Products/GenericSetup/upgrade.py", line 166, in doStep 
    self.handler(tool) 
    File "/usr/local/Plone/buildout-cache/eggs/plone.app.upgrade-1.3.18-py2.7.egg/plone/app/upgrade/v50/betas.py", line 63, in upgrade_portal_language 
    lang_settings.use_content_negotiation = portal_languages.use_content_negotiation 
AttributeError: use_content_negotiation 
2015-10-09 13:52:29 INFO plone.app.upgrade Starting upgrade of core addons. 
2015-10-09 13:52:29 INFO Products.GenericSetup.tool No upgrades available for profile Products.CMFEditions:CMFEditions. Profile stays at version ('4',). 
2015-10-09 13:52:29 WARNING Products.GenericSetup.tool Version of profile Products.CMFPlacefulWorkflow:CMFPlacefulWorkflow is unknown, refusing to upgrade. 
2015-10-09 13:52:29 WARNING Products.GenericSetup.tool Version of profile plone.app.contenttypes:default is unknown, refusing to upgrade. 
2015-10-09 13:52:29 WARNING Products.GenericSetup.tool Version of profile plone.app.dexterity:default is unknown, refusing to upgrade. 
2015-10-09 13:52:29 INFO Products.GenericSetup.tool No upgrades available for profile plone.app.discussion:default. Profile stays at version ('102',). 
2015-10-09 13:52:29 WARNING Products.GenericSetup.tool Version of profile plone.app.event:default is unknown, refusing to upgrade. 
2015-10-09 13:52:29 WARNING Products.GenericSetup.tool Version of profile plone.app.iterate:plone.app.iterate is unknown, refusing to upgrade. 
2015-10-09 13:52:29 WARNING Products.GenericSetup.tool Version of profile plone.app.multilingual:default is unknown, refusing to upgrade. 
2015-10-09 13:52:29 INFO Products.GenericSetup.tool No upgrades available for profile plone.app.querystring:default. Profile stays at version ('11',). 
2015-10-09 13:52:29 WARNING Products.GenericSetup.tool Version of profile plone.app.theming:default is unknown, refusing to upgrade. 
2015-10-09 13:52:29 WARNING Products.GenericSetup.tool Version of profile plone.app.users:default is unknown, refusing to upgrade. 
2015-10-09 13:52:29 INFO plone.app.upgrade Done upgrading core addons. 
2015-10-09 13:52:29 INFO plone.app.upgrade End of upgrade path, migration has finished 
2015-10-09 13:52:29 ERROR plone.app.upgrade The upgrade path did NOT reach current version 
2015-10-09 13:52:29 ERROR plone.app.upgrade Migration has failed 
2015-10-09 13:52:29 INFO plone.app.upgrade Dry run selected, transaction aborted

Quelle

2015-10-09 Jeff Shafer

Antwort

8

Sind Produkte von Drittanbietern installiert? Vielleicht LinguaPlone? Der wichtige Teil hier ist AttributeError: use_content_negotiation, so scheint es, dass Ihre Migration irgendwo in Products.PloneLanguageTool feststeckt.

Sie können versuchen, Ihr portal_languages-Objekt in ZMI von einer neuen Plone-Site zu aktualisieren, die in derselben Instanz erstellt wurde. Oder deinstallieren Sie LinguaPlone vor der Migration, falls dies möglich ist (dh es werden nicht zu viele Inhalte verwendet).

Quelle

2015-10-10 12:56:32

+6

Danke, das war der Tipp, den ich brauchte. Kein 3rd-Party-Produkt ist jetzt installiert, aber vielleicht hatte ich vor Jahren etwas ausprobiert und etwas Crud wurde zurückgelassen? Im ZMI habe ich eine neue Dummy - Plone - Site erstellt, 'portal_languages' auf den lokalen Datenträger exportiert, bin zu meiner Hauptplone - Site zurückgekehrt, habe 'portal_languages' dort gelöscht, die Datei von der Festplatte importiert und DANN konnte mit meinem fortfahren Plone 4 -> Plone 5 Migration und führen Sie das Import-Tool erfolgreich aus. –

+0

Danke, Jeff, dass du uns erzählt hast, wie du das Problem gelöst hast. Ich bin genau auf dasselbe Problem gestoßen, und Ihre Lösung hat mir auch geholfen. – fulv

 Verwandte Themen

  • Keine verwandten Themen^_^