-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
nzbgeek multilanguage bug #888
Comments
Hydra usually doesn't care about the language and forwards all newznab attributes. You can test it by making the API query made by sonarr to hydra in your browser (e.g. http://127.0.0.1:5076/api/t=search&q=fullmetal.alchemist&apikey=). See if the attributes are returned properly. |
Hey, you are totally right. You forward the Language value without any changes: The syntax doesn't seem right on indexer side if I compare to this, but I will try to open a bug report on Sonarr Side. Is it possible you can parse that attribute so Sonarr can understand it as multi-language, or isn't that your intention with hydra, or simply not possible? And if the attribute is not set, Sonarr is trying to get the Language out of the Title and then multilanguage works, like here: I will open a bug on the Sonarr side. Thanks for your help so far. |
I could fix that if necessary but I'd rather have the indexer fix it or
perhaps sonarr.
…On Mon, 4 Sept 2023, 16:20 PeterRudolpf78910, ***@***.***> wrote:
Hey, you are totally right. You forward the Language value without any
changes:
[image: image]
<https://user-images.githubusercontent.com/143845956/265479525-e7d6fed6-82cc-4923-b556-a7ff4c15cfcd.png>
The syntax doesn't seem right on indexer side if I compare to this, but I
will try to open a bug report on Sonarr Side. Is it possible you can parse
that attribute so Sonarr can understand it as multi-language, or isn't that
your intention with hydra, or simply not possible?
And if the attribute is not set, Sonarr is trying to get the Language out
of the Title and then multilanguage works, like here:
[image: image]
<https://user-images.githubusercontent.com/143845956/265483827-2eb49a7f-86c6-43c0-b13f-a9ac470a118d.png>
[image: image]
<https://user-images.githubusercontent.com/143845956/265484629-1d2fc684-415a-41ae-9e22-50948ca4d952.png>
I will open a bug on the Sonarr side. Thanks for your help so far.
—
Reply to this email directly, view it on GitHub
<#888 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADNUA6J75MNE2LZFNX2OX2DXYXPTDANCNFSM6AAAAAA4ICEEAY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi nzbhydra team,
I tried the following. I wanted to search nzbgeek for a TV show with multiple languages. In the result, I can see the two languages, but it seems like nzbhydra is not mapping them correctly. When I look in sonarr it only shows Japanese and not both languages.
Could also be an issue from sonarr not interpreting the newznab:attr:language correctly, hope you can assist.
Here is the API call result:
Here is the debug archive:
nzbhydra2-debug-infos.zip
The text was updated successfully, but these errors were encountered: