HtmlDecode for problematic indexers

[Sek0n]

Wasn’t sure if this would be better here or support, so sorry if it’s in the wrong place.

I’ve started using morethan.tv, but ran into a problem where any release that has an apostrophe comes up with the html code(&#3 9;) instead of the actual character, resulting in the release being ignored.

Example:

It comes up correct on their webpage, but the RSS and ajax search(which is what Jackett uses to search) both give the html code.

I tried to bring this to their attention, but I think there is a slight language barrier, and they think it’s a sonarr issue. I would bring this to Jackett too, but it’s not being developed now.

Just curious if this is something that could be implemented in sonarr so it would also fix it for any future, or unknown current indexers that do this?

[markus101]

This seems like a Jackett issue to me, something in how its being scraped would be my first place to look. Its unfortunate about Jackett, but this issue should be fixed there as its going to be a slippery slope of scraping bugs that we would need to deal with if it was handled in Sonarr.

[Sek0n]

That’s what I was thinking, or an issue on the tracker. Thanks

To clarify for anyone looking; on the ajax search results that I forgot to include, they report any series with an apostrophe like this:

Shows correctly on the webpage, but the plain text that’s used on the search gives the htmlcode.