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
When search plugins are installed the Jackett search plugin gets enabled by default along with other ones. The problem is that many users don't have Jackett server and this only leads to error being displayed in the search results until Jackett is manually disabled. The solution is probably simply to not enable Jackett by default. Or possibly even detect its availability and act accordingly - just not blindly enable it by default, which leads to errors with default configuration.
Steps to reproduce
Install search plugins for the first time with the Check for updates button.
Observe Jackett being enabled alongside other plugins regardless of its availibility on the host system.
Additional context
No response
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered:
The problem is that many users don't have Jackett server and this only leads to error being displayed in the search results until Jackett is manually disabled
Indeed. This is a good point.
If jackett is not running then the user sees something like this:
Jackett: api key error! Right-click this row and select 'Open description page' to open help. Configuration file: '/home/foo/.local/share/qBittorrent/nova3/engines/jackett.json' Search: 'random search term'
qBittorrent & operating system versions
qBittorrent: 4.6.3 x64
Operating system: Arch Linux x64
Qt: 5.15.12
libtorrent-rasterbar: 1:2.0.9
What is the problem?
When search plugins are installed the Jackett search plugin gets enabled by default along with other ones. The problem is that many users don't have Jackett server and this only leads to error being displayed in the search results until Jackett is manually disabled. The solution is probably simply to not enable Jackett by default. Or possibly even detect its availability and act accordingly - just not blindly enable it by default, which leads to errors with default configuration.
Steps to reproduce
Additional context
No response
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: