Last modified: 2007-09-13 11:26:32 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 T11315, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 9315 - Show log fragments for the target user
Show log fragments for the target user
Product: MediaWiki extensions
Classification: Unclassified
Renameuser (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-03-17 08:02 UTC by Nicholas
Modified: 2007-09-13 11:26 UTC (History)
0 users

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


Description Nicholas 2007-03-17 08:02:16 UTC
Hi! I am a bureaucrat on en wiki [[user:Nichalp]]. While carrying out user
renames, I find it very tedious to go through the user logs, so I request the
following features:

When carrying out the special:rename function, I would like mediawiki to alert
bureaucrats if:
* The user is currently blocked
* The user has changed his name before

The bureaucrat can then confirm the rename if possible.

Comment 1 Rob Church 2007-03-17 16:51:05 UTC
A nice means of providing this might be to show log fragments for actions
targeted at the user at the bottom of the page, e.g. their block log, rename
logs affecting them, etc.
Comment 2 Raimond Spekking 2007-05-09 11:39:08 UTC
Button added to show block log fragment for current user with r22020.

A similar button for the renameuser log fragment could be done easily but it is
nearly useless: If a user was renamed earlier, his old username is part of the
comment field, which is not indexed/searchable. 
Comment 3 Rob Church 2007-09-13 11:26:32 UTC
Resolving FIXED, as far as is feasible/helpful.

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