SABnzbd Forums

I have noticed this once or twice, but i think i have how it happened now.

I forced a RSS refresh and added an nzb. It came with the correct category, X (I do not know if this is a required step, or auto-adding would have worked).
I then manually added a nzb using the API. It should have the default category Y, but instead it had X. This was true for the next addition as well.

I waited until the queue was clear, and tried another manual addition, and this time it correctly came in with the default Y category.

How did you add the NZB? Through the upload window? (of the Glitter skin?)

The first addition was with the Download button from the Rss feed interface. As i mentioned, i dont know if this was special, or if it was added automatically over time, it would have still casued this.

The manual addition was with the chrome app SabConnect++, which uses the api i assume. I have been using for years without incident. This is Glitter.

Both RSS and using an add-on have the option to override the category.
With this little info it's hard to tell where things went wrong, if at all.
We do need some more details.

What addition information could i provide or generate?

It seems the use case is not that common, because i have only noticed this twice.

Debug log files of the event would be useful, combined with the content of your sabnzbd.ini file.
(Should you send the latter, remove all passwords from the copy.)
The category system is quite complicated.
Category can come from NZB or indexer meta-data.
It can come from the default for RSS
It can come from specific filters.

The API calls come from usenetcrawler.
If my category name happens to match their category name, perhaps it automatically puts it.

Jumbs wrote: If my category name happens to match their category name, perhaps it automatically puts it.

It does. But isn't that what you want anyway?

Possibly, never thought about it.
When the beta came out, i figured it was time to clean up my categories and scripts.
Renamed a category to TV (from HDTV), which i guess made this start working.

Ill keep an eye on it and try to prove it is working as intended, and there is not an actual bug.