Last modified: 2011-11-22 00:36:50 UTC
I just hit a situation where the rename log is left omitting entries. I'd like not to give the exact usernames, but they are available on request by any developer. Can someone confirm the following scenario can cause log issues: Steps to reproduce: 1. User X is created and edits a while. 2. User X requests a rename to user Y, which is granted. 3. To prevent impersonation, userX/Y creates a new account, also called X, so that nobody else can pretend to be his/her old account. End result appears to be: * The user log for Y shows no rename, because rename /targets/ are not logged * The user log for X shows no rename, because the new user X has not been renamed Although the rename log viewed chronologically shows the rename from X to Y, if one knows where and when to look, the individual logs for users X and Y show nothing for renames if one is searching to check whether they were renamed. This is my interpretation of what I'm seeing in the logs. PROPOSED ENHANCEMENT REQUEST: 1. A rename should be shown under the log of both source and target usernames, not just the source username. 2. RevisionDelete should be used to clearly mask the data but leave the fact of a rename in the logs. As such, rename should have an option (subject to some control to be decided) to suppress or redact the original source username in both log entries, similar to how block has a suppress username option for oversighters, if hiding the original username is required. 3. When a user account is renamed, a "stub log" entry should be left on the old account saying "the old account by this name was renamed by CRAT to NEWNAME on DATE". The old username's log should not be entirely blank, that's misleading. Such an entry does not cast a shadow on the new user; rather it helps them and the community by distinguishing the new user from the old user.
This could probably use the log_search table like the "revision author/offender" thing for the Supress Log.