Question

Okay, it seems to have been a bad idea to do two things at the same time:

• Upgrade from Cairo to 4.1.2
• Move content from Main to General Web.

In our old installation we had the content in the Main web. In the new installation I decided to cleanly separate content from organizational data. So, what I did was principally this:

1. Install new TWiki.
2. Create General web.
3. Make a copy of the new General web.
4. Copy old Main Content into new General web.
5. Copy content of the copied original General web back to the just filled General web (but merged old and new content in the WebHome topic).

I expected that all user data would now stay in the Main web, leaving General alone.

Something must have gone wrong. Among unexpected side-effects when creating new users (can't remember exactly, will tell more when I have to add the next one), I have a strange behaviour of the leases:

• When a user who got his account after we upgraded to the new TWiki edits and saves a topic, the lease file stays and other users are informed that the user does/did some editing. That is expected, since:
  • {ReplaceIfEditedAgainWithin} 3600
  • {LeaseLength} 3600
  • {LeaseLengthLessForceful} 3600
• When an old user does the same, the lease file vanishes directly after the user saves the topic.

Something is obviously not set up correctly for old users. Maybe this wrong setup causes the problems of ChangesAndDiffsOmittingRevisions also.

I checked the documentation an did quite some file content checks but am still lost.
Any idea?

Environment

-- DetlefMarxsen - 13 Aug 2007

Answer

If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.

Just had another strange behaviour after concurrent view/edit, which may be caused by the disturbed leases handling:

Changed a table and afterwards the table contained code similar to:

<del>|blah|
</del><ins>|blah2|
</ins>

Oops?

-- DetlefMarxsen - 14 Aug 2007

I would expect the lease file to disappear after the topic is saved. And the behaviour you report is also what I would expect after a concurrent edit which resulted in a merge. I'm not sure exactly what your problem is here.....

-- CrawfordCurrie - 20 Aug 2007

But how does the LeaseLengthLessForceful setting work? Isn't it necessary to keep the lease file to enable others to detect that state?

-- DetlefMarxsen - 22 Aug 2007

LeaseLengthLessForceful applies only if the lease times out - i.e. the lease expires without a save. The lease is always removed after the editor has stated they are finished editing (either saves or cancels)

-- CrawfordCurrie - 22 Aug 2007