Last modified: 2014-09-05 11:00: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 T72261, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 70261 - Changing the visibility of a log event should also change the visibility of the corresponding null revision
Changing the visibility of a log event should also change the visibility of t...
Status: UNCONFIRMED
Product: MediaWiki
Classification: Unclassified
Revision deletion (Other open bugs)
1.24rc
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-09-01 16:20 UTC by Nathan Larson
Modified: 2014-09-05 11:00 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Nathan Larson 2014-09-01 16:20:02 UTC 
Changing the visibility of a log event should also change the visibility of the corresponding null revision. See bug 70239#c10 .
Comment 1 Jackmcbarn 2014-09-01 16:22:06 UTC 
I'm not convinced that it should, and it's possible to create a few nasty cases where bad thins would happen if it tried.
Comment 2 Nathan Larson 2014-09-01 16:24:08 UTC 
(In reply to Jackmcbarn from comment #1)
> I'm not convinced that it should, and it's possible to create a few nasty
> cases where bad thins would happen if it tried.

What would be some examples? By the way, isn't UNCONFIRMED supposed to mean "possibly INVALID" rather than "possibly should be WONTFIXed"?
Comment 3 Jackmcbarn 2014-09-01 16:30:11 UTC 
UNCONFIRMED is used to mean both (at least here).

The issue is that there's nothing in the database or elsewhere that ties a null revision to its log event. Imagine that you move a page, then later use Special:MergeHistory to move its revisions to a different page. If you then try to revdel the move, it won't know where the revision went.
Comment 4 Jackmcbarn 2014-09-01 16:30:56 UTC 
Also, only move and protection events generate null revisions, and those aren't often revdel'd.
Comment 5 Nathan Larson 2014-09-01 16:36:07 UTC 
(In reply to Jackmcbarn from comment #3)
> UNCONFIRMED is used to mean both (at least here).
> 
> The issue is that there's nothing in the database or elsewhere that ties a
> null revision to its log event. Imagine that you move a page, then later use
> Special:MergeHistory to move its revisions to a different page. If you then
> try to revdel the move, it won't know where the revision went.

Yeah, that's bug 68936 ("log_params should contain the revision IDs of null revisions created by log events"). I happen to want that revision ID data for use by [[mw:Extension:MirrorTools]], but it would help with this bug too.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links