- 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.