WordPress.org

Making WordPress.org

Opened 3 years ago

Closed 2 years ago

Last modified 15 months ago

#1320 closed defect (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.

https://www.evernote.com/l/ABRIz2B2i8pC_Z9KC1uroGRE1MQpwHhWktsB/image.png

Attachments (1)

all-topics.xml (46.9 KB) - added by ShinichiN 3 years ago.
XML from https://ja.forums.wordpress.org/rss/view/all-topics

Download all attachments as: .zip

Change History (12)

#1 @ocean90
3 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 @ocean90
3 years ago

  • Resolution set to fixed
  • Status changed from new to closed

#3 @tg29359
2 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.

Last edited 2 years ago by tg29359 (previous) (diff)

#4 @ocean90
2 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

The broken char was removed yesterday.

#5 @tg29359
2 years ago

The broken char will be back soon. And this ticket shall be reopened soon.

#6 @tg29359
2 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 and again and forever).
But this time, Google Chrome says that Bytes: 0x03 0x26 0x23 0x33, not 0x08.

Last edited 2 years ago by tg29359 (previous) (diff)

This ticket was mentioned in Slack in #meta by ocean90. View the logs.


2 years ago

#8 @ocean90
2 years ago

  • Resolution set to worksforme
  • Status changed from reopened to closed

#9 @ocean90
2 years ago

Should be finally fixed with the upgrade to bbPress 2.x, see #1544.

#10 @tg29359
2 years ago

Reproduced? or another problem?

https://ja.forums.wordpress.org/rss

#11 @SergeyBiryukov
15 months ago

#656 was marked as a duplicate.

Note: See TracTickets for help on using tickets.