View Full Version : RSS Feed Problem
Hello,
I recently upgraded to Pixelpost 1.7 and noticed a few things regarding my feed. I am using Feedburner and the original feed validates, although, there is a 'missing atom:link with rel="self"'. I'm not sure if it's cause for concern.
Here is the link to the Feed Validators results (http://feedvalidator.org/check.cgi?url=http%3A//jonbernardkoch.com/index.php%3Fx%3Drss).
I also noticed that my Feedburner feed (http://feeds.feedburner.com/ASmallPainting) has an ugly Media Enclosure link of the image below my post. This never appeared with PP 1.6. Is there a way to get rid of the link?
Thanks for the help!
Jon
dhdesign
12-28-2007, 04:48 PM
With regard to the "original enclosure" link, this post (http://www.pixelpost.org/forum/showthread.php?p=52551#post52551) will tell you how to remove that.
Not sure what to tell you about the problems with the feed. Maybe one of the devs can answer that one for you.
It worked...Thank You! I removed line 122 of the function_feeds.php and I no longer see the media enclosure link on my Feedburner feed.
'missing atom:link with rel="self"' still there when I validate feed.
Any help is much appreciated.
dakwegmo
12-28-2007, 07:19 PM
I wouldn't worry about the atom:link message. The feed still validates, so everything should be fine. Fixing it would require hacking the code and as rumors seem to indicate 1.7 Final is just around the corner you'd need to hack the files again after you upgrade.
The feed does validate, so, you're right it should be ok...it's just a minor concern. I'll look forward to the final release of 1.7. Thank you for your help.
dakwegmo
12-28-2007, 08:42 PM
If you want to hack the functions_feeds.php to eliminate the warning do the following.
Find each occurrence of:
$output .= "<rss version=\"2.0\">\n";
and Replace it with
$output .= "<rss version=\"2.0\" xmlns:atom=\"http://www.w3.org/2005/Atom\">\n";
This should be in three places, around lines 27, 150, and 280.
Then after each occurrence of this line:
$output .= "<link>".$cfgrow['siteurl']."</link>\n";
Add this line:
$output .= "<atom:link href=\"".$cfgrow['siteurl']."index.php?x=rss\" rel=\"self\" type=\"application/rss+xml\" />\n";
Again, three ocurrence, around lines: 30, 155, and 287.
I haven't really dug into why the RSS feed requires an atom:link to validate without warnings, but I have tested the code and it works.
Im a lil bit confused as warning is releated with ATOM and feed which is validated is RSS.
Does anyone get what is going on right here??
I was googling for this issue and IMHO there is very strange situation and as its not straight from RSS specification then we shouldnt add it. This is only recomendation which can disappear within some short time.
I dont get it the same as I dont get exactly what it is for. Its clear which feed is used and there is no reason what for we should duplicate this data within feed.
Thank You dakwegmo....If the warning persists I may try that hack.
dakwegmo
12-29-2007, 04:36 AM
Im a lil bit confused as warning is releated with ATOM and feed which is validated is RSS.
Does anyone get what is going on right here??
I was googling for this issue and IMHO there is very strange situation and as its not straight from RSS specification then we shouldnt add it. This is only recomendation which can disappear within some short time.
I dont get it the same as I dont get exactly what it is for. Its clear which feed is used and there is no reason what for we should duplicate this data within feed.
The validator says this: "This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations."
So it's a perfectly valid feed as is, but whoever designed the validator doesn't expect separate feeds for atom and RSS. I think it's being stricter than the RSS specification calls for.
Yesterday I read some comments about it and some guys involved in whole issue were writing its some strange part of ATOM vs. RSS war. They belive that after next few months there will be more ATOM in RSS so we should stop for a while and take a look what happen.
On the other hand - Wordpress added it in one of the lastest releases so I really dont know what to think about it. As its not warning or error I would live it for a while as it is to look what future brings.
vBulletin® v3.7.3, Copyright ©2000-2013, Jelsoft Enterprises Ltd.