[wp-trac] [WordPress Trac] #63825: Creating a post containing UTF-8, then changing WP_CHARSET to "latin1", makes posts un-editable.

[WordPress Trac]

#63825: Creating a post containing UTF-8, then changing WP_CHARSET to "latin1",
makes posts un-editable.
-------------------------------------------------+-------------------------
 Reporter:  mcc111                               |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Database                             |     Version:  6.6.2
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-screenshots close  |     Focuses:  ui
-------------------------------------------------+-------------------------

Comment (by mcc111):

 Hi jonsurrell, the bug report was not about ''why'' the encodings got
 confused— I do not even know for a fact this happened in WordPress at all,
 as far as I know the mixup could have happened in MySQL. The problem is

 1. I need to run in DB_CHARSET=latin1, for a valid reason (my site appears
 wrong without it)
 2. Running the site with the option DB_CHARSET=latin1 causes an
 unacceptable breakage (silent failure with symptoms that actively mislead
 the user)

 It seems you've closed my bug arguing the reason I want DB_CHARSET=latin1
 is invalid (IE, you believe that my 2020 failure "shouldn't happen", or
 isn't debuggable). I think this is unreasonable because it ''doesn't
 matter why'' I set DB_CHARSET to latin1— ''anyone'' who sets DB_CHARSET to
 latin1 for ''any reason'' while having at least one UTF-8 character in a
 post will see this same failure (the 2024 failure, the UI-failure-without-
 error-message). I only mentioned the 2020 failure to provide context.

 Now, it might be the case #62172 will make this irrelevant anyway by
 removing DB_CHARSET=latin1 completely. If so I guess that does obviate the
 need for good error messages around DB_CHARSET=latin1, but it will create
 a larger and potentially harder-to-solve set of problems for me (as
 currently DB_CHARSET=latin1 solves a problem I have).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/63825#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform