Last modified: 2011-03-13 18:05:36 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 1716 - reverting can never cause an edit conflict
reverting can never cause an edit conflict
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
PC All
: Lowest major with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-03-19 18:55 UTC by Tomer Chachamu
Modified: 2011-03-13 18:05 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Tomer Chachamu 2005-03-19 18:55:03 UTC
"Reverts never cause an edit conflict - if between you pressing edit, and then
pressing post, someone else edits the page, their edits will be silently
overwritten (though still in the page history). Beware of reverting high-traffic
pages! Conversely, if it looks like someone has deleted your edits, consider if
it's more likely that it's one of these unfortunate reversion conflicts."
Comment 1 Tomer Chachamu 2005-03-19 18:55:41 UTC
Clarification: that it text from the URL. I haven't tested this myself.
Comment 2 peter green 2005-03-19 18:57:08 UTC
yes it is known that editing an old version WILL NOT create an edit conflict
this is by design

this should be in the help pages but it doesn't belong here
Comment 3 Tomer Chachamu 2005-03-19 19:04:52 UTC
Why is this by design?

Note You need to log in before you can comment on or make changes to this bug.