815268 - After upgrading to TB 17 an RSS subscription is broken

Status: RESOLVED INVALID

(Thunderbird :: Untriaged, defect)

Description

[Patrick Reinhard]

Attachment: Screenshot-Feed Subscriptions.png

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:17.0) Gecko/17.0 Firefox/17.0
Build ID: 20121120042406

Steps to reproduce:

I upgraded to 17.0

(Troubleshooting info:
  Application Basics
    Name: Thunderbird
    Version: 17.0
    User Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
    Profile Directory: Open Directory
              (Local drive)
    Application Build ID: 20121118032921
    Enabled Plugins: about:plugins
    Build Configuration: about:buildconfig
    Crash Reports: about:crashes
    Memory Use: about:memory)


Actual results:

a feed (http://www.engadget.com/rss.xml) stopped being updated; when trying to update it manually or removing it and subscribing to it again, TB says "The feed URL could not be found. Please check the name and try again." (see screenshot).
On the same machine the same feed works correctly with other applications and passes the w3.org validation test.


Expected results:

the feed should have been found and updated

Comment 1

[alta88]

that url sure works for me in Tb17 on win7.  you can set feeds.logging.console to debug and attach the error log if this really isn't some transient network/publisher error (they happen all the time).

Comment 2

[Patrick Reinhard]

The error log entry is:

Timestamp: 11/27/2012 11:08:35 AM
Error: no element found
Source File: http://www.engadget.com/rss.xml/

Comment 3

[alta88]

yeah, that's the 'publisher error' part.  the error is thrown by lower level gecko code and means there's no file to parse there.  you can see this by clicking (currently) on the link in the browser.

Comment 4

[Gene Scharmann]

The correct link to this rss is:

http://www.engadget.com/rss.xml

NOTE: Without the trailing '/'  (rss.xml is a file, not a directory!)

Comment 5

[Gene Scharmann]

Now: Who is adding the trailing '/' ?

Comment 6

[Patrick Reinhard]

Not me, as shown in the screenshot

Comment 7

[JLYoung]

I'm having the same problem with the same message in the error console (including the trailing slash).

Comment 8

[Gene Scharmann]

Since this bug has been marked STATUS: 'Resolved - Invalid' meaning they are blaming the publisher and *NOT* the code that is adding the unwanted trailing slash. Maybe someone having this problem should start a new Bug Report, unless [e-mail] is still monitoring this one.

In reply to alta88 from comment #3)
> yeah, that's the 'publisher error' part.  the error is thrown by lower level
> gecko code and means there's no file to parse there.  you can see this by
> clicking (currently) on the link in the browser.

I understand that the TBird superheros are having a lot of work right after the release of V.17.

I'm just a mortal (l)user, and don't have rights to change status.

Comment 9

[Patrick Reinhard]

A quick and dirty workaround to this "Resolved" bug is to subscribe via an online proxy, eg.

https://aniscartujo.com/webproxy/default.aspx?prx=http://www.engadget.com/index.php?a=feed-classic

This brought back my engadget feeds on TB, and by the way demonstrates that the problem is not in the rss.xml file, but in TB

hth

Comment 10

[Patrick Reinhard]

And adding a fake or even null parameter works as well:

http://www.engadget.com/rss.xml?bug=resolved
http://www.engadget.com/rss.xml?

Comment 11

[JLYoung]

Thank you Patrick, your second fix worked perfectly.