feed1 article display in feed2

[GoogleCodeExporter]

I install and uninstall(uninstall and remove setting / cache folder)
several times, and get the same error.
- folder 1
- - feed11(20 item)
- - feed12(40 item)
- - feed13(60 item)
- folder 2
- - feed21(40 item)
- - feed22(xx item)
- - feed23(xx item)
1. update feed11 get 20 article.
2. update feed12 get 40 article, 20 new article and 20 old article(belong
to feed11)。
3. update feed13 get 60 article, 20 new(20 feed11 and 20 feed12)
4. update feed in other folder, some time is right and some time is
wrong(same as before).

my setting: 
 * system's wm5.0.
 * install in sd.
 * max 200 article.
 * cache article.
 * cache image.
 * 5 folder and 30 feed.
 * auto connection.
 * connection internet by usb.

Original issue reported on code.google.com by vical...@gmail.com on 19 Nov 2008 at 11:05

[GoogleCodeExporter]

Can you export the registry branch under:
HKCU/Software/DaProfik/pRSSreader/Subscriptions and submit it here?

If I remember well, PHM registry editor should be able to do that (it for free).

Original comment by and...@gmail.com on 19 Nov 2008 at 7:48

[GoogleCodeExporter]

The system and the feed is chinese.
I it seems the feed2 copy feed1's article befor real update.

Original comment by vical...@gmail.com on 20 Nov 2008 at 3:13

Attachments:

• DaProfik.reg
• main.PNG
• feed1.PNG
• feed2.PNG
• system.PNG

[GoogleCodeExporter]

The problem is that 3 feeds of zaobao.com are being saved into the same file
'zaobaocom' and the three other feeds are saved into the file called Feed. You 
shold
be able to find these files in the cache folder. That is why you see the 
articles in
the incorrect feed.

The question is what did you do (exactly) to get this state, since pRSSreader 
has
routines to prevent saving into the files of the same name.

Original comment by and...@gmail.com on 20 Nov 2008 at 4:09

[GoogleCodeExporter]

I think you can use the url as filename.

Original comment by vical...@gmail.com on 21 Nov 2008 at 4:29

[GoogleCodeExporter]

pRSSreader will be using SHA1 hash of the feed url as the file name, so this 
should
not happen again. Thus closing this issue.

Original comment by and...@gmail.com on 16 Dec 2008 at 12:19

• Changed state: Fixed