|Date|23-Aug-2005 12:56:36 EEST
|JSPWiki version|2.2.28
|[Idea Category]|GenericIdea
|[Idea Status]|NewIdea

I have previously used TWiki and I prefer the way it handles multiple sequential saves by the same user:

Within a given timeframe (default 1 hour, should be definable as a property) multiple saves by the same user overwrite each other without creating new versions. 

That is: the first save always creates a new version and backs up the previous version. The following saves first check: is user same, and is current save time less than an hour away from previous update. If so, no new version is created and the page text and the modification date are directly overwritten.


Often a page is saved and when seeing the result yet another point is detected or something forgotten is remembered. This frequently leads to multiple minor edits following a major edit.

This feature is not intended to save disk space, it is highly useful to make the revision control and comparison feature more useful, because minor are already compacted.


We have changed the jdbc provider to achieve this and it required only a handful lines of code in updatePageText. Is this more complicated with the file-system providers?

See also [Idea Save And Continue Editing] which may be covered by this.

Other problem: Although to a user after submitting a bug or idea it looks like a facitility to update the submission, (the submitted text is redisplayed as a form with submit button again) it rather creates a new version!