Page MenuHomePhabricator

Prevent edit conflicts with "in use" warning
Closed, ResolvedPublic

Description

Author: ui2t5v002

Description:
When someone presses edit, a flag should be flipped so that if someone else
presses edit they get a simple notice at the top of the page that it MAY be in
use and when the edit button was pressed. This will not prevent anyone from
editing, it will just suggest that they wait a bit. Exactly like an inuse
template, but automatic.

When Person A presses "Edit", the flag is flipped. If Person B then presses
"Edit" they will see "Another user may be editing this page. The Edit button was
pressed at 15:23, May 30, 2005. You might want to wait a few minutes to avoid
edit conflicts." Every time Person A presses "Show preview", the message will be
updated and the timer will be reset. (Refreshing Person B's screen at this
point will show "Another user may be editing this page. The Show preview button
was last pressed at 15:26, May 30, 2005." instead.) If Person A never saves
their page, the notice will disappear when the timer runs out. The timer runs
out after x minutes since the last button press by Person A.

It should not indicate a potential conflict if you are editing two different
sections.

I noticed this is already done on moinmoinwiki.

See above URL for more discussion.


Version: unspecified
Severity: enhancement
URL: http://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28technical%29&oldid=15484838#Avoiding_edit_conflicts

Details

Reference
bz2438

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 21 2014, 8:35 PM
bzimport set Reference to bz2438.
bzimport added a subscriber: Unknown Object (MLST).

gangleri wrote:

Hallo!

I thing this is a wrong approach. What if person A just looks at the code but
never saves the page and person B is waiting. It is kind of "mental" deadlock.
Personaly I start editing on a problem , open dozens of other browsers (with or
without editing) and save after several hours.

At Nuka-Wiki I have experienced some weeks ago an implementation with the
notification that the page was *deleted* *since* edit was pressed. I thing this
makes more sense because it averts about *real* conflicts. The new button "Show
changes" allows anyway "diffs" *before* saving.

Regards Reinhardt [[user:gangleri]]

ui2t5v002 wrote:

I thing this is a wrong approach. What if person A just looks at the code but
never saves the page and person B is waiting.

Sure. But how often does this happen? Edit conflicts themselves happen rarely,
but are very frustrating when they do. I know personally I would see the
warning message and go do something else for five minutes and come back and see
if it is still there.

It is kind of "mental" deadlock.
Personaly I start editing on a problem , open dozens of other browsers (with or
without editing) and save after several hours.

At Nuka-Wiki I have experienced some weeks ago an implementation with the
notification that the page was *deleted* *since* edit was pressed. I thing this
makes more sense because it averts about *real* conflicts.

That is a good reason, too.

The new button "Show
changes" allows anyway "diffs" *before* saving.

I don't know about this button.

ui2t5v002 wrote:

It is kind of "mental" deadlock.

That's the whole point.

gangleri wrote:

compare with

bug 1510: Provide "edit warning" for pages when someone else has just started
editing

  • This bug has been marked as a duplicate of 1510 ***