-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Anidex search by categories does not work whilst searching by "any" works #9727
Comments
the anidex indexer needs to separate the categories in the query with a comma, like this: ATM the anidex indexer is encoding the comma as %2C and this generates a query like:
|
Working in browser:
|
Jackett 0.16.1583 |
Cool, now it works as expected. Thanks! |
Hhmmm this is happening again in 0.17.159 😕 |
Same workarounds as before work in browser: current (blocked) - https://anidex.info/?q=2020+720p&s=upload_timestamp&o=desc&group=0&id=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16 extra comma - https://anidex.info/?q=2020+720p&s=upload_timestamp&o=desc&group=0&id=1,2,3,4,5,6,7,8,9,10,11,12,13,14,,15,16 switch order - https://anidex.info/?q=2020+720p&s=upload_timestamp&o=desc&group=0&id=1,2,3,4,5,6,7,8,9,10,11,12,13,14,16,15 They have an RSS feed if we want to try to implement that - https://anidex.info/rss/ |
This is the way |
v0.18.95 |
Environment
OS: arch linux (using docker
linuxserver/jackett
).Net Runtime: Mono
Jackett Version: 0.16.1549.0
Last Working Jackett Version: not sure, the one used by latest linuxserver's docker image.
Are you using a proxy or VPN? yes, traefik
Description
Searching in anidex works, but as soon as you try to search with categories, it returns empty results. Selecting all tags doesn't help at all either.
Obviously sonarr & radarr aren't able to find anything because, AFAIK, it always uses categories when searching.
Note that this does not happen with other indexers, I'm only experiencing this issue with anidex.
Logged Error Messages
There are no errors. It just doesn't return results.
Screenshots
The text was updated successfully, but these errors were encountered: