WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #39123, comment 6


Ignore:
Timestamp:
12/06/2016 11:02:45 PM (3 years ago)
Author:
johnjamesjacoby
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #39123, comment 6

    initial v1  
    11For BuddyPress & bbPress, username mentions in content blocks are problematic in exactly the way you'd expect them to be. They are linked on output, and only on usernames that exist, so old links would not link to new usernames. The human element of a username change is also weird, but in my experience people accept & adapt this change relatively quickly.
    22
    3 I think the reason is not having a system in place to handle author archive redirections similar to `redirect_canonical()`. That, and any unknown third-party integrations. Username changes on WordPress.org, for example, would cause some level of breakage to Trac and Slack. Username changes on WordPress.com would break OpenID integrations. Without a way to redirect requests to old slugs, we can all imagine weird things happening with these integrated systems. Also not sure if any LDAP implementations use the nicename at all.
     3I think the main reason this isn't already in core is a lack of a system to handle author archive redirections (similar to `redirect_canonical()` for single posts.) That, and any unknown third-party integrations. Username changes on WordPress.org, for example, would cause some level of breakage to Trac and Slack. Username changes on WordPress.com would break OpenID integrations. Without a way to redirect requests to old slugs, we can all imagine weird things happening with these integrated systems. Also not sure if any LDAP implementations use the nicename at all.
    44
    55FWIW, I do agree that certain types of user accounts should be trusted to more easily make these changes within WordPress, both to the `user_login` and the `user_nicename` fields. This is probably super/global-admins in multisite, and regular Administrators in single-site. In my imagination, some descriptive text to warn against potential third-party problems is maybe wise, but it should be something that's coy enough to not prohibit the larger percentage of admins from using the feature.