Atom 1.0 Feed Problems

1. TEXT/HTML MEDIA TYPE ERROR
My feed https://domain.com/wp/feed/atom/ has the following on line 13
<link rel=”alternate” type=”text/html” href=”https://domain.com/wp&#8221; />
Feed Validator thinks this media type shouldn’t be specified in Atom feeds.

Feed Validator is wrong on this one. That’s a link to an alternate version, not a self link. And the atom feed is served as the correct content type, not as text/html.

3. SELF-REFERENCE ERROR

I may be out on a limb here, but I thought as RSS 2.0 feeds could reference WP categories, the same could be done with the latest Atom 1.0 standard. So I’m specifying the following in header.php:

<link rel=”alternate” type=”application/atom+xml” title=”Atom 1.0 – Category: XYZ” href=”https://domain.com/wp/category/xyz/feed/atom/&#8221; />

Netnewswire and Safari read it just fine, but the self reference on line 15 of the feed, points back to the generic Atom feed not the category feed:
<link rel=”self” type=”application/atom+xml” href=”https://domain.com/wp/feed/atom/&#8221; />

That’s a bug, probably should be put into trac.

@otto42:

(1) The error is the media type specified as text/html. FV is saying that not part of Atom spec? This error is nothing to do with self-reference in (3). If the feed is supplied as correct content type then why does it declare it as text/html? Surely there is a problem here…

(3) Self reference error relates to link at very end of post.

(1) The error is the media type specified as text/html.

That’s not the error you indicated in the first place.

If it’s saying “Feeds should not be served with the “text/html” media type” then that’s something different. That has nothing to do with the alternate link element.

That’s a header issue of some sort, because the atom feed is supposed to be served as application/atom+xml. That’s why the header “Content type” stuff is at the top of the feed-atom.php file, to force the content type to the right thing.

You may have a plugin or something else interfering. WP-Cache has been known to do this. A fix for WP-Cache can be found here: https://blog.saddey.net/2007/02/18/how-to-prevent-wpcache-from-changing-a-feeds-content-type-to-text-html/

You write:

>That’s not the error you indicated in the first place.

Someone needs to learn to read properly and stop being so downright condescending! Enough of this! That is *exactly* what I said in the first post.

I wrote:

>The feeds were validated here, and DO validate as Atom 1.0 feeds
>Feed Validator thinks this media type shouldn’t be specified in Atom feeds.

I’ve never made any statement that there was an issue with the alternate link statement. Where did you get that from? Huh? You’re creating issues that simply aren’t there. Learn to read.

You write:

>That’s a header issue of some sort, because the atom feed is supposed to be served as application/atom+xml. That’s why the header “Content type” stuff is at the top of the feed-atom.php file, to force the content type to the right thing.

Yes I know it’s *supposed* to be application/atom+xml, that’s how it’s defined it in my header.php. FV knows it’s *supposed* to be application/atom+xml that’s why it’s flagged as an error to be defined as text/html in the feed.

If you can’t be bothered to properly read what I’ve said and stop being so downright condescending I just won’t bother flagging up these issues. I’ve got better things to do with my time than put up with such an appalling attitude.

Goodbye.

I’ve never made any statement that there was an issue with the alternate link statement. Where did you get that from? Huh?

You mentioned the <link…> statement in your very first post as being the source of the problem with text/html.

So… Sorry for trying to help. Thanks for leaving.