Last modified: 2009-07-26 02:15:45 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 10293 - There isn't edit conflicts (warning) if the page you're editing becomes protected
There isn't edit conflicts (warning) if the page you're editing becomes prote...
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
unspecified
All All
: Normal minor with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-06-16 21:07 UTC by djpetesz
Modified: 2009-07-26 02:15 UTC (History)
4 users (show)

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


Attachments

Description djpetesz 2007-06-16 21:07:03 UTC
Null edits are often used to indicate something important in the edit history, such as page protections. If someone makes a null edit while a user is editing the page, an edit conflict will not occur.
Comment 1 Roan Kattouw 2007-06-16 21:09:27 UTC
Why should it cause an edit conflict? The changes made in the null edit will be reverted by the next edit, but that doesn't matter, since changes made in a null edit don't change what the page looks like.
Comment 2 Platonides 2007-06-16 21:26:23 UTC
If the protection level of a page is increased after the user opened the edit form, the editor gets no warning that he's modifying a now-protected page.
Comment 3 Roan Kattouw 2007-06-16 22:25:34 UTC
(In reply to comment #2)
> If the protection level of a page is increased after the user opened the edit
> form, the editor gets no warning that he's modifying a now-protected page.

So everyone can (if the timing is right) make a null edit to a protected page. So what? As I said before, null edits don't change the way the page is rendered (sent to the browser), so it doesn't really matter whether you're allowed to edit the page or not: apart from an entry in the page history, you're not changing anything.
Comment 4 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-06-17 02:00:16 UTC
I would agree that you should get a warning if the page has been protected since you started editing, like we have if it's been deleted, but this is a roundabout way of doing it.  I'd suggest you open a request asking for the desired feature directly.  "Edit conflicts" are meant to record, in fact, conflicts between successive edits, and won't even pop up if the changes are substantive provided they're to different lines.  This is by design.
Comment 5 Brion Vibber 2007-06-18 19:06:28 UTC
To clarify -- this *will* trigger an edit conflict, but the conflict will be automatically suppressed by the conflict merging, because there are no conflicting changes.

Since there are no conflicting changes, no user-visible warning is required or shown.

> So everyone can (if the timing is right) make a null edit to a protected page.

No, only if he has permission to edit protected pages.
Comment 6 p858snake 2009-07-26 02:15:45 UTC
Changing Product: Wikimedia → Mediawiki
Changing Component: WikiBugs → Bugzilla
Reason: The wikibugs component is designed for the I.R.C. bot.

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


Navigation
Links