Edgewall Software
Modify

Opened 20 years ago

Closed 18 years ago

Last modified 13 years ago

#1334 closed enhancement (wontfix)

Checkpoint support in wiki editing

Reported by: eric.moret@… Owned by: Jonas Borgström
Priority: normal Milestone:
Component: wiki system Version: 0.7
Severity: normal Keywords: checkpoint
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

Like the Twiki project it would be very nice to have a checkpoint button in wiki editing. The checkpoint button would save the page without creating a new revision then come back to editing mode immediately. This would allow:

  • Avoiding multiple revisions of a wiki page when just saving your work
  • Avoiding losing your work when trying to minimize revisions of a given page

Attachments (0)

Change History (6)

comment:1 by anonymous, 20 years ago

Severity: normalenhancement

comment:2 by Christopher Lenz, 20 years ago

Milestone: 0.9

comment:3 by sid, 18 years ago

Sounds interesting, but you could also just work in an external editor (saving your work there) and paste it back into the wiki box as needed. This solves the problem in the same way without code changes.

in reply to:  3 comment:4 by Christian Boos, 18 years ago

Resolution: wontfix
Status: newclosed

Replying to sid:

Sounds interesting, but you could also just work in an external editor (saving your work there) and paste it back into the wiki box as needed. This solves the problem in the same way without code changes.

I don't think so. I think the motivation for saving often your work comes more from the risk of having the edit overwritten by someone else than by a crash of the application or similar.

I don't think we could provide a way to save changes without creating new versions, and I also don't think that would be a good thing to introduce this extra complexity in the way resource are stored. Think also about saving in a vc backend (#1132), how would you not create revisions then?

So I think the effort should rather be spent on better handling the concurrent edits (#152).

comment:5 by eric.moret@…, 18 years ago

OK, I agree it does not make sens to save temporary edits in the backend. How about just saving those temp edits somewhere locally to the current session, outside of the backend. This would have the benefit to allow for recovery in case of browser crash or unexpected client side issue.

comment:6 by sandinak, 13 years ago

I too want this functionality .. gonna take a stab at it as we need it significantly.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Jonas Borgström.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Jonas Borgström to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.