Steps to reproduce

  1. open ?action=edit in one browser for a page that doesn't exist
  2. open ?action=edit in another browser for the same page
  3. put "1" into the first editor, save page
  4. put "2" into the second editor, save page
  5. Expected result
    Editing conflict shown to second editor
    Actual result
    page saved with two revisions

Component selection

Details

This Wiki, applies to versions 1.6, 1.7, 1.8, 1.9.

Workaround

Discussion

I tend to think that the best way to fix this bug is to review the usage of the 'rev' variable in the save code, a first look suggests that it might even be possible to get moin to crash there with some unexpected input/race conditions. It seems that 'rev' is always supposed to indicate the revision that the user intended to make a new one of, where the problem is that 'not rev' is treated specially. -- JohannesBerg 2008-03-26 13:44:21

This issue may be solved after merging 2.0-storage-editor-amartani

Plan


CategoryMoinMoinBug CategoryForMoin2

MoinMoin: MoinMoinBugs/ConflictDetectionNotWorkingForNewPages (last edited 2010-08-14 08:57:55 by p5B1738CD)