Jump to:

When processing an atom feed, if the link element follows an image, textinput, summary, tagline, subtitle, logo or info attribute within an entry, that link will be attributed to the feed URL instead of the entry. Atom feeds which do not have a link attribute before those other elements (most, including many atom feed samples around the web), will have the same link URL for every entry as a result.

The aggregator module is virtually unusable for atom feeds unless attributes within the entry are ordered to accommodate.

Parses correctly

<title>This is fine</title><link href="http://example.org/" /><summary>The link appears before the summary.</summary>

Parses incorrectly

<title>We have a problem</title><summary>The summary appears before the link, and so we have a problem</summary><link href="http://example.org/" />

well, this issue isn't looking like it's getting 'major' priority ... if this is issue is affecting a site you're working on now, you might try using feeds module. I think it's much more robust and flexible. I think it also should be able to do all the core aggregator module does plus more. I haven't used recent versions for aggregation though, so I'd be curious if it works for you.

Thanks for the heads up. I've asked the developer of a feed we're importing to change the order of attributes to accommodate, so I don't need a patch right now, but I just wanted to make sure this issue got the attention it deserves, but if feeds does exactly what the aggregator module does and more, I suppose that could be why this isn't considered important at the moment.

Yes it seems to be the same issue. I think your options are waiting for a rewrite or using the Feeds module as recommended above. Waiting for a rewrite might take some time because it appears to be a large task, and I'm not sure if anyone is up to it at this point.