Submitted by : simon at: 2003-10-26T21:31:57+00:00 (14 years ago)
Name :
Category : Severity : Status :
Optional subject :  
Optional comment :

Reported by DeanG: when running upgradeAll after upgrading to 0.17:

 Sorry, a site error occurred.<p> 

 Traceback (innermost last):
  File /Zope251/lib/python/ZPublisher/Publish.py, line 150, in publish_module
  File /Zope251/lib/python/ZPublisher/Publish.py, line 114, in publish
  File /Zope251/lib/python/Zope/__init__.py, line 159, in   zpublisher_exception_hook
    (Object: FrontPage)
  File /Zope251/lib/python/ZPublisher/Publish.py, line 98, in publish
  File /Zope251/lib/python/ZPublisher/mapply.py, line 88, in mapply
    (Object: upgradeAll)
  File /Zope251/lib/python/ZPublisher/Publish.py, line 39, in call_object
    (Object: upgradeAll)
  File /Zope251/lib/python/Products/ZWiki/ZWikiPage.py, line 2674, in upgradeAll
    (Object: FrontPage)
  File /Zope251/lib/python/Products/ZWiki/ZWikiPage.py, line 2705, in upgradeId
    (Object: Client-Server)
  File /Zope251/lib/python/Products/ZWiki/ZWikiPage.py, line 1963, in rename
    (Object: Client-Server)
  File /Zope251/lib/python/OFS/CopySupport.py, line 226, in manage_renameObject
    (Object: wiki)
 Copy Error

more details, fix in cvs --SimonMichael, 2003/04/03 17:23 GMT
This happens when two similarly-named pages in your old wiki want to use the same page id. You should delete or rename one of them manually. There's a fix in CVSRepository so that upgradeAll will just log this and keep going. (Untested - if you hit this problem, if possible upgrade to the cvs code, try again, and confirm this works.)

need more feedback? --DeanGoodmanson, 2003/04/03 18:29 GMT
To test this next time I upgrade on the live site, should I upgradeId to the Client-Server page for the most detailed test?

need more feedback? --SimonMichael, 2003/04/03 21:01 GMT
Thanks, that would be great. To test this, upgrade another wiki with same issue, or you could recreate it by setting up another clashing page. Eg in the ZMI make a page with title "Client--Server", any id, and run upgradeAll again. The event log should complain about this page but the upgradeAll should complete successfully.

pretty sure this works, closing --SimonMichael, 2003/04/11 13:33 GMT
Status: pending => closed