[wp-meta] [Making WordPress.org] #3284: Character bug on profile name

Making WordPress.org noreply at wordpress.org
Thu Aug 30 15:44:43 UTC 2018

#3284: Character bug on profile name
 Reporter:  jranavas     |       Owner:  (none)
     Type:  defect       |      Status:  closed
 Priority:  low          |   Milestone:
Component:  Profiles     |  Resolution:  fixed
 Keywords:  needs-patch  |

Comment (by coffee2code):

 As explained upticket, the primary user account data is stored in a
 database that is `latin1`. BuddyPress/Profiles runs in a database that is
 `utf8`. The differing charsets can cause issues during cross-database
 reads and writes. For this specific set of issues, the `display_name` user
 field can be set via a user's profiles.wordpress.org profile or the
 support forums profile. If set via profiles.wordpress.org, `utf8` data was
 getting saved into the `latin1` user table. If set via the support forums
 profile, the Profiles name could appear ok, but the "Logged in as:" name
 wouldn't be proper. The two commits fix the issues by ensuring `latin1` is
 used for these particular reads/writes.

 This doesn't fix the data that is already stored as the user's
 `display_name`. Such users would just need to edit their profile (in
 either location) and save the changes. In Profiles, it's the "Name" field,
 in the support forums profile it is "Display Name".

 [attachment:meta-3284_fixed-example.png] shows a Profile with characters
 in the name that would have not rendered properly before the fixes.

Ticket URL: <https://meta.trac.wordpress.org/ticket/3284#comment:23>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list