Question

I'm trying to move our Twiki installation from a RedHat 9 box to a Gentoo box. Everything seems to be working fine, except when I save changes to a topic. The revision number does get incremented when saving the topic, but the changes to the topic are saved.

I saw in the output of testenv that if the webserver is not running as the same user that has locks on all the RCS files, the RCS functionality doesn't work. My RCS files are locked by "nobody", and I updated Apache to run as "nobody" (it was originally running as "apache"). This didn't seem to fix the problem.

Is there anything else that could cause this problem? Is it an Apache2 problem? The install on the RedHat box was running under Apache 1.3.29.

Thanks.

I get this same problem with a clean Twiki install. -- NateDrake - 27 Apr 2004

It is strange, it seems that when I make the first edit to page, a new revision is created, but further changes to the topic don't get new revisions. -- NateDrake - 27 Apr 2004

Environment

-- NateDrake - 27 Apr 2004

Answer

The answer is that I am a total idiot. Twiki combines multiple changes by the same person (within a 60 minute period), so if the same user makes several changes in a row, a new revision is not created.

Sorry to have wasted anyone's time.

-- NateDrake - 27 Apr 2004

• TestTWikienvironment.html: The output of the latest testenv

Nate, you're not an idiot, most people get confused by this for a little while when first learning twiki. You can change the timeout period with the $editLockTime setting in TWiki.cfg (number of seconds). If you want every save to bump the revision number, regardless of the timeout setting, set $doKeepRevIfEditLock to 0 (zero).

-- MattWilkie - 27 Apr 2004

The revision number not incrementing feature also confused us for a while. There does, however, seem to be an actual bug with the timestamp set when keeping the revision number the smae. Check out this snippet from our twiki logs. I edited the twiki topic GregoryGo several times within the hour. As expected, the rev number stayed at 1.2, but notice that the timestamp keeps going back 14 hours. Another "feature"? If it has already been discussed, I apologize for wasting your time, and please point me to the right pages.

By the way, this is not a show-stopper issue, since we just took Matt Wilkie's advice and set $doKeepRevIfEditLock = 0. This increments the rev number as expected, and sets the correct timestamp. There is a minor bug where the rcs info (rev #, timestamp) isn't being logged.

| 17 Jun 2004 - 17:09:09 | User.GregoryGo | save | User.GregoryGo | repRev 1.2 User.GregoryGo 2004/06/17 10:09:00 | 10.4.7.103 |
| 17 Jun 2004 - 17:10:43 | User.GregoryGo | save | User.GregoryGo | repRev 1.2 User.GregoryGo 2004/06/16 20:10:00 | 10.4.7.103 |
| 17 Jun 2004 - 17:11:59 | User.GregoryGo | save | User.GregoryGo | repRev 1.2 User.GregoryGo 2004/06/16 06:11:00 | 10.4.7.103 |
| 17 Jun 2004 - 17:26:51 | User.GregoryGo | save | User.GregoryGo | repRev 1.2 User.GregoryGo 2004/06/15 16:12:00 | 10.4.7.103 |
| 17 Jun 2004 - 17:27:32 | User.GregoryGo | save | User.GregoryGo | repRev 1.2 User.GregoryGo 2004/06/15 02:13:00 | 10.4.7.103 |
| 17 Jun 2004 - 17:28:01 | User.GregoryGo | save | User.GregoryGo | repRev 1.2 User.GregoryGo 2004/06/14 12:14:00 | 10.4.7.103 |
| 17 Jun 2004 - 17:36:46 | User.GregoryGo | save | User.GregoryGo | repRev 1.2 User.GregoryGo 2004/06/13 22:15:00 | 10.4.7.103 |
| 17 Jun 2004 - 17:37:07 | User.GregoryGo | save | User.GregoryGo | repRev 1.2 User.GregoryGo 2004/06/13 08:16:00 | 10.4.7.103 |

* changed $doKeepRevIfEditLock = 0 *

| 17 Jun 2004 - 17:42:32 | User.GregoryGo | save | User.GregoryGo |  | 10.4.7.103 |
| 17 Jun 2004 - 17:43:22 | User.GregoryGo | save | User.GregoryGo |  | 10.4.7.103 |

* note: rev number correctly incremented to 1.3 and 1.4, but no info is logged. *

-- GregoryGo - 18 Jun 2004

the bug Gregory mentions may be TimeTravellingTopics

-- MattWilkie - 20 Apr 2005