Last modified: 2010-05-15 15:42: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 8296 - Move should also move protect history
Move should also move protect history
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
PC All
: Low trivial with 1 vote (vote)
: ---
Assigned To: Aaron Schulz
Depends on:
  Show dependency treegraph
Reported: 2006-12-17 16:31 UTC by Plyd
Modified: 2010-05-15 15:42 UTC (History)
3 users (show)

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


Description Plyd 2006-12-17 16:31:54 UTC
When a page is protected and then moved, the protection is moved, but the
protection log remains on the redirect article.

This provokes examples where page is protected and has no protection log to show.

Imho, we have 3 possibilities :
- move log history (pb with what should be kept or not - rename log etc.)
- duplicate log history
- when we move a protected page, automatically add another log like "Keeping
protection of moved page. Reason was: "

Last one is probably the easiest.
Comment 1 Aaron Schulz 2008-09-05 22:53:33 UTC
Of the 3, I guess the last one is the best
Comment 2 Aaron Schulz 2008-09-24 15:02:20 UTC
Done in r41227
Comment 3 Mike.lifeguard 2008-09-28 21:52:07 UTC
Having logs entries where non-administrators are seemingly protecting pages may be easy, but it is wrong. The log is supposed to reflect what actually happens in the wiki. The log should be moved instead, as with moving the block log of renamed users. There is no new protection, the protection and log are simply moving with the page.

Where you might want new protection log entries is with bug 10527 - protecting the redirect left behind after the move. In such a case, I would rather see this attributed to the last admin who protected the page (as with autoblocks) rather than having non-admins with protection log entries.
Comment 4 Platonides 2008-09-28 22:43:11 UTC
See bug 15754
Comment 5 Aaron Schulz 2008-09-29 12:44:37 UTC
Closing again. Separate bug will be done separately.

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