nzbhydra2

v2.8.3

Fix Improve logging and handling of torznab/newznab XML transformation.

v2.8.2

Feature Support for pourcesoir.in, a french indexer. Their dev approached me with an idea on how to work around laws forbidding hosting NZB files. The indexer provides a certain text for each result using which you will find the result using a raw search engine like binsearch. NZBHydra will display a search icon in the search results GUI via which you can search for the result on Binsearch. I'll be honest, I'm not sure how viable that approach is, but I'm open to new ideas.

Fix Fix pagination display error with.

v2.8.1

Feature Allow to define sorting for the search results via URL parameters. Use &sortby= and, optionally, &sortdirection=asc or &sortdirection=desc. This will take preference to the sorting settings saved in a cookie but not overwrite them.

v2.8.0

Fix Hydra will use proper HTTP status codes when NZB download fails to signal that an indexer's API limit is reached. This will be recognized by *arr, which will skip the release and try another one. This will also prevent *arr from disabling NZBHydra in such cases.

Fix Fix minor issue in indexer uniqueness score calculation.

v2.7.7

Fix Indexer uniqueness score had wrong axis labels in the stats page.

v2.7.6

Feature Restore the indexer uniqueness score introduced with 2.7.0 and then rolled back due to database migration problems. The database is now restored on startup which should prevent any migration errors. The startup will take a while for this update.

v2.7.5

Fix Fix 'You're not allowed...' error caused by the fix in 2.7.4... :-/

v2.7.4

Fix Fix 'You're not allowed...' error related to security cookie. Thanks to /u/routhinator for the hin

v2.7.3

Feature Added option to configure cover width in search results.

Fix TMDB capabilities were not correctly checked.

Note I've added instructions to send one-time donations via PayPal and recurring donations via Github Sponsors.

v2.7.2

Fix I had to revert the changes from 2.7.0 because for some reason some databases could not be migrated. I'll need to take a closer look first, sorry.

v2.7.1

Fix Hopefully fix a problem which might prevent a successful database migration for some instances.

v2.7.0

Feature I've added a new statistics value called "Indexer result uniqueness score" (which is is a mouthful, if you have a better name please let me know). This score attempts to answer the question: Which indexer should I keep and which can I let go? See the wiki for more information. The score will only work for new downloads.

v2.6.18

Feature Add global cache time config parameter

v2.6.17

Feature Allow users to be used only for API update queries

Feature Allow regular expressions to be used in the search results title filter

v2.6.16

Fix Fix problems with special characters when using autocomplete

v2.6.15

Fix Fix form auth and remember-me cookies

v2.6.14

Fix Minor changes

v2.6.13

Fix Hopefully fix error with CookieTheftException introduced with v2.6.12

v2.6.12

Features Allow limiting the indexers to be used via API. Use "&indexers=,".

Fix Reduce how long sessions are kept open, possible reducing memory usage in some cases

v2.6.11

Fix Improve handling and performance of wildcards for removal of trailing words

Fix Added option to define how long Hydra will try to compress the database file when shutting down. With big databases shutting down may take up to 15 seconds by default. I'm still working on analyzing why some databases grow very large. Until I've found a way to prevent the root cause this option may help a bit but it will still require Hydra to shut down (or restart)