Text in database should not be entity-encoded
|Reported by:||redsweater||Owned by:|
I've noticed that some text, e.g. the names of categories and the post_content, are stored in the database with XML-compatible (I think) entity encoding. For instance, the & character is stored in the database as "&"
Other fields, such as the Excerpt and Title for instance, store the same & character verbatim in the field as &.
It seems that for consistency, the text in the database should be of a standardized form. I would vote for not storing entity encoding in the database, as it seems more of a presentational thing.
To observe the issue, just write a test post in which the & character for instance appears in all possible text fields. Then observe the database directly to see what has happened.
This has particularly vulgar affects on the sanity of the text values returned by the XML-RPC interface, which I'll describe in another bug report.
Change History (10)
comment:3 @redsweater — 8 years ago
- Summary changed from Text in database is inconsistently entity-encoded to Text in database should not be entity-encoded
- Keywords needs-patch added; has-patch needs-testing removed
- Milestone 2.9 deleted
- Resolution set to wontfix
- Status changed from new to closed