Last modified: 2008-10-28 02:31:14 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 T17754, 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 15754 - Make a different protect log message when moving a protection
Make a different protect log message when moving a protection
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Page protection (Other open bugs)
1.14.x
All All
: Normal normal (vote)
: ---
Assigned To: Aaron Schulz
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2008-09-28 14:59 UTC by Platonides
Modified: 2008-10-28 02:31 UTC (History)
3 users (show)

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

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

Description Platonides 2008-09-28 14:59:04 UTC 
Moving a protected page, now produces a log protect entry with Mediawiki:protectedarticle and Mediawiki:1movedto2 as reason. Seeing a non-sysop protect a page, using a move reason is annoying. I first thought the log was broken, then I saw it was protected!

It's a good idea but it should be made clearer. I propose making it a new action 'protect_move', with its own messages 'movedprotection' and 'protect_1movedto2'
Comment 1 Aaron Schulz 2008-09-29 13:25:45 UTC 
Done in r41384
Comment 2 Mike.lifeguard 2008-10-24 23:19:04 UTC 
(In reply to comment #1)
> Done in r41384
> 

It's still highly misleading to have anything in the protection log for users who are not sysops. A better solution would be to log the "new" protection under the admin who last protected the moved page. This is analagous to the entry in ipblocklist for autoblocks, where it is logged to the admin who last blocked the user.
Comment 3 Aaron Schulz 2008-10-27 18:07:41 UTC 
The schema does not permit this at this time.
Comment 4 Mike.lifeguard 2008-10-28 02:31:14 UTC 
(In reply to comment #3)
> The schema does not permit this at this time.
> 
See bug 16154.
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