#1320 closed defect (bug) (worksforme)
UTF8 encoding error in support forum's RSS feed
Reported by: | ShinichiN | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | International Forums | Keywords: | |
Cc: |
Description
When accessing to for example https://ja.forums.wordpress.org/rss/view/all-topics , we get encoding error and google chrome browser or SimplePie cannot parse the feed.
I attach xml file that we can see the whole feed.
Here's the WP_Error object I got from SimplePie bundled in WP.
object(WP_Error)#54 (2) { ["errors"]=> array(1) { ["simplepie-error"]=> array(1) { [0]=> string(129) "This XML document is invalid, likely due to invalid characters. XML error: not well-formed (invalid token) at line 338, column 25" } } ["error_data"]=> array(0) { } }
And here's the error message Google Chrome gave me.
This page contains the following errors:
error on line 327 at column 26: Input is not proper UTF-8, indicate encoding !
Bytes: 0x08 0xE7 0x8A 0xB6
Below is a rendering of the page up to the first error.
Attachments (1)
Change History (12)
#1
@
9 years ago
- Component changed from Support Forums to International Forums
I have removed the char from the post but it seems like the feed is cached somewhere.
#2
@
9 years ago
- Resolution set to fixed
- Status changed from new to closed
There was a new post, so the feed got re-built. It's now valid again: https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fja.forums.wordpress.org%2Frss%2Fview%2Fall-topics
#3
@
9 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
This problem has been reproduced.
https://ja.forums.wordpress.org/rss
It is not fixed.
And I think that rebuilding the feed is merely the time being. It is not resolusion for all the dashboards of Japanese users.
#4
@
9 years ago
- Resolution set to fixed
- Status changed from reopened to closed
The broken char was removed yesterday.
#6
@
9 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
This problem has been reproduced.
https://ja.forums.wordpress.org/rss
The broken char has returned today.
Please remove it again (and again ang again and forever).
But this time, Google Chrome says that Bytes: 0x03 0x26 0x23 0x33, not 0x08.
XML from https://ja.forums.wordpress.org/rss/view/all-topics