create new tag
, view all tags

Purge Revision History

After editing a topic for some times, the revision numbers increase very fast and maybe some of the old stuff is not necessary any more. There should be a purge functionality which deletes old versions.

See also CurrentFunctionalityWithRevisions

-- JoergBieri - 13 May 2003

I agree!

-- MartinCleaver - 15 May 2003

Five years ago.. and nobody needs it ??? Strange... I'll do.

-- TWikiGuest - 13 Aug 2008

As part of the CleaningUpCodevRevisited work, I'm "resurrecting" this kind of old feature requests.

I updated the form, and put you as the commited developer. Be sure to read the DeveloperResponsibilities and TWikiReleaseManagementProcess.

Happy Coding smile

-- RafaelAlvarez - 14 Aug 2008

IMHO "history is history" and should not be changed/edited/purged, however CurrentFunctionalityWithRevisions points out a good reason to "forget" some revisions (sensible data exposure). Let's discuss a bit more about this and build a detailed specification.

I'm not sure that NextLevel can be the CommittedDeveloper, since he/she doesn't have check-in access. I will be happy to see a new developer, maybe you can tell us a bit more about you, NextLevel. See SoYouWantToBeATWikiDeveloper.

-- GilmarSantosJr - 14 Aug 2008

This is a feature that I personally think would fit well in a plugin.

Many corporate users see such a feature as something very unwanted. The thing that makes the soft security (anyone can edit anything but we know who you are and what you did) is the fact that you have full audit trail of anything.

So I would not like to see it as a standard feature that is always there. But as a plugin people can choose to add it. Such a feature should for sure also be one that can be limited to admins only.

As a plugin no decision has to be made. Anyone can just start coding and post it on twiki.org.

-- KennethLavrsen - 14 Aug 2008

I guess that the undertaking of implementing this as a plugin will discover some functions that need to be implemented in TWiki::Func.

-- RafaelAlvarez - 14 Aug 2008

I agree with Kenneth. In most corporate settings you want a complete audit trail. You lose that if you fiddle around with history. Version control is out of the way, and disk space is cheap. See for example the Sandbox.WebHome page, it has over 3500 revisions, and it does not matter on usability.

Except for one thing: By default, the history should show only the last 5 or so revisions, with a paging mechanism for more. This is for performance and convenience.

-- PeterThoeny - 16 Aug 2008

Edit | Attach | Watch | Print version | History: r8 < r7 < r6 < r5 < r4 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r8 - 2008-08-16 - PeterThoeny
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.