Page 1 of 1

0.6.0 RSS Matched and not Matched error

Posted: May 13th, 2011, 2:13 am
by WARLOCK
Hi Guys,

Fists post so first off, awesome work thanks.

Ever since I have upgraded to 0.6.0 my rss feeds are not showing anything under matched and matched downloaded, but the feed is pulling and is actually downloading the files ? using Plush.

When using smpl - white, I can see the 5 downloads I am expecting to see but under Not Matched even though they have been downloaded. Clicking on read feed we are getting and "404 Not Found The path '/sabnzbd/m/test_rss_feed' was not found." error


Just to add my RSS Feed filters is set to "Accept *" I am filtering my feed at the nzbs.org site,

Re: 0.6.0 RSS Matched and not Matched error

Posted: May 13th, 2011, 2:15 am
by shypike
Which  browser do you use?
Did you clear your browser cache yet?
(It's sometimes needed).

Re: 0.6.0 RSS Matched and not Matched error

Posted: May 13th, 2011, 2:20 am
by WARLOCK
Firefox and yes cache was cleared, still would not explain why feeds are being downloaded but not reporting as such.

Version: (Ex: 0.6.0 )
OS: (Ex: Windows 7)
Install-type: (Ex: Windows Installer)
Skin (if applicable): (Ex: Plush, Smpl)
Firewall Software: (Ex: None)
Are you using IPV6? (no - most likely no)
Is the issue reproducible? (yes)

Re: 0.6.0 RSS Matched and not Matched error

Posted: May 13th, 2011, 2:32 am
by WARLOCK
Just to Add I can reproduce this on 2 different PC's and using either Firefox or IE

Re: 0.6.0 RSS Matched and not Matched error

Posted: May 13th, 2011, 2:46 am
by shypike
In previews you have to click the "Read Feed" button in order to see new data.
Unlike 0.5.6, 0.6.0 doesn't re-read the feed every time.
The cached content is just re-evaluated each time you enter the preview
and each time you change a filter.
As long as you don't click "Read Feed", only the scheduled read will
refresh the content.

This is what I'm guessing from your limited info.

Re: 0.6.0 RSS Matched and not Matched error

Posted: May 13th, 2011, 3:32 am
by WARLOCK
This can't be the case, coz with plush it's showing me nothing under matched and not matched yet under smpl - white it's showing me my feeds under not matched, for both of them it's showing my feeds under downloads.

With simple if I click reed feed  I get that 404 error, under plush nothing happens.

Re: 0.6.0 RSS Matched and not Matched error

Posted: May 13th, 2011, 4:00 am
by WARLOCK
Ok I see what's happened, as soon as it's matched it's downloaded, and if we read the feed again it won't so you the stuff already matched and downloaded  :(

As for my issue with the smpl page, I this it's was an install issue.

Re: 0.6.0 RSS Matched and not Matched error

Posted: May 13th, 2011, 4:04 am
by shypike
You normally test your feed in "disabled" mode so that the automated read-out
doesn't interfere with previewing.

Re: 0.6.0 RSS Matched and not Matched error

Posted: May 13th, 2011, 4:13 am
by WARLOCK
Understood, but then you'd have to wait a few hours to see if anything is matched against your filter.

e.g if I check right now I will not see any of my filters matched, I'd have to disable the feed wait till tomorrow and then check it, to ensure that all my filters are correct, as most things in the feed come out at the same time.

Before I forget there is still a problem with the smpl theme, it's showing six feeds as not matched though they were and they downloaded ?

Re: 0.6.0 RSS Matched and not Matched error

Posted: May 13th, 2011, 5:12 am
by shypike
Feeds usually contain older content too, that's what you test on.
If the data is not available you either wait or just enable automatic handling.
By the time the data is available, you use preview to see what wasn't matched.
What was matched is in your queue.
If you want to test after the fact. stop SABnzbd, remove the file admin/rss_data.sab
and start SABnzbd again. This way all your feeds will look as new and you test
your filters again.

The data supplied to the skins is identical.
Our release testers never reported differences between the skins in this area.
What we do see sometimes is bizarre differences between browsers and platforms.
(E.g. Chrome9 on Linux shows issues that aren't present on OSX or Windows).