Last modified: 2007-07-10 11:27:17 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 5605 - Edits made as a user is being renamed aren't attributed to the new user
Edits made as a user is being renamed aren't attributed to the new user
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Renameuser (Other open bugs)
unspecified
All All
: Normal minor with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-16 17:42 UTC by David Benbennick
Modified: 2007-07-10 11:27 UTC (History)
1 user (show)

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


Attachments

Description David Benbennick 2006-04-16 17:42:04 UTC
On February 7, 2006 at 23:17, [[Commons:User:Roman pride]] was renamed; see
http://commons.wikimedia.org/w/index.php?title=Special:Log&type=renameuser

At the same time that the rename was happening, that user was editing.  As a
result, an edit didn't get reattributed.  See
[[Commons:Special:Contributions/Roman_pride]].

One way to fix this problem is for [[Special:Renameuser]] to block the user from
editing while the rename is happening.
Comment 1 David Benbennick 2006-04-16 19:04:56 UTC
A better way to fix this problem is for Special:Renameuser to first change the
user's account, so that any new edits are attributed under the new name.  Then,
get the list of the old contributions, and reattribute them.  Apparently it does
those two steps in the wrong order.

I reset the bug summary, since preventing editing is just one possible solution.
Comment 2 Rob Church 2006-04-16 19:22:14 UTC
Altered summary again. The old one misleadingly implied that the extension was
broken, when it's not, per se.
Comment 3 Rob Church 2007-07-10 11:27:17 UTC
This would have been fixed in r23186.

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


Navigation
Links