SABnzbd Forums

If you set a category's priority to something different from the default, and then download a report from Newzbin with that category, the category is set on the queue item but the priority is still set to the default.

For example, I have the TV category priority set to Force, because I want episodes to download even if the queue is paused. I use Episode butler to download reports using the API. When a new episode appears in the queue, its category is set correctly but the priority is set to Normal. Same thing happens if I bookmark a report in the TV category.

If I then set the category manually, for example to Movies then back to TV, the priority is set correctly and the download starts.

Version: 0.5.0 RC3
OS: Windows 7
Install-type: Windows Installer
Skin: Classic - darkblue
Firewall Software: Windows 7 Firewall
Are you using IPV6? No
Is the issue reproducible? Yes

I cannot confirm your report.
The jobs do get the right priority from the category,
So that part of your report is not confirmed.

What does go wrong is that the place is the queue is incorrect.
The new job having a higher priority stills get added to the bottom of the queue.

This will be fixed in the final release 0.5.0

I'm noticing this problem as well.

SABnzbd+ 0.5.0 RC3

My category/priority setting for category "TV".


Added a tv episode for testing:



This is adding the file via the SABnzbd Tab firefox extension.

I also encountered this problem when using Episode Butler: https://forums.sabnzbd.org/index.php?topic=3202.0

If I set a category manually via drop-down in the queue, the priority is updated correctly.

Maybe a problem with the way NZB's are added by third-party programs?

There is one real problem: that the priority gets set correctly, but it isn't effective.
This means you can see High priority jobs below lower ones.
It only happens when coming from an RSS feed and when you enter
newzbin report numbers or any URL in the AddNZB dialogue.

The other is probably a perceived problem only.
An NZB will only use the category's priority when the API call
does not include a priority setting.
An explicit priority will always overrule the one from the category.

Gotcha.

Time to go harrass third party debs to not set explicit priorities unless necessary, then, I suppose.

What about bookmarking a report on Newzbin? That produces the same outcome but doesn't use the API.

Ah ha!

The plot thickens!

Any updates on the newzbin bookmarking priority issue? Is it even an issue?

It will be solved in 0.5.0 Final.

Awesome.

Thanks!