Feature #2698


Wiki Auto-Save currently editing page

Added by Jos Yule over 15 years ago. Updated over 9 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


It would be nice to have the currently edited page auto-saved every once and a while, so that changes are not lost inadvertently.

Unfortunately, this can lead to wiki-history bloat. A possible solution to this is to have "minor-revisions" to pages. These could be "flushed" periodically from the wiki-DB, as they would only be used as temporary placeholders before a user "saves" their edits to their page.

Actually, in thinking this through, i can see that this might lead to clobbering of other users work, if two users are editing the same page at the same time... Could the auto-save save the changes locally, at least? Just so that the work is not lost if the user's browser goes down, or something...

Actions #1

Updated by Axel Voitier over 15 years ago

I had a similar though about that some days ago, when I was chatting with a user of Twiki. Twiki got a feature to invisibly edit a revision. I am totally against such thing. But the user was using it to temporary save his work.

I rewrote the use case and plan to develop the following feature for my Redmine use (but not for the moment):

As it is often that when editing a wiki page we want to save modifications without publishing them publicly (don't publish unfinished/unstable work), a "save in working copy" action would benefit wiki edition.

Behaviour would be:
  • having a specific option or button to save an edited wiki page that:
  • save the edited content on the server
  • does not produce any new revision of the page
  • is strictly private and re-editable only by the user itself
  • when edition work is over, a traditional save action publish a new revision of the page, dated at this precise moment (and not timed when we did a previous "save to working copy" action
  • if conflict with a new revision happens (someone(s) else published new revision(s) since we firstly edited the working copy), then:
  • show differences between head revision and edited revision, but without local changes made in the working copy
  • propose an edition possibility to merge the working copy changes with head revision changes
Actions #2

Updated by Jerome Vanthournout over 15 years ago

Same feature than #1888

Actions #3

Updated by Emrah KAVUN almost 15 years ago

Any update regarding this feature?
I checked issue #1888 but there doesn't seem to be any progress about it either.


Actions #4

Updated by Chris Grieger almost 15 years ago

Working on the basic implementation of

-ability to save the current draft
-when going back to edit the page the draft is loaded into the editor

-maybe autosave

Actions #5

Updated by Alex Dergachev almost 15 years ago

That's great news Chris, we're eagerly waiting to see the results of your work!
Please let me know if you need help bug testing it.

Once the redmine side of things has been built, we may be able to help out with the js autosave functionality.


Actions #6

Updated by Joe Hodsdon almost 15 years ago

Looking forward to it. I'm happy to help test as well. Would be nice if the JS responded to a Ctrl-S keypress by saving a draft copy, too.

Actions #7

Updated by Udit Sajjanhar over 14 years ago

Hi Chris,

Are you still working on the patch for this feature?

Do you have some design documents so that in case you have not taken up this issue, I can continue from where you left.


Actions #8

Updated by Toshi MARUYAMA about 13 years ago

  • Category set to Wiki
Actions #9

Updated by N Bischof about 13 years ago

I agree, this is must-have feature.

What about a button "Save Minor Changes" (as confluence has it), but which:

  • is only visible if the user has locked the issue (or wiki page), and
  • if pressed, saves the current changes without modification emails

The first condition prevents us from conflicts when 2 user update the same issue.
Modification emails still may be sent once the user unlocks the issue.


Also available in: Atom PDF