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.
[Bug][Beta] Incorrect Category for default additions
Forum rules
Help us help you:
Help us help you:
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: [Bug][Beta] Incorrect Category for default additions
How did you add the NZB? Through the upload window? (of the Glitter skin?)
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: [Bug][Beta] Incorrect Category for default additions
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.
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.
Re: [Bug][Beta] Incorrect Category for default additions
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.
With this little info it's hard to tell where things went wrong, if at all.
We do need some more details.
Re: [Bug][Beta] Incorrect Category for default additions
What addition information could i provide or generate?
It seems the use case is not that common, because i have only noticed this twice.
It seems the use case is not that common, because i have only noticed this twice.
Re: [Bug][Beta] Incorrect Category for default additions
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.
(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.
Re: [Bug][Beta] Incorrect Category for default additions
The API calls come from usenetcrawler.
If my category name happens to match their category name, perhaps it automatically puts it.
If my category name happens to match their category name, perhaps it automatically puts it.
Re: [Bug][Beta] Incorrect Category for default additions
It does. But isn't that what you want anyway?Jumbs wrote: If my category name happens to match their category name, perhaps it automatically puts it.
Re: [Bug][Beta] Incorrect Category for default additions
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.
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.