nzbhydra2

v2.3.4

Fix: Move cancel button in dialog shown while searching because you're all too slow to click it.

Fix: Prevent database trace file becoming too large

Fix: Keep less gclog files in the log folder

v2.3.3

Fix: Connection to hosts like 'sabnzd' would fail

v2.3.2

Fix: 2.3.1 didn't start for users updating from 2.2.5 to 2.3.0. Fuck this shit

v2.3.1

Fix: 2.2.5 unfortunately may have caused database corruption in some cases. Hopefully no more... The fix may need some time the first time this new version is started.

v2.3.0

Feature: Java 11 is now supported. This required an update of the internal framework which might have some unforseen side effects (bugs), especially regarding authentification and handling of reverse proxies. Let me know if something doesn't work as expected.

Feature: Rename searching option 'Ignore temporarily disabled' to 'Ignore temporary errors'. If enabled indexers will not be temporarily disabled at all if a recoverable error occurs.

Fix: Opening magnet links under Windows 7 doesn't require administrator rights anymore.

v2.2.5

Fix: In some cases (with really big databases) the check of the API hit limit could take very long. This was hopefully improved. Migration to this version might take a bit for such instances.

v2.2.4

Feature: Add indexer specific limit to caps check. Background: RARBG only allows one request every two seconds so the caps check, which until now used two concurrent threads and a delay of 1 second, would result in errors. The limits are hard coded. Hydra will not attempt to do any rate limiting for regular search requests.

v2.2.3

Feature: Include database metadata in debug infos

v2.2.2

Feature: Minor improvements to performance logging

v2.2.1

Feature: Improve logging of unparseable indexer responses

v2.2.0

Note: This release brings some major changes regarding categories and the handling of newznab categories. Please let me know if it breaks anything or has unexpected side effects (or if you love what I've done ;-))
Feature: Allow combinations of newznab categories which must all be found in a search result for that category to be applied. For example 4090&11000 will only match items with both 4090 and 11000. This should allow for even finer category tuning with trackers accessed via Jackett.

Feature: Replace newznab categories incoming API searches with newznab categories of mapped category. For example when you have 2040,2050 configured for Movies HD and a search comes in using 2040 then indexers will be queried using 2040,2050. Until now only the supplied category was used (2040 in the example). This should result in more results to be found and so far I can't tell if it will return just better results or more crap. You can disable this with the 'Transform newznab categories' setting in the searching config.

Feature: Related to above: The categories on the caps page are created from the configured categories. To keep this clean only one newznab category will be used for every category (e.g. Movies HD using 2040,2050 will only be included once with 2040 as ID.
Fix: Use dereferer for NZB details site

v2.1.7

Fix: Fix/improve category mapping introduced in 2.1.6. Use custom newznab categories if none from the predefined range are provided.

v2.1.6

Fix: When uploading a backup file the UI didn't update to inform the user about the progress after the file was uploaded
Fix: Improve category mapping for (torznab) indexers. Some use custom newznab category numbers (>9999) which could not be properly mapped to preconfigured categories.

v2.1.5

Fix: Improve handling of movie and tv searches with some indexers (see v2.0.23). I just wish all indexers could work the same... :-/
Fix: Prevent indexers without caps from being caps checked (NZBIndex, Binsearch)
Fix: Improve wording indexer state when disabled by the system due to an error from which it cannot recover automatically

v2.1.4

Feature: Allow retrieval of history and stats via API. See https://github.com/theotherp/nzbhydra2/wiki/External-API,-RSS-and-cached-queries
Fix: Repeat of searches from history sometimes used wrong parameters
Fix: Added nzbs.org to list of indexers unable to process type searches without IDs

v2.1.3

Fix: Removed dead indexers from presets
Fix: Prevent exception related to duplicate TV infos in database

v2.1.2

Fix: Indexer added as newznab indexer even when selected as torznab in the config GUI

v2.1.1

Fix: Validate config to prevent indexers with duplicate names
Fix: Validate config to prevent torznab indexers being added as newznab indexer and vice versa

v2.1.0

Fix: Search query was not built properly when conversion of search IDs did not provide any IDs usable by an indexer
Feature: Support API caps in JSON

v2.0.24

Note: Added NZBGeek to the list mentioned in v2.0.23. Thanks to the user letting me know about it.