Last modified: 2012-12-14 23:02:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T8797, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 6797 - Disable automatic conflict resolution on request
Disable automatic conflict resolution on request
Status: NEW
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
1.8.x
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-07-24 01:34 UTC by Lupin
Modified: 2012-12-14 23:02 UTC (History)
1 user (show)

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


Attachments

Description Lupin 2006-07-24 01:34:53 UTC
I'd like to be able to reliably revert to a particular version as a non-admin
user. Currently, my scheme is to (1) edit the old revision and (2) hit the save
button. However, if a vandal edits the page between steps (1) and (2) in a
section unaffected by my edits, then the automatic conflict resolution will
ensure that his edits persist in my final revision.

To get around this, I'd like to be able to explicitly request that automatic
conflict resolution be disabled when I save a page. I want to always be taken to
the manual conflict resolution page.
Comment 1 SJ 2012-12-14 23:02:16 UTC
If there were an api call for "revert to version X" then even without changing the default interface there could be a gadget that adds a "revert to this rev." link in the history.   I can imagine other uses for such a call (for instance, it would simplify maintaining a wiki for maintaining a static snapshot such as WP 1.0 that relies on 'last good revision' iterations).

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


Navigation
Links