Normally, if you make subsequent edits within a one hour period ($editLockTime
in lib/TWiki.cfg
), TWiki will fold together your changes. This is often the "right thing to do", as it can reduce the visual clutter of diffs.
The "Force New Revision" checkbox is a way to force it to create a separate revision each time you save.
The TWiki06x01.TWikiPreferences variable FORCENEWREVISIONCHECKBOX
controls whether this is checked by default or not.
You can force every save to be a new revision number by editing lib/TWiki.cfg
and setting $ReplaceIfEditedAgainWithin=0
-- JeffreyLaughlin, WillNorris, MattWilkie, SamHasler, CrawfordCurrie
Request
I would like to have a "Force New Revision" check box on the topic editing page. Oftentimes I find myself making several changes in rapid succession that aren't saved as a new revision because they've occured within the no-new-revision time period. Actually maybe the best name for the checkbox would be "Major Revisions" as opposed to the "Minor Revisions" checkbox. That wouldn't be good GUI design though, since the two checkboxes should be but wouldn't be mutually exclusive. Well whatever checking "Force New Revision" wouldn't preclude checking "Minor Changes" as well. It would create a new revision and not notify people. If you've only made small changes that you want commited as a revision immediately but don't want to bother telling people about because they're minor, this may be desireable behavior.
--
JeffreyLaughlin - 25 Mar 2004
I have the same request, I want an extra revision in the history of the topic, even if I edit it 5 minutes apart.
--
BruceDillahunty - 04 Aug 2004
I'd like this facility too. I want to be able to make html forms that will direct save and always force a new revision. But I'd also like to have the choice to be able to edit in the relock time without creating a new revision.
--
SamHasler - 15 Sep 2004
Feature Discussion
You can force every save to be a new revision number by editing
lib/TWiki.cfg
and setting
$doKeepRevIfEditLock
to 0 (zero).
I think you may get the same behaviour by setting
$editLockTime
to zero.
--
MattWilkie - 05 Aug 2004
Doesn't this get accomplished by setting this:
(six spaces)* Set RELEASEEDITLOCKCHECKBOX="on"
Then the "Release lock" checkbox is already clicked and the revision is stepped.
This can be done on a per Web or in any individual topic.
--
JanCarstenJ - 11 Oct 2004
yes, but that isn't what this topic is about. If you make subsequent edits within a one hour period twiki will fold the changes together. This topic is requesting a way to force it to create a separate revision each time.
--
SamHasler - 12 Oct 2004
Implementation Discussion
It would be better to spend the effort doing
ReleaseLocksOnSave which would create a revision for every edit. This is scheduled for
DakarRelease.
--
CrawfordCurrie - 05 Aug 2004
while creating this patch, i added yet more positional parameters to the
search
family of functions. i'd like
DakarRelease to
DeprecatePositionalParameters for functions with large numbers of parameters or optional parameters, and
UseNamedParameters instead.
--
WillNorris - 15 Sep 2004
Rev 3523 (DEVELOP branch) supports the "forcenewrevision" parameter to the query to force it. Will's patch needs to be reduced to just the template changes when it is applied to DEVELOP.
--
CrawfordCurrie - 17 Jan 2005
template changes for
ClassicSkin and
PatternSkin and preferences setting for
TWikiPreferences checked into DEVELOP r3595
--
WillNorris - 06 Feb 2005
docs checked into
SVN r4222
--
WillNorris - 02 May 2005