[wp-meta] [Making WordPress.org] #3284: Character bug on profile name
Making WordPress.org
noreply at wordpress.org
Wed Jan 24 23:46:10 UTC 2018
#3284: Character bug on profile name
----------------------+-----------------------
Reporter: jranavas | Owner:
Type: defect | Status: reopened
Priority: low | Milestone:
Component: Profiles | Resolution:
Keywords: |
----------------------+-----------------------
Comment (by dd32):
This is something to do with the fact that
buddypress.org/profiles.wordpress.org is forced into `utf8` mode where as
every other site on w.org (and the shared database being used for it all)
is `latin1`.
I don't know why BuddyPress is using utf8, I think the idea was to solve
this kind of problem, but it only causes more of them IMHO.
I'm not sure of the best way forward myself, as I'm not sure where the
issue is.
Probably need to track down where the data is being inserted or retrieved
incorrectly, or maybe even a cache being retrieved and fix the DB
collation for the query - There's a few places where we do something akin
to `$current_collation = $wpdb->.....; $wpdb set as utf8;
$wpdb->get_results(); $wpdb set as $current_collation` to temporarily
switch types.
I know there's another ticket for a Profiles refresh, unfortunately I
doubt that'll fix the DB issues and we'll probably end up building more of
these issues in.
To debug, one option may be to temporarily disable memcache for your
sandbox and see if when it's using just straight DB access if things break
or not. Unfortunately disabling memcache will probably result in some
really bad queries and super-slow page loads for certain things that might
mean debugging is impossible.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/3284#comment:10>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list