[ZCM] [ZC] 2062/ 2 Comment "Zope 2.9 breaks manage_historyCopy"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #2062 Update (Comment) "Zope 2.9 breaks manage_historyCopy"
 Status Pending, Zope/bug medium
To followup, visit:
  http://www.zope.org/Collectors/Zope/2062

==============================================================
= Comment - Entry #2 by camil7 on Apr 6, 2006 6:04 pm


Uploaded:  "dump_workaround_for_historyCopy.patch"
 - http://www.zope.org/Collectors/Zope/2062/dump_workaround_for_historyCopy.patch/view
Commenting out a "_p_deactivate" call in OFS/History.py,
class History, method "manage_historyCopy"
works around the problem.
(See attached patch for exact location.)

 Of course I do not propose this patch to fix the issue;
I have no idea whats going on here at all.
It's just maybe a starting for people having more zen
who want to look into this issue.
________________________________________
= Request - Entry #1 by chrisw on Apr 6, 2006 2:40 am

Steps to reproduce:

1. Create a history-aware object such as a PythonScript or PageTemplate

2. Edit it

3. try and use manage_historyCopy to restore it to its pristine state.

I got pretty confused by bouncing around to different URLs in ways that I'm pretty sure never used to happen. I also saw transactions being committed (ie: showing up in boith the Undo and History tabs) but I could never actually get manage_historyCopy to copy the old version to the new version.

I have _no_ idea where to go looking to fix this :-/
==============================================================