Re: [Zope] Versions problem in 2.6.1
Wil Cooley writes:
FWIW, I just spent the last few hours fighting with the same thing. Another thing I'm noticing is that even when I do save the version, the changes aren't publicly accessible.
That's no good.
I couldn't find anything in Collector, and I don't really know enough to be sure I'm not doing something stupid. FWIW, the Versioned files I initially had trouble with were probably put into the version around 2.5.1, remained in the version through the 2.6.0 and .1. But now I'm seeing it again with files that only were created today under 2.6.1.=20 I'm guessing I'll downgrade until I can figure it out. [...]
Interesting: the objects I'm working with now were imported into a clean 2.6.1 installation after being exported (in binary) from a 2.6.0 installation. I have not tried versioning with an object created wholely in 2.6.1. I would just like to be able to unlock the versions that are currently installed. Unfortunately I don't know enough about how ZODB works, nor do I have the cycles right now to dig into the source and figure it out. BTW, Dieter, I further explored the cookie angle, and was able to watch the version cookie come into existence and disappear as I join and quit the versions. This does not appear to be the issue. I'm a bit nonplused by this turn of events. -tree -- Tom Emerson Basis Technology Corp. Software Architect http://www.basistech.com "Beware the lollipop of mediocrity: lick it once and you suck forever"
n Mon, 2003-02-17 at 18:17, Tom Emerson wrote:
Wil Cooley writes:
FWIW, I just spent the last few hours fighting with the same thing. Another thing I'm noticing is that even when I do save the version, the changes aren't publicly accessible.
That's no good.
No, not at all. I'm afraid of the versioning right now. I'd like someone to tell me that working on a version through several upgrades was a stupid thing to do or that I was doing something else stupid. As it is, I'm afraid to use Versions, which were really one of the nice things about Zope.
Interesting: the objects I'm working with now were imported into a clean 2.6.1 installation after being exported (in binary) from a 2.6.0 installation. I have not tried versioning with an object created wholely in 2.6.1.
Did you import into the same path that you exported from?
I would just like to be able to unlock the versions that are currently installed. Unfortunately I don't know enough about how ZODB works, nor do I have the cycles right now to dig into the source and figure it out.
I thrashed about a bit trying to get the lock to go away; I'm not entirely sure how I did it, but I think exporting and imported were part of it. I think I was able to save/commit several times and make them go away Wil -- Wil Cooley wcooley@nakedape.cc Naked Ape Consulting http://nakedape.cc * * * * Linux, UNIX, Networking and Security Solutions * * * * QCSNet http://www.qcsn.com * * * * T1, Frame Relay, DSL, Dial-up, and Web Hosting * * * *
Wil Cooley writes: [...]
No, not at all. I'm afraid of the versioning right now. I'd like someone to tell me that working on a version through several upgrades was a stupid thing to do or that I was doing something else stupid. As it is, I'm afraid to use Versions, which were really one of the nice things about Zope.
Likewise.
Interesting: the objects I'm working with now were imported into a clean 2.6.1 installation after being exported (in binary) from a 2.6.0 installation. I have not tried versioning with an object created wholely in 2.6.1.
Did you import into the same path that you exported from?
Same path.
I thrashed about a bit trying to get the lock to go away; I'm not entirely sure how I did it, but I think exporting and imported were part of it. I think I was able to save/commit several times and make them go away
I ended up exporting the directory and reimporting it into a new installation of 2.6.1: paranoia at its best. -tree -- Tom Emerson Basis Technology Corp. Software Architect http://www.basistech.com "Beware the lollipop of mediocrity: lick it once and you suck forever"
participants (2)
-
Tom Emerson -
Wil Cooley