[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
  needs-test-info                                |
-------------------------------------------------+-------------------------
Changes (by jonsurrell):

 * keywords:  needs-testing has-screenshots close => needs-testing has-
     screenshots close needs-test-info


Comment:

 Thanks for the additional detail.

 One clarification: ''I did not close the ticket.'' I added a workflow
 keyword `close` that marks it as a candidate for closure. Subtle and
 somewhat confusing, but not the same thing. This ticket remains open, but
 other folks may close it if they agree with my reasoning.

 I marked it as a closure candidate because it's unclear to me that this
 has a productive path forward. The information I understand is that:

 - This site was working fine with encoding X
 - Something happened to cause the site to have encoding Y
 - At this point it's likely there's data with different encoding in the
 database, things are already corrupt
 - You were able to workaround the issue and fix the problem to some extent
 by changing `DB_CHARSET=latin1`.
 - A post that may have been stored with encoding X, Y or `latin1` could
 not be edited in the editor

 At the final step, data was likely already corrupt. I don't want to
 dismiss that, it's ''terrible'' for a user. But, with corrupt data,
 editing a post could make things worse! Depending on the contents of the
 post, it's possible that the editor made a best effort to show you the
 post but found it so corrupt that there was nothing to show. At that point
 it doesn't seem like there's much to be done.

 -----

 If there are more details you can provide such as the post content for the
 post in question, the database encoding before and after the problem, or
 some minimal reproduction examples, it may help this move forward.

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