From df012e9a0d6eec8acbad1e48be215aabdeb2675c Mon Sep 17 00:00:00 2001 From: Donald Webster Date: Wed, 20 Nov 2019 13:33:35 -0800 Subject: [PATCH] Updated Searches Indexers and Trackers (markdown) --- Searches-Indexers-and-Trackers.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Searches-Indexers-and-Trackers.md b/Searches-Indexers-and-Trackers.md index 3a02cbc..673748e 100644 --- a/Searches-Indexers-and-Trackers.md +++ b/Searches-Indexers-and-Trackers.md @@ -22,6 +22,8 @@ When you test an indexer or tracker, in debug or trace logs you can find the URL ### Testing a Search Just like the indexer/tracker test above, when you trigger a search while at Debug or Trace level logging, you can get the URL used from the log files. While testing, it is best to use as narrow a search as possible. A manual episode search is good because it is specific *and* you can see the results in the UI while examining the logs. +In this test, you'll be looking for obvious errors and running some simple tests. You can see the search used the url `https://api.nzbgeek.info/api?t=tvsearch&cat=5030,5040,5045,5080&extended=1&apikey=(removed)&offset=0&limit=100&tvdbid=354629&season=1&ep=1`, which you can try yourself in a browser after replacing `(removed)` w/ your apikey for that indexer. Does it work? Do you see the expected results? In that URL, you can see that it set specific categories with `cat=5030,5040,5045,5080`, so if you're not seeing expected results, this is one likely reason. You can also see that it searched by tvdbid w/ `tvdbid=354629`, so if the episode isn't properly categorized on the indexer, it will need to be fixed. You can also see that it searches by *specific* season and episode with `season=1` and `ep=1`, so if *that* isn't correct on the indexer, you won't see those results. + [[images/Series.Season.Episode.v3.png]] [[images/Series.Season.Episode.Search.Manual.png]]