#2235 closed defect (bug) (invalid)
Upgrading does not preserve display name preferences
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 2.0 |
| Component: | Administration | Keywords: | displayname users user |
| Focuses: | Cc: |
Description
I've just upgraded a blog (entirely successfully) from 1.2 - first 1.2->1.5, and then 1.5 -> 2.0.
Under 1.2, display names were preserved entirely correctly, and I believe this was the case under 1.5 (having upgraded other blogs from 1.2 before). However, by 2.0, the display name preferences for all my 25 users have been reset to being the login name (as opposed to Firstname+Lastname). Obviously this is a slight inconvenience; in the database, the "display name" field isn't a preference setting, but a text field.
For starters, I'd hope that the import problem could be fixed; also, in future, given "display name" is a limited array of possibilites based on login, firstname, and surname, it might be worth making this a preference.
Change History (2)
Note: See
TracTickets for help on using
tickets.
Couldn't duplicate this problem.
Upgraded a 1.5.2 blog to 2.0.1 and had different settings for the "How to display name" field and all variations seemed to upgrade properly to the "Display name publicly as" field in 2.0.1.
infovore, don't know if this explains what you saw, but at 1.5.2 there was a user_idmode field in wp_users; that field no longer exists. It seems that user_idmode field was normally set to nickname which was also used as the login for newly added users in 1.5.2. In 2.0.1 there is a new field called display_name in wp_users that replaces the old user_idmode functionality.