[wp-trac] [WordPress Trac] #33524: json_encode giving invalid UTF-8 sequence followed by maxed CPU's
WordPress Trac
noreply at wordpress.org
Wed Aug 26 03:25:17 UTC 2015
#33524: json_encode giving invalid UTF-8 sequence followed by maxed CPU's
-------------------------------------+---------------------
Reporter: thehrisworld | Owner: pento
Type: defect (bug) | Status: closed
Priority: normal | Milestone: 4.4
Component: General | Version: 4.1
Severity: normal | Resolution: fixed
Keywords: needs-testing has-patch | Focuses:
-------------------------------------+---------------------
Changes (by pento):
* owner: => pento
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"33747"]:
{{{
#!CommitTicketReference repository="" revision="33747"
When `wp_json_encode()` calls `json_encode()`, the latter will generate
warnings if the string contains non-UTF-8 characters. No-one likes
warnings, so we need to do something about that.
The good news is, the point of `wp_json_encode()` is to handle those non-
UTF-8 characters. It'll totally just fix them up, no problem.
Anyway, we can just ignore those warnings.
Fixes #33524.
}}}
--
Ticket URL: <https://core.trac.wordpress.org/ticket/33524#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list