Closed Bug 268050 Opened 20 years ago Closed 12 years ago

RSS: Not informed of bad feeds

Categories

(MailNews Core :: Feed Reader, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mozilla.bugzilla, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041103 Firefox/1.0RC2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041103 Firefox/1.0RC2

Just now I saw a message in the status bar flash by that said that one of my RSS
feeds is invalid.  But I don't know which one it is.  So one of my many RSS
feeds is not working anymore, but I've no idea which one it is, and to verify
each one by hand would take a long time, and I'm too tired for that right now.  :)

Reproducible: Always
Steps to Reproduce:
1.  Add a feed that works.
2.  Wait for the feed to go bad.

Actual Results:  
Thunderbird will never tell you that the feed went bad.

Expected Results:  
Tb should pop up a dialog box telling you that the feed is bad, and why, and
should give you the option of editing the URL or deleting the feed.

I almost want to mark this bug as major, because you can just merrily go along
in ignorant bliss that your RSS feed is bad, thinking that there are simply no
new articles, when in reality the feed has gone bad, and you need to do
something to fix it.
I don't know if the RSS feed is bad but  
when I try to add this feed in recent thunderbird 1.0RC (linux version) 
http://www.linux-quebec.org/wiki/ChangementsR_e9cents?action=rss_rc 
 
Thunderbird try infinitely to add it, without any warning or timeout and since 
there is no cancel button, you can correctly stop the action. 
 
 
I've seen this, although the feed in question corrected itself soon enough.
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: rss
Assignee: mscott → nobody
Component: RSS → Feed Reader
Product: Thunderbird → MailNews Core
current trunk (Tb14) implements Error Console logging via the pref Feeds.logging.console, with a value of info showing basic errors, and a value of debug showing more than anyone really wants to know.

error code 1: url could not be found, network error.
error code 2: fatal parsing error, maybe not a feed url.
error code 4: feed file unchanged since last check (for servers which support LAST-MODIFIED timestamps).

currently, the pref needs to be explicitly added in Options-Advanced Config Editor.

this is an interim solution as the proper implementation is to log to Activity Manager.
Tb15 now adds logging by default, closing.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.