294969 - Thunderbird ignores RSS feed entries that reference the same url as a previous feed

Status: RESOLVED DUPLICATE of bug 297906

(MailNews Core :: Feed Reader, defect)

Description

[Marc Richards]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: version 1.0.2 (20050317)

Thunderbird fails to display multiple entries that reference the same url in the
aforementioned Atom Feed.

The feed in question was generated by the Macromedia Contribute Publishing
Services server to allow users to recieve notifications when updates are made to
a website.  The feed uses the link tag to indicate which page was updated e.g.

<link rel="alternate" type="text/html"
href="http://www.swarthmore.edu/academics/honors/handbook/02-Basics.html"/>

Taking a look around my profile it seemd like feeditems.rdf uses the url rather
than the entrie's id to differentiate between entries and therefore ignoring
other entries with the same url e.g.

<RDF:Description
RDF:about="http://www.swarthmore.edu/academics/honors/handbook/02-Basics.html"
                   fz:stored="true"
                   fz:valid="true">

That's my best guess anyway.

Reproducible: Always

Steps to Reproduce:
1. Subscribe to the feed

Actual Results:  
4 entries are displayed

Expected Results:  
7 entries should be displayed (This is how many I see using Firefox's Live
bookmarks)

Comment 1

[Mike Cowperthwaite]

There have been several fixes to RSS feed parsing since the 1.0 trunk was 
branched off.  The supplied URL works as a feed with TB 1.0+0515, Win2K.
Get a nightly trunk build, or wait for TB 1.1 to be released, to take advantage 
of these fixes.

Comment 2

[Marc Richards]

(In reply to comment #1)
> There have been several fixes to RSS feed parsing since the 1.0 trunk was 
> branched off.  The supplied URL works as a feed with TB 1.0+0515, Win2K.
> Get a nightly trunk build, or wait for TB 1.1 to be released, to take advantage 
> of these fixes.

I just tried version 1.0+ (20050522) and the problem still exists.  The URL
works as a feed BUT only 4 entries show up when in fact there are 7 entries in
the feed. That is the problem.

Comment 3

[Magnus Melin [:mkmelin]]

Confirming... with linux 20050521 build. The feed items with same url only show
up once. 

Comment 4

[Robert Sayre]

(In reply to comment #1)
> There have been several fixes to RSS feed parsing since the 1.0 trunk was 
> branched off. 

This one isn't fixed and is really serious. I suggest making it a blocker for 1.1. 

I can see the changes that need to be made in FeedItem.js to fix the problem
moving forward, but there will probably be migration issues unless we match
previously stored items with message-ids in the mbox.

Comment 5

[Magnus Melin [:mkmelin]]

The forumzilla extension now handles this. See http://www.melez.com/mykzilla/2005/11/indexing-items-by-id-rather-than-url.html

Comment 6

[Scott MacGregor]

maybe we can tackle this for thunderbird 2.0 if we can bribe Robert. Sounds like we might be able to crib some stuff from forumzilla.

Comment 7

[Mike Cowperthwaite]

*** Bug 325441 has been marked as a duplicate of this bug. ***

Comment 8

[Magnus Melin [:mkmelin]]

*** Bug 333577 has been marked as a duplicate of this bug. ***

Comment 9

[Marc Richards]

Is this still on the radar for 2.0?  

I also encounter this bug while using RSS feeds for tracking wiki changes in our local Trac (http://projects.edgewall.com/trac/) installation.

Comment 11

[Piotr Skowronek]

As we can see, 2 years and nothing was done regarding this bug,
in the meantime 2 other people plus me, issued the same bug.

Robert suggested to make it a blocker for TB 1.1...
Scott suggested to tack it for TB 2.0...
We have got TB 2.0 released, and the bug is still open,
that's why I think there is a need to fix it sooner than later :)

Comment 12

[Kill Gates]

I agree with Piotr.

Comment 15

[David E. Ross]

This might be caused by the problem cited in bug #754704.

Comment 16

[Wayne Mery (:wsmwk)]

(In reply to David E. Ross from comment #15)
> This might be caused by the problem cited in bug #754704.

potential problem - it's not clear anyone watching this bug still sees it.