Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-16) was last changed on 26-Sep-2007 23:09 by JanneJalkanen  

This page was created on 23-Aug-2005 12:56 by GregorHagedorn

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 27 removed one line
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!
At line 29 added 73 lines
----
This maybe be difficult to handle in a conflict situation. But it's certainly worth considering.
-- JanneJalkanen
----
One thing that immediately comes to mind is this scenario: someone spends say, 59 minutes editing a page, in multiple sessions. In that last minute they accidentally delete a substantial portion of the page and click on the Save button. In the current situation, they could just go back to the last revision, but it ''seems'' that in your proposal they would lose the entire hour's work. I'm not sure I'd even want this as an option, honestly. I don't mind the disk space, and having multiple revisions of a page during an editing session might be considered by some to be a Very Good Thing. As a writer, I might like a paragraph I had deleted twenty minutes ago, and currently I can recover that if I'd saved it. Revision control is a godsend. Perhaps I'm not understanding your proposal correctly — are the minor revisions created by a single user during that hour also stored in some way, or after one hour is there just one stored, recoverable revision?
-- MurrayAltheim
----
In regard to Janne's point: Can you explain a scenario where it would not work in a conflict situation (users A and B):
A saves\\
A continues to edit\\
A saves within 1 hour\\
-> Result is one version
A saves\\
A continues to edit\\
B starts to edit\\
B saves\\
A saves within 1 hour\\
-> Result is three versions (A B A)
With regard to Murray: The proposal does involve some tradeoff. However, the major problem when actually using any wiki to collaboratively develop content is to understand what is new and what has been updated or added by others. Thus in my experience, the Diff function is one of the central points. Having all versions is theoretically sufficient, but if in practice it becomes too cumbersome to understand which versions are actually the relevant and to follow the updates, the usability suffers.
I propose to introduce a property in the properties file, called something like: {{{NoVersioningSaveBySameAuthorIntervalMinutes}}} or something much better named. Setting this to 60 would create a 60 minute time span, setting it to zero would recreate the current behavior (any save is considered a new version and can be compared with diff functions). So nobody would have to make the same choice between usability and perfect change tracking.
-- Gregor
----
Gregor: if setting the property to zero reproduces the current situation, I certainly have no problem with it, and we might investigate setting it to 60 minutes to see the impact. We're currently in a prototyping mode right now, so if things are a bit unstable, our ''bleeding edge'' users won't mind so much. It's after our director begins using the wiki that we have to be more cautious... -- MurrayAltheim
----
Is there any compelling reason to have JSPWiki decide autonomously (based on 60min) whether or not a new version is required to be saved?
As alternative, we could add a checkbox next to the save button of the edit-page, where the user can indicate whether or not the change is editorial (and thus a save would not require a new version).
Eventually, we could have wiki make a suggestion based on the time-span: when editing within one hour, the checkbox could be checked.
-- [DF|DirkFrederickx]
----
I like this idea, however it is implemented. For now, I plan to incorporate the Gregor's changes into the [JDBC Providers] as an optional feature.
-- [Daggerbox]
----
There is a possible solution for this in [VersionOverwrite].
Janne, would you be willing to takes this in ? I think this is really a generic feature increasing usability of the version history a lot !
-- [DF|DirkFrederickx]
----
I'll consider it once we get 2.4 stable... At the moment any new feature will only make things later.
-- JanneJalkanen
----
@Janne: v2.4 is stable now. Any chance this Idea can make it into the next release ? --[DF|DirkFrederickx]
Version Date Modified Size Author Changes ... Change note
16 26-Sep-2007 23:09 5.488 kB JanneJalkanen to previous
15 26-Sep-2007 01:50 5.516 kB 63.241.9.240 to previous | to last
14 26-Sep-2007 01:49 5.503 kB 219.138.204.162 to previous | to last
13 04-Jan-2007 21:51 5.488 kB 84.197.115.97 to previous | to last Question to Janne
12 13-Jan-2006 10:41 5.358 kB JanneJalkanen to previous | to last
11 12-Jan-2006 20:50 5.226 kB DirkFrederickx to previous | to last
10 25-Aug-2005 03:59 4.983 kB Daggerbox to previous | to last
9 25-Aug-2005 02:05 4.812 kB DirkFrederickx to previous | to last
8 25-Aug-2005 00:02 4.3 kB MurrayAltheim to previous | to last
7 24-Aug-2005 14:08 3.879 kB GregorHagedorn to previous | to last
6 24-Aug-2005 14:06 3.869 kB GregorHagedorn to previous | to last
5 24-Aug-2005 02:02 2.567 kB MurrayAltheim to previous | to last
4 24-Aug-2005 01:27 2.359 kB MurrayAltheim to previous | to last
3 23-Aug-2005 22:43 1.571 kB JanneJalkanen to previous | to last
2 23-Aug-2005 12:58 1.591 kB GregorHagedorn to previous | to last
1 23-Aug-2005 12:56 1.667 kB GregorHagedorn to last
« This page (revision-16) was last changed on 26-Sep-2007 23:09 by JanneJalkanen