Carp Rss Problems

[TCH-Thomas]

Anyone received this error and knows what to do about it?

[CaRP]XML error: not well-formed (invalid token) at line 22

 

I´ve checked Carps own forum, while others have had the same problem, no one there seems to know why it happens or what to do about it.

[TweezerMan]

It looks to me like whatever RSS/XML feed that CaRP is trying to read has some invalid XML code in it. You might try running the URL of the feed through the Feed Validator and see if the feed has XML errors. If it does, you have to contact the publisher of the feed to have them correct the problem.

[TCH-Thomas]

Thanks David.

It´s good to know it´s not a fault on my end then, since that validator did report a error.

 

However, here is a new question, which came up in my head after visiting that validator site.

 

The validator site says:

Your feed appears to be encoded as "ISO-8859-1", but your server is reporting "US-ASCII"

Is there someway I can change that?

[TweezerMan]

It depends on whether you're talking about a feed you produce (yes), or one from another site (no).

 

What the Feed Vailidator is talking about is 1) the encoding declared in the first line of the feed, and 2) the encoding declared in the HTTP headers sent by the server.

 

My site's XML feed has the following in the first line, declaring an encoding of "UTF-8":

><?xml version="1.0" encoding="utf-8"?>

My server does not send a character encoding in the HTTP headers, so there is nothing to conflict with. If the server did send a different encoding in the HTTP headers (like "ISO-8859-1"), that is something I'd probably take up with the Help Desk (although there are ways to possibly address the issue yourself).

[TCH-Thomas]

Ok. Thanks David.