Page MenuHomePhabricator

moving a protected page broke the logs
Open, NormalPublic

Description

REPLICATION

  • protect a page. note "protect" operation in protection log and in history.
  • move the page (redirection created).
  • note that both moved page ("target") and redirection ("source") are now protected. the "protect" action exists in the target's history but not in the target's protection log. actually, target's log is empty (except of the "move").

WHY THIS BEHAVIOR SHOULD BE CONSIDERED A BUG ?

so as far as logs are concerned, the protect operation now appears only in the source log, even though the source is brand new, with empty history.

if the move was done with the intention re-using the source page for a completely different content, the log-entry is confusing at best (it shows for a date and time where this page did not even exist yet - the "source" page begun its existance when the move was executed).

if the move was done with the intetion of asking for its deletion, once it's deleted we lose the log entry completely.

WHAT SHOULD BE THE CORRECT BEHAVIOR?

  • when moving a page, all its logs should move also
  • when moving a protection page and creating a redirect page, the redirect should *not* be protected.
  • if you disagree and think the newly created redirect page should assume the same protection level as the page that was moved, then it should contain one log message for the move, and another for the protection, stated something like "automatically" or somesuch.

peace.


Version: 1.20.x
Severity: normal

Details

Reference
bz38123

Event Timeline

bzimport raised the priority of this task from to Normal.Nov 22 2014, 12:52 AM
bzimport set Reference to bz38123.
bzimport added a subscriber: Unknown Object (MLST).
Kipod created this task.Jul 2 2012, 8:26 PM
Kipod added a comment.Jul 2 2012, 8:32 PM

s/when moving a protection page/when moving a protected page/

You should find a protect log entry under the target like this (at least in 1.20):

HH:MM, DD MM YYYY User (talk | contribs) moved protection settings from "A" to "B" (Reason)

Kipod added a comment.Jul 5 2012, 11:12 PM

clearly wrong behavior.
logically, the logs are just another part of the page history, "meta-history" if you will.

the same logic that's used vis a vis history, should apply to logs.
when you move a page, the "history" remains with the move target, and the move source starts its life with (almost) clean slate, containng only the move operation as "page was created".
it makes no sense that the historical logs remain with the move source, and the target logs begins from 0 at the date of the move (optionally with "move protection" or somesuch, if the target was protected at the point of the move).

for instance, if the page was protected/unprotected in the past, let's say because of repeated vandalizm, how is it logical that the traces of vandalizm (i.e., page history) are with one page, and the traces of pretection/protection removal (i.e. logs) remain with a different page?

there is no other way to describe this behavior than "bug".

fuhghettaboutit wrote:

I just saw this in action. A user at the en.wikipedia help desk was confused because they could not move a page. I don't know if they actually checked the logs, but in order to tell the user definitively that the page was move-protected, as I immediately suspected, I had the trace back the title through two generations of moves to find the protection log entry for the original title.

The fact that there were two generations of moves here shows how problematic this could be. There are pages that have been moved many more times than that and there are many people who are not conversant enough to trace back a page to the original entry, though they may have a very good reason for wanting to see not just the automatic log entry but any tailored edit summary that accompanied it.