For many good reasons that may vary depending on the site in question, I am very happy about the fact that Drupal facilitates user name changes.

It can be improved, though, with some small adjustments, in particular if my hunch about this having some relevance for OpenID is correct (see below):

If I understand it correctly, as it currently works in Drupal 5, the comments table actually stores _both_ the user id (uid) AND the current user name for each comment. This means that when a user changes his name later, the name used originally when posting the comment, will be used even after a name change, with a link to the user profile which "now" have a different user name. Almost perfect.

When contributions are made (main posts or comments), it should be possible to retrieve a list of (and also to search for..?!) which contributions has been made with a specific user name. To facilitate this, there could be a link on the user page to a page that lists the user name change history for that user, listing only those name changes that has in fact been used in posts (main content or comments).

It should list the user name change history as a distinct list, with each name appearing only once (newest on top), each entry with additional information about the "last post: " with a link to that last post/comment made by that username. In addition to that link on the timestamp, there should be a link on the user name itself to a page that lists all comments and contributions made with that particular username (not the user id, but that user name).

This way, the community is provided practical tools to find back content and relations, and the flexibility of each user is provided. Many of us will in many situations remember the user name rather than the post title etc. So it is practical to provide this option.

Further:

The above may suggest that we might also consider adding a special username_history table with username as "unid" field to store with each main post too, not only for comments. Each time new content is posted, main or as comments, or being updated, then a quick check of the user name will determine if it matches the name currently registered with the current node or comment. if there is a change, a new record will be made in that table, if not, it will leave it untouched. That part might perhaps happen in the cached and not necessarily affect performance. We are not changing user names that often, after all, so I dont expect this to be a performance concern.

OpenID related:(?)
Regarding the new OpenID support of Drupal 6, I havent given it enough thought yet, but it appears to me that some of the concerns regarding multiple identities etc. could further emphasise the importance of having something like the above mentioned features.

End note:
When a user changes his/her user name without making any contributions, either new posts or comments, and then changes it again, so that the previous change had "practically no effect" for the community or contributions, then that user name should be irrelevant. Should not be listed even as part of the "history", I think. This is useful in case a user regrets a name change and want to correct it before it has been used. I see only flexibility in that, not a problem.

Comments

Leeteq’s picture

Related: see my comment in the OpenID discussion here:
http://drupal.org/node/152893#comment-244048

dpearcefl’s picture

Is there any interest in this issue right now? If so, it should be moved to D8.

Leeteq’s picture

Title: Better facilitation of user name changes (OpenID related too, perhaps) » History of changes to Username (and OpenID?)
Version: 6.x-dev » 8.x-dev

Moving to D8 for further input. Changing to better title too.
(The visibility of such history pages might also be roles-based, for extra flexibility, perhaps especially related to OpenID.)

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Version: 9.5.x-dev » 11.x-dev
Status: Active » Closed (outdated)

As there hasn't been any movement in 12 years going to close out.

If still a valid feature request please feel free to reopen, updating issue summary how this could be useful for D10.

Thanks!