367027 - Drag-n-drop one RSS folder to another disassociates feed

Status: RESOLVED DUPLICATE of bug 257700

(MailNews Core :: Feed Reader, defect)

Description

[Paul Stodghill]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Thunderbird 1.5.0.9 (Macintosh/20061207)

The number of feeds that I am subscribed to has reached the point where I would like to organize my feeds in a hierarchical manner (folders nested within folders). However, when I try to do this by drag-n-drop, the association between feeds and folders is lost.

Reproducible: Always

Steps to Reproduce:
1. Create a new "RSS News & Blogs" account.

2. Add a new subscription to the RSS account. I did this by
dragging and dropping the Slashdot feed (i.e.,
http://rss.slashdot.org/Slashdot/slashdot).

3. Create a new folder, named "NewFolder" under the main "News &
Blogs" folder.

4. Drag and drop the "Slashdot" folder to the "NewFolder"

Actual Results:  

The "Slashdot" folder and its contents will correctly appear as a
subfolder of "NewFolder". However, the subscription to the
Slashdot feed will no longer be associated with the "Slashdot"
folder.

The feeds.rdf contains the following entry,

  <fz:feed RDF:about="http://rss.slashdot.org/Slashdot/slashdot"
                   fz:quickMode="false"
                   dc:title="Slashdot"
                   NS1:link="http://slashdot.org/"
                   dc:identifier="http://rss.slashdot.org/Slashdot/slashdot">
    <fz:destFolder RDF:resource="mailbox://nobody@News%20%26%20Blogs/Slashdot"/>
  </fz:feed>

The destFolder element is wrong.


Expected Results:  
The expected result of dragging and dropping folders would be that the feed info would be updated would be updated correctly so that updates to folders would continue to query the appropriate feeds for new articles.

I would be happy to provide any additional info or run some test cases. Thank you for this wonderful piece of software.

Comment 1

[Mike Cowperthwaite]

The problem is a bit more complex than you describe; see bug 257700 comment 13 et seq.