[wp-meta] [Making WordPress.org] #2280: Broken encoding in some posts on support forums

Making WordPress.org noreply at wordpress.org
Tue Nov 29 01:34:52 UTC 2016

#2280: Broken encoding in some posts on support forums
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  high            |  Milestone:
Component:  Support Forums  |   Keywords:
 Since yesterday (November 28th, Monday), some posts on support forums are
 occasionally displayed in wrong encoding (Windows-1252 instead of UTF-8),
 which leads to broken Cyrillic or Japanese characters.

 A workaround is to click Edit and re-save the affected post, which makes
 it readable. One user reported that email notification for the post was
 readable as well, only the post itself in the forums thread had wrong

 [https://wordpress.slack.com/archives/meta/p1480297680001613 First
 reported in #meta] by @rmccue, regarding a post on make/core:
 rmccue: https://make.wordpress.org/core/2016/11/25/preferred-languages-
 research/ has an encoding bug
 rmccue uploaded an image: Screenshot 2016-11-28 11.47.38.png

 dd32: Calling @pento is ^ related to your HyperDB change?

 rmccue: Also seeing the classic ’ -> ’

 pento: Ugh, possibly. Google’s cached version from yesterday isn’t showing
 it, so I assume it’s related.

 Then by @takahashi_fumiki, regarding a thread on support forums:
 takahashi_fumiki: Every multibyte characters were broken on Forum.
 But now it seemed fixed. Ping for just confirmation.

 pento: Thanks @takahashi_fumiki, we were using the wrong character set for
 a little bit, it’s fixed now.
 Please let us know if you see any other problems. :)

 At this point, the issue was supposedly fixed, but our moderators still
 encountered it:
 cyrillic chars are broken here
 It seems to be in CP 1252 instead of UTF8
 > we were using the wrong character set for a little bit
 message in topic is fresh

 A bit later, I encountered it myself:
 sergey: @pento @dd32 The encoding issue still happens on
 Cyrillic chars are randomly broken in some posts. Just happened again with
 this reply (1 min ago):
 > Ñ ÐºÐ°ÐºÐ¾Ð¹ верÑии было обновление? в
 админку заходили?
 > Обновление базы данных предлагалоÑÑŒ
 (Сделали?) ?
 Clicking Edit and re-saving appears to have fixed it.
 Could it be that the fix has not propagated to all servers yet? (edited)

 pento: @sergey: I’ve re-deployed everything, just to check.
 I’m off to bed, but if there are still problems, get someone to roll it
 back and I’ll try again some other time.

 sergey: @pento: Thanks, will keep an eye on the forums :)

 Still happens 12 hours later, see the latest screenshots.

 I don't see any related commits on https://meta.trac.wordpress.org/log/,
 so apparently it was a dotorg-specific change and it has to do with
 HyperDB (per one of the first messages).

 Could someone track it down or roll it back pending further investigation?

Ticket URL: <https://meta.trac.wordpress.org/ticket/2280>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list