You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the endpoint torrents/setCategory will create a new category if the category passed doesn't exist. However, passing a new category results in a 409 Client Error: Conflict. Passing an existing category is successful.
What is the expected behavior
The preference is to add a new category if the passed category doesn't exist, as stated in the API docs. **Or correct the API docs to state the category must exist prior to calling setCategory (createCategory exists and is working, so there is a work around)
Steps to reproduce
Make API call to torrents/setCategory using a new category.
Extra info(if any)
(type here)
The text was updated successfully, but these errors were encountered:
This behavior was changed in PR #9228 and is reflected in WebAPI 2.1.0. I've updated the WebAPI docs to reflect this change. Thanks for reporting this @zfwjs.
Please provide the following information
qBittorrent version and Operating System
qB = v4.1.3 - Ubuntu 18.04.1 LTS Server
If on linux, libtorrent and Qt version
libtorrent= 0.13.6-2build1
What is the problem
According to the API docs here:
https://github.com/qbittorrent/qBittorrent/wiki/Web-API-Documentation#set-torrent-category
the endpoint torrents/setCategory will create a new category if the category passed doesn't exist. However, passing a new category results in a 409 Client Error: Conflict. Passing an existing category is successful.
What is the expected behavior
The preference is to add a new category if the passed category doesn't exist, as stated in the API docs. **Or correct the API docs to state the category must exist prior to calling setCategory (createCategory exists and is working, so there is a work around)
Steps to reproduce
Make API call to torrents/setCategory using a new category.
Extra info(if any)
(type here)
The text was updated successfully, but these errors were encountered: