[wp-trac] [WordPress Trac] #63825: Creating a post containing UTF-8, then changing WP_CHARSET to "latin1", makes posts un-editable.
WordPress Trac
noreply at wordpress.org
Wed Aug 13 08:13:57 UTC 2025
#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
-------------------------------------------------+-------------------------
Changes (by jonsurrell):
* keywords: needs-testing has-screenshots => needs-testing has-screenshots
close
* component: Posts, Post Types => Database
Comment:
Thank you for the detailed report!
Whatever happened to your site around 2020 when the encodings got confused
should not have happened. I don't know how to debug that without a lot
more detail like a more specific time frame or details about WordPress
updates.
It's expected that data is corrupt when data is stored in the database and
different charsets are changed on a site without the appropriate database
migrations. A site should not do that on its own and certainly in a way
that content is becomes mangled.
See #62172 which seeks to standardize on UTF-8 and would help reduce this
type of problem in the future.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/63825#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list