version deleted but there is still a version lock
I have a Zope folder which contained a version a long time ago. The version was deleted, but in the management-screens I always get a version lock. I cannot add documents, and I cant change a few of the existing docs. How can I make my existing objects notify that theres no version anymore and therefore no locking necessary? Unluckily this happened with a projectsite we have on the net. There are a lot of people waiting to see new content which I cannot add.... yours, andy ap@net22.net
Andy Pahne wrote:
I have a Zope folder which contained a version a long time ago. The version was deleted, but in the management-screens I always get a version lock. I cannot add documents, and I cant change a few of the existing docs.
How can I make my existing objects notify that theres no version anymore and therefore no locking necessary?
Unluckily this happened with a projectsite we have on the net. There are a lot of people waiting to see new content which I cannot add....
Yep, this happens to me a lot. Fortunately it isn't that hard to fix -- just create a new version in the same folder with the same id as the previous one (or go to Undo and remove the deletion of the Version). Once the Version is back, you can save the changes, discard the changes, etc. --Paul
----- Original Message ----- From: Paul Everitt <paul@digicool.com> To: Andy Pahne <ap@net22.net> Cc: <zope@zope.org> Sent: Monday, November 15, 1999 2:31 PM Subject: Re: [Zope] version deleted but there is still a version lock
Andy Pahne wrote:
I have a Zope folder which contained a version a long time ago. The version was deleted, but in the management-screens I always get a version lock. I cannot add documents, and I cant change a few of the existing docs.
Paul Everitt then wrote :
Yep, this happens to me a lot. Fortunately it isn't that hard to fix -- just create a new version in the same folder with the same id as the previous one (or go to Undo and remove the deletion of the Version). Once the Version is back, you can save the changes, discard the changes, etc.
--Paul
Yes, that was the idea that I had first. But I can't create a version. Here's the result if I try to do so: The Server has encountered an error while publishing this resource. Error Type: VersionLockError Error Value: ("'\\000\\000\\000\\000\\000\\000\\002\\017'", 'projectsite/schomburg/dirki') and in the source of the error-page: Traceback (innermost last): File /zope/Zope-2.0.1-src/lib/python/ZPublisher/Publish.py, line 214, in publish_module File /zope/Zope-2.0.1-src/lib/python/ZPublisher/Publish.py, line 179, in publish File /zope/Zope-2.0.1-src/lib/python/Zope/__init__.py, line 201, in zpublisher_exception_hook File /zope/Zope-2.0.1-src/lib/python/ZPublisher/Publish.py, line 169, in publish File /zope/Zope-2.0.1-src/lib/python/ZODB/Transaction.py, line 237, in commit File /zope/Zope-2.0.1-src/lib/python/ZODB/Connection.py, line 323, in commit (Info: (('OFS.Folder', 'Folder'), '\000\000\000\000\000\000\002\017', '')) File /zope/Zope-2.0.1-src/lib/python/ZODB/FileStorage.py, line 502, in store (Object: /zope/Zope-2.0.1-src/var/Data.fs) VersionLockError: (see above) ??? Yours, Andy
This happened to me once. Jim Fulton gave me the secret recipe, but it has a downside (which luckily did not affect me!). If you have no other versions that you need to preserve, you can shut Zope down, then delete the files that contain all of the version info in them (at least that's how it worked in 1.10.3). In 1.10.3 they are called Data.bbb.trans and Data.bbb.trans.index. So, check if you have files called Data.fs.trans, etc... After deleting those files, restart Zope, and all is well again (at least it worked for me). If you have transactions you need to keep, then you will either need to save them (meaning publish them!), or figure something else out... Hope this helps.
participants (3)
-
Andy Pahne -
Hadar Pedhazur -
Paul Everitt